# Base Receipt Normalizer

> Base Receipt Normalizer is a paid API for AI agents from cooper-confidentiality-guardian-spirituality.trycloudflare.com, paid per call via x402, $0.001/call, status down (last checked 2026-09-15).

Normalizes a Base blockchain transaction receipt into a compact, human-readable status summary

## Facts

- Endpoint: POST https://cooper-confidentiality-guardian-spirituality.trycloudflare.com/api/base-receipt-normalizer-v1
- Price: $0.001/call
- Payment: x402
- Status: down
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/base-receipt-normalizer-0ec6dcb0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_TyJcFPHRAMjVkJSnUJLhi

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 base-receipt-normalizer-0ec6dcb0 -d '<json body>'
```

Example prompt: Can you normalize this Base transaction receipt and give me a compact status summary for hash 0x3a1b2c4d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a0b1c2d3e4f5a6b7c8d9e0f1a2b?

## When to prefer this

Use this endpoint when you have a Base blockchain transaction hash and need a quick, normalized status summary without parsing raw EVM receipt data yourself. Prefer this over manual RPC calls when you want a compact, structured output rather than raw JSON-RPC receipt blobs.

## Known failure modes

- Invalid transaction hash format (not matching 0x[64 hex chars]) — likely 400 validation error
- Transaction hash not found on Base network — likely 404 or empty result
- Base node connectivity issues — likely 503 or timeout
- Payment not included or insufficient — 402 Payment Required

## How this service works

Normalize a Base transaction receipt into a compact status summary.

## Output

A compact status summary of the Base transaction, derived from the raw on-chain receipt. Likely includes fields such as transaction status (success/failure), block number, gas used, and other normalized metadata extracted from the receipt.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "transactionHash": {
   "type": "string",
   "pattern": "^0x[0-9a-fA-F]{64}$",
   "description": "Base transaction hash to normalize"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/base-receipt-normalizer-0ec6dcb0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from cooper-confidentiality-guardian-spirituality.trycloudflare.com](https://www.zero.xyz/host/cooper-confidentiality-guardian-spirituality.trycloudflare.com/llms.txt)
