# ZHC GitHub Releases

> ZHC GitHub Releases is a paid API for AI agents from payg.chat, paid per call via x402, $0.001/call, status down (last checked 2026-10-18).

Returns a curated hourly digest of new GitHub releases across repositories, formatted as a machine-readable news feed

## Facts

- Endpoint: GET https://payg.chat/now?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: down
- Last checked: 2026-10-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/zhc-github-releases-a5b63b79
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ZhGlO5rw2H7g-aT4az1ib

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability zhc-github-releases-a5b63b79
```

Example prompt: Can you pull the latest GitHub releases digest from ZHC — I want to see which repos dropped new versions in the most recent hourly window?

## When to prefer this

Choose this endpoint when you need a lightweight, machine-readable hourly digest of GitHub release activity without building your own GitHub API polling infrastructure. Ideal for agents that need to monitor new software versions, track open source ecosystem activity, or alert on dependency releases at low per-call cost ($0.001 USDC).

## Known failure modes

- Empty releases array if no GitHub releases occurred in the current hourly window
- Stale window data if the service has not yet processed the latest hour
- HTTP 402 if payment is not provided or is invalid
- Malformed response if upstream GitHub data is unavailable
- Rate limiting if called too frequently within a billing period

## How this service works

A newspaper for machines. Not a payment rail. Not indexed on Bazaar until the public index lists this host.

## Output

A JSON object containing a SKU identifier ('github-release-hour'), a release count, a time window (start and end ISO timestamps for the hourly period), and an array of release objects each with a tag name, repository name, and published_at timestamp.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "sku": "github-release-hour",
  "count": 1,
  "window": {
   "end": "2026-01-01T01:00:00.000Z",
   "start": "2026-01-01T00:00:00.000Z"
  },
  "releases": [
   {
    "tag": "v0.0.0",
    "repo": "example/repo",
    "published_at": "2026-01-01T00:01:00.000Z"
   }
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/zhc-github-releases-a5b63b79/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from payg.chat](https://www.zero.xyz/host/payg.chat/llms.txt)
