# EVM Transaction Receipt Lookup

> EVM Transaction Receipt Lookup is a paid API for AI agents from flat-rate-llm.kikoribera03.workers.dev, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-14).

Returns the receipt of an on-chain transaction: success/revert status, gas used, fee paid in Ether, and number of logs emitted, via eth_getTransactionReceipt.

## Facts

- Endpoint: POST https://flat-rate-llm.kikoribera03.workers.dev/v1/evm/receipt
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/evm-transaction-receipt-lookup-559fbb41
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_seGMeXpni_E2KiuQ6YOk6

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 evm-transaction-receipt-lookup-559fbb41 -d '<json body>'
```

Example prompt: Did my transaction 0x4a7f3b9e2c1d8f05a6b3e7c2d9f4a1b8e5c2d7f0a3b6e9c2d5f8a1b4e7c0d3f6 actually go through on Ethereum mainnet, and how much gas did it use?

## When to prefer this

Use this endpoint when you need a fast, pay-per-call lookup of a single transaction's on-chain outcome without managing your own RPC infrastructure. Ideal for agents that need to confirm whether a transaction succeeded, how much gas it consumed, or how many events it triggered, especially in automated workflows where you submit a tx and then need to poll for its receipt. Prefer this over general-purpose Ethereum RPC libraries when you want a clean JSON response with pre-computed feePaidEther without doing the arithmetic yourself.

## Known failure modes

- Transaction hash not yet mined — returns found: false if the tx is still pending or doesn't exist
- Invalid or malformed transaction hash — returns an error or found: false
- Unsupported chain ID — endpoint may return an error if the requested chain is not supported
- Network timeout or RPC node unavailability — may return a service error
- Querying a very old transaction on a pruned node — may not be found

## How this service works

60 paid endpoints with no metering, no API key and no account. Each endpoint has one flat price per call, whatever the size of the request: LLM completions with automatic failover across several large models, read-only EVM tooling over Base, Ethereum, Polygon, Arbitrum and Optimism, and pure crypto utilities that touch no network.

## Output

A JSON object indicating whether the transaction was found on-chain (found: true/false), its outcome (status: 'success' or 'reverted'), the amount of gas consumed (gasUsed), the actual fee paid denominated in Ether (feePaidEther), and the number of logs/events emitted (logs).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "hash"
 ],
 "properties": {
  "hash": {
   "type": "string",
   "description": "32-byte transaction hash."
  },
  "chain": {
   "type": "string",
   "description": "base | ethereum | polygon | arbitrum | optimism."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "logs": {
   "type": "number"
  },
  "found": {
   "type": "boolean"
  },
  "status": {
   "type": "string"
  },
  "gasUsed": {
   "type": "number"
  },
  "feePaidEther": {
   "type": "number"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/evm-transaction-receipt-lookup-559fbb41/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from flat-rate-llm.kikoribera03.workers.dev](https://www.zero.xyz/host/flat-rate-llm.kikoribera03.workers.dev/llms.txt)