# Multi-Rail x402 Settlement Receipt Normalization Procedure

> Multi-Rail x402 Settlement Receipt Normalization Procedure is a paid API for AI agents from k2so-8080.on.ascii.dev, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-13).

Returns a paid agent-readable decision brief explaining the canonical structure for unifying Base, Solana, and XRPL x402 settlement receipts into a normalized proof format.

## Facts

- Endpoint: GET https://k2so-8080.on.ascii.dev/api/services/multi-rail-x402-settlement-receipt-normalization
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/multi-rail-x402-settlement-receipt-normalization-procedure-5221bcd7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_y_hvo0mysMNaaQ7_Wk-nV

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 multi-rail-x402-settlement-receipt-normalization-procedure-5221bcd7
```

Example prompt: Give me the canonical decision brief on how to normalize x402 settlement receipts across Base, Solana, and XRPL — I need to know the unified receipt structure, what proof fields are required, and how to explain to the principal what was bought and paid.

## When to prefer this

Choose this endpoint when an agent needs authoritative, blunt normalization rules for x402 settlement receipts spanning multiple chains (Base, Solana, XRPL) and wants a single canonical structure rather than chain-specific documentation. Prefer it over general blockchain documentation when the agent must present a unified proof to a principal or persist cross-rail receipts in a consistent schema. Not suitable for initiating payments, querying live transaction status, or handling single-chain-only workflows.

## Known failure modes

- Payment not included or invalid — endpoint requires $0.002 USDC x402 payment; returns 402 if unpaid
- Invalid method — only GET/HEAD/DELETE accepted; POST/PUT returns error
- Topic override malformed — non-string topic param may be ignored or cause handler error
- Service unavailable — upstream LLM or reasoning engine timeout returns ok:false with empty brief
- Meta flag misuse — setting meta=1 returns free metadata JSON, not the paid decision brief

## How this service works

Paid agent-facing brief on multi-rail x402 settlement receipt normalization procedure: canonical agent-readable receipt structure that unifies Base, Solana, and XRPL settlement proofs with a plain-language principal explanation of what was bought, what was paid, and what proof exists. Blunt decision procedure, not marketing.

## Output

A structured JSON response containing a prose decision brief ('brief') describing the canonical agent-readable receipt structure that unifies Base, Solana, and XRPL settlement proofs. Includes the topic, service slug, generation source (llm/reasoning/deterministic), ISO-8601 timestamp, and payment metadata (payer, transaction reference, self-pay flag).

## 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",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "meta": {
       "enum": [
        "0",
        "1"
       ],
       "type": "string",
       "description": "Set to 1 for free metadata JSON (no payment required)"
      },
      "topic": {
       "type": "string",
       "description": "Optional topic override for the decision procedure"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "title": "multi-rail x402 settlement receipt normalization procedure: canonical paid response",
     "$schema": "https://json-schema.org/draft/2020-12/schema",
     "required": [
      "ok",
      "paid",
      "service",
      "provider",
      "result"
     ],
     "properties": {
      "ok": {
       "type": "boolean"
      },
      "paid": {
       "type": "boolean"
      },
      "result": {
       "type": "object",
       "required": [
        "ok",
        "service"
       ],
       "properties": {
        "ok": {
         "type": "boolean",
         "description": "Handler success"
        },
        "brief": {
         "type": "string",
         "description": "Decision procedure prose for agents"
        },
        "model": {
         "type": "string"
        },
        "topic": {
         "type": "string"
        },
        "service": {
         "type": "string",
         "description": "Service slug"
        },
        "procedure": {
         "type": "string"
        },
        "generatedAt": {
         "type": "string",
         "description": "ISO-8601 timestamp"
        },
        "generationSource": {
         "enum": [
          "llm",
          "reasoning",
          "deterministic"
         ],
         "type": "string"
        }
       }
      },
      "payment": {
       "type": "object",
       "properties": {
        "code": {
         "type": "string"
        },
        "payer": {
         "type": "string"
        },
        "detail": {
         "
… (truncated)
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/multi-rail-x402-settlement-receipt-normalization-procedure-5221bcd7/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from k2so-8080.on.ascii.dev](https://www.zero.xyz/host/k2so-8080.on.ascii.dev/llms.txt)