# Changelog State API – Chrome Releases

> Changelog State API – Chrome Releases is a paid API for AI agents from changelog-state-api.replit.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Returns structured, paginated recent release entries for the Chrome (Google Chrome) vendor as tracked by the Changelog State API.

## Facts

- Endpoint: GET https://changelog-state-api.replit.app/api/monitors/chrome
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/changelog-state-api-chrome-releases-a6c0911a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_bh5gk-K1-R1Q5lb0kpN0W

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 changelog-state-api-chrome-releases-a6c0911a
```

Example prompt: Pull the 10 most recent Chrome releases from the Changelog State API and show me the version numbers and publish dates.

## When to prefer this

Use this endpoint when you need structured, machine-readable release data specifically for Chrome and want pagination support to walk through historical entries. Prefer it over scraping Chrome release blogs directly when you need consistent JSON output and cursor-based pagination. It is best suited for agents that monitor vendor release cadences, perform dependency audits, or trigger downstream workflows on new Chrome versions.

## Known failure modes

- 404 if the literal slug 'chrome' is not tracked — verify available slugs via GET /api/monitors first
- 400 if a malformed or cross-vendor cursor is supplied
- Payment failure if the x402 USDC payment of $0.01 is not completed
- Empty results array if no releases have been detected yet for this vendor
- Rate limiting or upstream errors from the Replit-hosted service

## How this service works

Structured recent releases for one tracked vendor.

## Output

A JSON object containing a list of structured release entries for the Chrome vendor (e.g. version numbers, publish dates, release titles/notes) ordered newest-first, plus an opaque `nextCursor` token for fetching the next page of older results.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "pathParams": {
     "type": "object",
     "required": [
      "slug"
     ],
     "properties": {
      "slug": {
       "type": "string",
       "example": "openai",
       "pattern": "^[a-z0-9][a-z0-9-]*$",
       "maxLength": 64,
       "minLength": 1,
       "description": "Vendor slug, lowercase alphanumeric with dashes. Take one from GET /api/monitors and substitute it into the path: `{slug}` is a placeholder, and requesting those literal characters returns 404. Worked example: GET /api/monitors/openai."
      }
     }
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "limit": {
       "type": "integer",
       "default": 5,
       "maximum": 50,
       "minimum": 1,
       "description": "Maximum number of release entries to return on this page. The page size, not a total: use `cursor` to walk past it."
      },
      "cursor": {
       "type": "string",
       "default": "",
       "maxLength": 512,
       "description": "Opaque next-page token, copied verbatim from `nextCursor` on the previous response for this same vendor. Omit it — or send the empty string — to start at the newest entry. It names a position in the newest-first order rather than an offset, so a page you have already read never shifts under you: an entry that arrives mid-walk takes the place its own publish date gives it — above the cursor, on ground you have already covered, or below it, still ahead of you — instead of renumbering every page behind it. It does not expire; a walk can be paused and resumed. Do not construct or edit one: a token that is malformed, or was issued for a different vendor, is refused with 400 and is never charged."
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "enum": [
      "json"
     ],
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   },
   "description": "Full structured recent releases (paid)"
  }
 },
 "description": "Call shape for GET /api/monitors/{slug}."
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/changelog-state-api-chrome-releases-a6c0911a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from changelog-state-api.replit.app](https://www.zero.xyz/host/changelog-state-api.replit.app/llms.txt)