# Base Receipt Lookup

> Base Receipt Lookup is a paid API for AI agents from 402.com.tr, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-14).

Retrieves the full receipt for a Base blockchain transaction by hash, including success/revert status, block, gas used, fees, logs, and contract deployment address.

## Facts

- Endpoint: GET https://402.com.tr/api/x402/base-receipt
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/base-receipt-lookup-98049e3a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_LEt25z6FsaqsWEvWmIMz4

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-lookup-98049e3a
```

Example prompt: Can you pull up the receipt for Base transaction 0x4a3b…f9c2 and tell me whether it succeeded or reverted, how much gas it used, and what the fee was in ETH?

## When to prefer this

Use this endpoint when you need structured, detailed receipt data for a specific Base transaction — especially when you need fee breakdowns in both wei and ETH, emitted log metadata, or deployed contract addresses. Prefer it over general block explorers when building automated agents that need machine-readable receipt data without scraping. It also gracefully handles missing receipts by diagnosing pending vs dropped states rather than returning a generic error.

## Known failure modes

- Transaction hash not yet mined — endpoint returns pending/dropped/unknown diagnostic instead of receipt
- Invalid or malformed transaction hash — returns error indicating bad input
- Transaction submitted to a different network (e.g. Ethereum mainnet) — no receipt found on Base
- Hash typo or wrong case — no match found
- Payment failure (x402 protocol) — call not executed if USDC payment is insufficient

## How this service works

🆕 The receipt for a Base transaction: success or reverted, block, gas used, effective gas price, the fee in wei and ETH, how many logs it emitted and which contracts emitted them. A contract deployment reports the new address. No receipt yet means pending, dropped, or never here — and it says which is possible instead of failing.

## Output

Returns a structured receipt containing: success or reverted status, block number, gas used, effective gas price, transaction fee in both wei and ETH, count of emitted logs, list of contracts that emitted logs, and (for deployments) the new contract address. If no receipt exists, returns a diagnostic explanation indicating whether the transaction is pending, dropped, or was never submitted to Base.

## 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"
    },
    "pathParams": {
     "type": "object"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "hash"
     ],
     "properties": {
      "hash": {
       "type": "string",
       "description": "Transaction hash"
      }
     }
    }
   },
   "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/base-receipt-lookup-98049e3a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from 402.com.tr](https://www.zero.xyz/host/402.com.tr/llms.txt)