# Aether Base Transaction Receipt Lookup

> Aether Base Transaction Receipt Lookup is a paid API for AI agents from aether-x402.vercel.app, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-12).

Fetches decoded receipt data for a Base blockchain transaction by hash, including gas used and token transfers.

## Facts

- Endpoint: POST https://aether-x402.vercel.app/v1/base/receipt?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/aether-base-transaction-receipt-lookup-280abc30
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_bKL-uzMwyhF5yoYrEQhXV

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 aether-base-transaction-receipt-lookup-280abc30 -d '<json body>'
```

Example prompt: Can you pull the receipt for Base transaction 0x4a3b...c9f2 and tell me what token transfers happened and how much gas it used?

## When to prefer this

Use this endpoint when you need decoded receipt data for a specific Base (Coinbase L2) transaction — especially token transfer details and gas usage — and want to pay per-call in USDC via x402 without managing API keys. Prefer this over general-purpose block explorers when operating in an autonomous agent context that supports x402 micropayments.

## Known failure modes

- Invalid or malformed transaction hash returns a validation error
- Transaction hash not found on Base returns a not-found error
- Network or RPC issues may cause timeouts
- Hash from a different chain (e.g. Ethereum mainnet) will return no data or error
- Payment failure via x402 if USDC balance is insufficient

## How this service works

Pay-per-call Base onchain data, token risk verdicts and x402 payability audits over x402 (USDC on Base).

## Output

Returns a JSON object with transaction status (success/failure), total gas used, and an array of token transfer events each containing sender address, recipient address, token contract address, and value transferred.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "status": "success",
  "gasUsed": "52000",
  "transfers": [
   {
    "to": "0x...",
    "from": "0x...",
    "token": "0x...",
    "value": "1000000"
   }
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/aether-base-transaction-receipt-lookup-280abc30/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from aether-x402.vercel.app](https://www.zero.xyz/host/aether-x402.vercel.app/llms.txt)