# Agent Paywire Changes Feed

> Agent Paywire Changes Feed is a paid API for AI agents from api.agentpaywire.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-27).

Returns a filtered, time-windowed feed of new or updated entries in the AI agent payment protocols library, including stablecoins and machine-to-machine payment resources.

## Facts

- Endpoint: GET https://api.agentpaywire.com/v1/changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-27
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-paywire-changes-feed-e0833dd5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_5KToW2jbRyxTgPd5tVXff

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 agent-paywire-changes-feed-e0833dd5
```

Example prompt: Pull the Agent Paywire changes feed for everything new or updated since January 1st, 2026, filtered to L402 protocol entries, and return it as JSON.

## When to prefer this

Use this endpoint when you need a structured, filterable changelog of AI agent payment protocol resources — especially when you want to track what's new or updated since a specific date, filter by protocol (e.g. L402, x402), or integrate a recurring monitoring workflow. Prefer this over the general updates endpoint when you need date-windowed, protocol-specific change tracking rather than a broad content snapshot.

## Known failure modes

- Missing required 'since' parameter returns a 400 error
- Invalid date format (non-YYYY-MM-DD) causes a parse error
- Unknown protocol tag or category ID returns an empty result set rather than an error
- 'until' date earlier than 'since' date may return zero results
- Network or payment failure (x402) prevents access to the endpoint

## How this service works

Library sources that are new or updated in an inclusive date window. since (YYYY-MM-DD) is optional and defaults to the last 7 UTC days through today. Optional until, protocols, categories, type (new or updated), and format (json or markdown). A probe without header X-APW-Trial: 1 or query trial=1 is this paid challenge. One request is 0.01 USDC.

## Output

A JSON object containing a count of matching changes, the queried date window, and an array of protocol-grouped change entries. Each entry includes an ID, URL, title, change type (new or updated), verification date, and publication date.

## 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"
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "type": {
       "enum": [
        "new",
        "updated"
       ],
       "type": "string",
       "description": "new or updated. Optional."
      },
      "since": {
       "type": "string",
       "description": "Inclusive window start, YYYY-MM-DD. Optional. Omitted, the window is the last 7 UTC days through today. A probe without header X-APW-Trial: 1 or trial=1 is HTTP 402 and returns a count and the first three ids and titles. Do not send trial on a probe."
      },
      "until": {
       "type": "string",
       "description": "Inclusive window end, YYYY-MM-DD. Optional."
      },
      "format": {
       "enum": [
        "json",
        "markdown"
       ],
       "type": "string",
       "description": "json or markdown. Optional. Default json."
      },
      "protocols": {
       "type": "string",
       "description": "Comma-separated library tags. Optional."
      },
      "categories": {
       "type": "string",
       "description": "Comma-separated library category ids. Optional."
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "required": [
      "since",
      "count",
      "groups"
     ],
     "properties": {
      "count": {
       "type": "integer"
      },
      "since": {
       "type": "string"
      },
      "until": {
       "type": [
        "string",
        "null"
       ]
      },
      "groups": {
       "type": "array"
      }
     }
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "count": 1,
  "since": "2026-10-01",
  "until": null,
  "groups": [
   {
    "count": 1,
    "changes": [
     {
      "id": "lightning-labs-l402-for-agents",
      "url": "https://lightning.engineering/posts/2026-03-11-L402-for-agents/",
      "title": "The Future Is Now: Why L402 Is the Internet-Native Payments Protocol for Agents",
      "change_type": "updated",
      "verified_at": "2026-10-20",
      "date_published": "2026-03-11"
     }
    ],
    "protocol": "l402"
   }
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-paywire-changes-feed-e0833dd5/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.agentpaywire.com](https://www.zero.xyz/host/api.agentpaywire.com/llms.txt)