# EVM Transaction Receipt Lookup

> EVM Transaction Receipt Lookup is a paid API for AI agents from twin.unykorn.org, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-01).

Fetches a transaction receipt for a given EVM transaction hash on any of 10 supported chains, returning success/failure status, gas cost, and emitted events.

## Facts

- Endpoint: POST https://twin.unykorn.org/evm-receipt?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/evm-transaction-receipt-lookup-fc3cdb29
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_WFERGOncvhley6dF1OalH

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-fc3cdb29 -d '<json body>'
```

Example prompt: Can you check whether my transaction 0x3a1b2c...64hex went through on Base, and tell me if it succeeded and how much it cost?

## When to prefer this

Choose this endpoint when you need a single-call, pay-per-query lookup of an EVM transaction receipt across any of 10 major chains without managing your own RPC infrastructure. It is especially useful when you need the USD cost denomination alongside raw receipt data, or when querying chains (e.g. Linea, Scroll, Gnosis) where free public RPCs are unreliable.

## Known failure modes

- Invalid transaction hash format (not a 0x-prefixed 64-hex string) returns a validation error
- Unsupported chain name returns an enum validation error
- Transaction not yet mined or not found on the specified chain returns a not-found error
- Upstream RPC node timeout may cause delayed or failed responses
- Payment failure via x402 protocol results in 402 response before execution

## How this service works

Transaction receipt — did it succeed, what did it cost, what did it emit — Genesis402 / UnyKorn Operator Network

## Output

Returns a JSON object with a boolean success flag, the transaction hash, the USD cost of the transaction, a receipt ID prefixed with 'g402-', and an ISO 8601 timestamp of when the receipt was generated.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "params": {
   "type": "object",
   "properties": {
    "hash": {
     "type": "string",
     "pattern": "^0x[0-9a-fA-F]{64}$"
    },
    "chain": {
     "enum": [
      "ethereum",
      "base",
      "polygon",
      "arbitrum",
      "optimism",
      "bsc",
      "avalanche",
      "gnosis",
      "linea",
      "scroll"
     ],
     "type": "string"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "type": "evm-receipt",
  "receipt": {
   "tx_hash": "0x<64hex>",
   "amount_usd": 0.003,
   "receipt_id": "g402-<16hex>"
  },
  "generated_at": "<iso8601>"
 }
}
```

## More

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