# Changelog State API – Recent Releases for Vendor (Near)

> Changelog State API – Recent Releases for Vendor (Near) 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-10-22).

Returns structured recent release entries for the 'near' vendor slug tracked by the Changelog State API, with pagination support.

## Facts

- Endpoint: GET https://changelog-state-api.replit.app/api/monitors/near?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-22
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/changelog-state-api-recent-releases-for-vendor-near-e0d6bfaa
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_LsDlBSgu8xHKla6bBDCZB

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-recent-releases-for-vendor-near-e0d6bfaa
```

Example prompt: Can you pull the 10 most recent structured releases for the Near vendor from the Changelog State API so I can see what's changed lately?

## When to prefer this

Use this endpoint when you specifically need structured, paginated release data for the Near vendor from the Changelog State API. It is ideal for agents that need to programmatically walk through Near's release history newest-first, or when you want stable cursor-based pagination that won't shift under you as new releases arrive. Prefer this over generic web scraping when you need clean, structured release metadata rather than raw HTML.

## Known failure modes

- 400 Bad Request if cursor token is malformed or was issued for a different vendor
- 404 if the vendor slug 'near' is not tracked
- Payment failure if USDC balance is insufficient for the $0.01 per-call fee
- Empty results array if the vendor has no tracked releases yet
- Rate limiting or server error from Replit-hosted infrastructure

## How this service works

Structured recent releases for one tracked vendor.

## Output

A JSON object containing a list of structured recent release entries for the Near vendor, each with metadata such as version, publish date, and changelog details, plus an opaque nextCursor token for pagination to retrieve older entries.

## 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 that names no vendor and never returns data. 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-recent-releases-for-vendor-near-e0d6bfaa/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)