# EVM Transaction Lookup by Hash

> EVM Transaction Lookup by Hash 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-15).

Fetches merged transaction details and receipt (from, to, value, gas used, status, block) for a given transaction hash on EVM-compatible chains in a single call.

## Facts

- Endpoint: POST https://flat-rate-llm.kikoribera03.workers.dev/v1/evm/tx
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/evm-transaction-lookup-by-hash-438d85f5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_YuH2FVme7LeK8k8W4rAvw

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-lookup-by-hash-438d85f5 -d '<json body>'
```

Example prompt: Can you look up the Ethereum transaction 0xabc123...def456 and tell me whether it succeeded, how much gas it used, and which block it landed in?

## When to prefer this

Use this endpoint when you need both transaction details and receipt data in a single call without managing two separate RPC requests. Ideal for agents that need to verify transaction finality, check success/failure status, or audit sender/receiver without running their own Ethereum node or managing API keys. Preferred over raw RPC when working across multiple EVM chains (Base, Ethereum, Polygon, Arbitrum, Optimism) from a single interface.

## Known failure modes

- Transaction hash not found on the specified chain — returns empty or error response
- Wrong chain specified — transaction exists on a different network and will not be found
- Malformed transaction hash — invalid hex string causes a 400 or validation error
- Chain not supported — only base, ethereum, polygon, arbitrum, optimism are valid chain values
- Transaction pending — not yet mined, so receipt fields may be null or absent

## 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 containing the destination address (to), sender address (from), transaction status (success or failure), gas used as a number, and block number where the transaction was confirmed.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "to": {
   "type": "string"
  },
  "from": {
   "type": "string"
  },
  "status": {
   "type": "string"
  },
  "gasUsed": {
   "type": "number"
  },
  "blockNumber": {
   "type": "number"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/evm-transaction-lookup-by-hash-438d85f5/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)