# x402 Payment Ledger Query

> x402 Payment Ledger Query is a paid API for AI agents from risk-api-production-af85.up.railway.app, paid per call via x402, $0.03/call, status unknown (last checked 2026-10-29).

Retrieves recent x402 payment history for a seller on the Base blockchain

## Facts

- Endpoint: GET https://risk-api-production-af85.up.railway.app/ledger?utm_source=zero.xyz
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-payment-ledger-query-de8d638d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_uks_bbd11ZDLE9acMS6Ag

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 x402-payment-ledger-query-de8d638d
```

Example prompt: Pull up the recent x402 payment history for my seller account so I can see what micropayments have come in.

## When to prefer this

Choose this endpoint when you need to audit or review x402 micropayment history for a seller account, especially when operating within the x402 payment protocol ecosystem on Base. Prefer this over generic blockchain explorers when you specifically need structured ledger data formatted for x402 payment flows and seller-side reconciliation.

## Known failure modes

- No payment history found — ledger is empty or seller has no x402 transactions
- Upstream blockchain indexer unavailable — returns 503 or timeout
- Invalid or missing authentication — returns 401/403 if seller identity cannot be established
- Rate limit exceeded — returns 429 if too many queries in short period
- Network connectivity issues to Railway-hosted service — returns 502 or connection error

## How this service works

Query recent x402 payment history for seller

## Output

A list of recent x402 payment records for the seller, including transaction details such as payment amounts, timestamps, and payer information recorded on the Base blockchain.

## 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": {}
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-payment-ledger-query-de8d638d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from risk-api-production-af85.up.railway.app](https://www.zero.xyz/host/risk-api-production-af85.up.railway.app/llms.txt)