# Changelog State API – Structured Recent Releases for Sentry

> Changelog State API – Structured Recent Releases for Sentry 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-14).

Returns structured recent release entries for the Sentry vendor, tracked and formatted for programmatic consumption.

## Facts

- Endpoint: GET https://changelog-state-api.replit.app/api/monitors/sentry
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/changelog-state-api-structured-recent-releases-for-sentry-be8007fe
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_7jZIa1WYASv4R6ggUIfqg

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-structured-recent-releases-for-sentry-be8007fe
```

Example prompt: Can you pull the latest 10 structured release entries for Sentry from the changelog tracker?

## When to prefer this

Use this endpoint when you need machine-readable, structured release data specifically for Sentry and want a pre-tracked, normalized feed rather than scraping Sentry's changelog page yourself. It is ideal for automation pipelines, dependency monitoring agents, or alerting workflows that need reliable structured version data on a per-vendor basis.

## Known failure modes

- Unknown or untracked vendor slug returns a 404 or empty result
- Requesting more than 50 entries returns a validation error
- Service unavailable if the Replit-hosted backend is down or cold-starting
- Payment failure (402) if USDC balance is insufficient for the $0.01 per-call fee
- Rate limiting if too many requests are made in a short window

## How this service works

Structured recent releases for one tracked vendor.

## Output

A JSON object containing structured recent release entries for Sentry, including version identifiers, release dates, and associated changelog content, up to the requested limit (default 10, max 50).

## 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-structured-recent-releases-for-sentry-be8007fe/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)