# Ethereum Transaction Receipt Lookup

> Ethereum Transaction Receipt Lookup is a paid API for AI agents from agent-data-tools.revmesh2074.workers.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-30).

Fetches a parsed transaction receipt for a given Ethereum transaction hash, including status, gas used, fees, block number, and log count.

## Facts

- Endpoint: GET https://agent-data-tools.revmesh2074.workers.dev/eth/receipt?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-30
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ethereum-transaction-receipt-lookup-d288a586
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_oqZ3NPOSIGBMJqmgKOXvy

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 ethereum-transaction-receipt-lookup-d288a586
```

Example prompt: Can you pull up the receipt for Ethereum transaction 0x9531467e03a57bbb5cd080439ac3b10c0cefed147282eb2ff709b02c897afcbf and tell me if it succeeded, what block it landed in, and how much gas was used?

## When to prefer this

Use this endpoint when you need fast, cheap ($0.001) per-call lookup of an Ethereum transaction receipt without setting up your own RPC node or API key. Ideal for agents that need to verify transaction outcomes, confirm gas costs, or check contract deployment results on Ethereum mainnet. Prefer this over raw RPC calls when you want a clean, normalized JSON response without handling raw hex decoding.

## Known failure modes

- Invalid or malformed transaction hash returns an error
- Transaction hash not found on the chain returns a not-found error
- Network or RPC provider downtime may cause timeouts
- Hash from a different chain than Ethereum may return no result or incorrect data

## How this service works

Transaction receipt on Ethereum (eth_getTransactionReceipt): success or reverted, gas used, effective gas price, fee paid in ETH, number of event logs and any contract created. Use to confirm a payment or call went through; for sender, value and calldata use eth_tx. Input is a 0x-prefixed 64-hex hash; a pending or unknown hash returns 404, uncharged.

## Output

Returns a JSON object with: transaction hash, success/failure status, block number, chain name and chain ID, gas used (as a string), effective gas price in gwei, total fee paid in ETH, number of logs emitted, and contract address (if a contract was deployed, otherwise null).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "hash"
 ],
 "properties": {
  "hash": {
   "type": "string",
   "description": "0x-prefixed transaction hash (64 hex characters)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "fee": {
   "type": "string"
  },
  "hash": {
   "type": "string"
  },
  "logs": {
   "type": "number"
  },
  "block": {
   "type": "number"
  },
  "chain": {
   "type": "string"
  },
  "status": {
   "type": "string"
  },
  "chainId": {
   "type": "number"
  },
  "gasUsed": {
   "type": "string"
  },
  "contractAddress": {},
  "effectiveGasPriceGwei": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ethereum-transaction-receipt-lookup-d288a586/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent-data-tools.revmesh2074.workers.dev](https://www.zero.xyz/host/agent-data-tools.revmesh2074.workers.dev/llms.txt)