# EVM Transaction Receipt Lookup

> EVM Transaction Receipt Lookup is a paid API for AI agents from ai-data-marketplace-1042299154756.us-central1.run.app, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-15).

Fetches the on-chain receipt for a given EVM transaction hash, including status, gas used, and event logs, across Base, Ethereum, or Arbitrum.

## Facts

- Endpoint: GET https://ai-data-marketplace-1042299154756.us-central1.run.app/api/v1/evm_receipt
- Price: $0.003/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-receipt-lookup-60990ed7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_hFHdaPtjPmgOl9tIp5AmH

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-60990ed7
```

Example prompt: Can you check whether the transaction 0x91698c8339b23372096c31fe065bfa0a73988d1b5969447986b3b1b3a7960d06 was successful on Base and tell me how much gas it used?

## When to prefer this

Choose this endpoint when you need a quick, pay-per-use lookup of an EVM transaction receipt without managing your own RPC node or blockchain SDK. It is ideal for AI agents confirming payment finality, auditing gas costs, or debugging failed transactions on Base, Ethereum, or Arbitrum with a simple HTTP GET and micro-USDC billing via x402.

## Known failure modes

- Invalid or malformed transaction hash returns an error
- Transaction hash not found on the specified chain returns no receipt
- Unsupported chain value returns a validation error
- Network RPC timeout or node unavailability may cause delayed or failed responses
- Omitting required transaction_hash parameter returns a 400-level error

## How this service works

Retrieve a real transaction receipt with execution status, gas consumption, contract creation address, bloom, and complete event logs.

## Output

Returns a JSON object with a success boolean, the network name, and a receipt object containing the transaction hash, integer status code (1 = success, 0 = failure), a boolean successful flag, gas_used as a string, and an array of event logs emitted by the transaction.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "transaction_hash"
     ],
     "properties": {
      "chain": {
       "type": "string",
       "description": "base, ethereum, or arbitrum; defaults to base."
      },
      "transaction_hash": {
       "type": "string",
       "description": "32-byte 0x-prefixed transaction hash."
      }
     },
     "additionalProperties": true
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "required": [
      "success",
      "network",
      "receipt"
     ],
     "properties": {
      "network": {
       "type": "string"
      },
      "receipt": {
       "type": "object",
       "required": [
        "transaction_hash",
        "status",
        "successful",
        "gas_used",
        "logs"
       ],
       "properties": {
        "logs": {
         "type": "array",
         "items": {}
        },
        "status": {
         "type": "integer"
        },
        "gas_used": {
         "type": "string"
        },
        "successful": {
         "type": "boolean"
        },
        "transaction_hash": {
         "type": "string"
        }
       },
       "additionalProperties": true
      },
      "success": {
       "type": "boolean"
      }
     },
     "additionalProperties": true
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "network": "base",
  "receipt": {
   "logs": [],
   "status": 1,
   "gas_used": "46218",
   "successful": true,
   "transaction_hash": "0x91698c8339b23372096c31fe065bfa0a73988d1b5969447986b3b1b3a7960d06"
  },
  "success": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/evm-transaction-receipt-lookup-60990ed7/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from ai-data-marketplace-1042299154756.us-central1.run.app](https://www.zero.xyz/host/ai-data-marketplace-1042299154756.us-central1.run.app/llms.txt)