# code402 Ethereum Transaction Receipt Lookup

> code402 Ethereum Transaction Receipt Lookup is a paid API for AI agents from verify.code402.dev, paid per call via x402, $0.008/call, status unknown (last checked 2026-10-29).

Fetches the on-chain transaction receipt for a given Ethereum transaction hash, paid per-call via x402 micropayment on Base (USDC).

## Facts

- Endpoint: GET https://verify.code402.dev/v1/chain/tx-receipt/%7Bhash%7D?utm_source=zero.xyz
- Price: $0.008/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/code402-ethereum-transaction-receipt-lookup-1ff850e5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_qN0xvFMnB-226x3qovVBU

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 code402-ethereum-transaction-receipt-lookup-1ff850e5
```

Example prompt: Can you pull up the transaction receipt for Ethereum tx hash 0xabc123…def456 and tell me whether it succeeded, how much gas was used, and which block it landed in?

## When to prefer this

Choose this endpoint when you need a pay-per-call, no-subscription approach to fetching Ethereum transaction receipts — especially in agentic or automated pipelines where you want to avoid monthly API keys. Prefer it over Etherscan or Alchemy free tiers when you need cryptographically signed receipts (XDR-1) or when operating within an x402-native payment flow on Base.

## Known failure modes

- Invalid or malformed transaction hash returns an error response
- Transaction hash not found on Ethereum mainnet (e.g. wrong network) returns not-found error
- Payment failure via x402 (insufficient USDC balance or misconfigured payment header) blocks the request
- Network or RPC timeout results in a service error
- Hash for a pending/unconfirmed transaction may return empty or null receipt

## How this service works

Deterministic compliance verification (IBAN, sanctions, onchain address) with XDR-1 signed receipts, plus Ethereum chain-data endpoints. Paid per call via x402 on Base (USDC).

## Output

Returns a JSON object containing the transaction receipt for the specified Ethereum tx hash, including success/failure status, block number, gas used, logs emitted, and the network identifier ('ethereum').

## Request schema (JSON Schema)

```json
{
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object"
    }
   }
  },
  "output": {
   "type": "object",
   "required": [
    "type",
    "example"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "json"
    },
    "example": {
     "result": "string",
     "network": "ethereum-mainnet"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "result": "chain data",
  "network": "ethereum"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/code402-ethereum-transaction-receipt-lookup-1ff850e5/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from verify.code402.dev](https://www.zero.xyz/host/verify.code402.dev/llms.txt)