# LogicNodes EVM Transaction Receipt Lookup

> LogicNodes EVM Transaction Receipt Lookup is a paid API for AI agents from logicnodes.io, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-28).

Fetches the full transaction receipt for an EVM transaction hash on a specified chain

## Facts

- Endpoint: POST https://logicnodes.io/paid/v1/tools/evm_tx_receipt?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-28
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/logicnodes-evm-transaction-receipt-lookup-1d7b6ec5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_N-Pa7YjBbBxn2dunn3hIV

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 logicnodes-evm-transaction-receipt-lookup-1d7b6ec5 -d '<json body>'
```

Example prompt: Can you pull the transaction receipt for hash 0xabc123...def on Base (chain eip155:8453) and tell me if it succeeded and how much gas was used?

## When to prefer this

Choose this endpoint when you need authoritative, exact transaction receipt data for EVM-compatible chains and want a simple pay-per-call model without managing your own RPC infrastructure. It supports 14+ chains via a single unified API, avoiding the need to configure separate RPC providers per chain. Prefer it over raw RPC calls when operating as an AI agent that needs reliable, structured responses rather than raw JSON-RPC output.

## Known failure modes

- Transaction hash not found on the specified chain — returns error response
- Invalid or unrecognized chain ID format (chain names are rejected, must use CAIP-2 eip155:X or numeric string)
- Transaction still pending and not yet mined — receipt unavailable
- Malformed transaction hash — returns validation error
- Unsupported chain ID not in LogicNodes' supported network list
- Network timeout or RPC node unavailability on the target chain

## How this service works

Exact answers for AI agents: 40+ tools for EVM chains and Aptos, gas on 14 chains, never a guess. Free tier; pay per call in USDC (x402) on 13 networks.

## Output

Returns a JSON object with ok: true and a tool field, plus the full EVM transaction receipt including status (success/failure), block number, gas used, cumulative gas used, logs array with event data, contract address (for deployments), and other standard receipt fields for the given transaction hash on the specified chain.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "hash": {
   "type": "string"
  },
  "chain": {
   "type": "string",
   "description": "EVM CAIP-2 chain id such as eip155:8453, or a bare chain id number as a string. Chain names are refused."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "tool": "evm_tx_receipt"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/logicnodes-evm-transaction-receipt-lookup-1d7b6ec5/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from logicnodes.io](https://www.zero.xyz/host/logicnodes.io/llms.txt)