# Axiomworks EVM Transaction Receipt Lookup

> Axiomworks EVM Transaction Receipt Lookup is a paid API for AI agents from api.axiomworks.co.uk, paid per call via x402, $0.002/call, status unknown (last checked 2026-11-12).

Fetches raw transaction receipt data for an EVM transaction hash, including success/revert status, gas used, effective gas price, fee in native coin, contract created, and raw logs.

## Facts

- Endpoint: GET https://api.axiomworks.co.uk/chain/receipt?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/axiomworks-evm-transaction-receipt-lookup-86dbc114
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_VoqK61NSTmzpNtz1FaHr9

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 axiomworks-evm-transaction-receipt-lookup-86dbc114
```

Example prompt: Can you pull the transaction receipt for 0x6f0d9bbb400eef11b67d1b9b41a5b9053b6790f254a3e9dea264dd1a8ded6a73 on Base — I need to know if it succeeded, how much gas was used, the fee in ETH, and the raw logs?

## When to prefer this

Use this endpoint when you need raw transaction receipt data including gas metrics, fee amounts, and raw logs for any EVM transaction on Base, Ethereum, Arbitrum, Optimism, or Polygon. Prefer this over the /tx endpoint when you don't need decoded transfer details or confirmation counts and want to minimise cost ($0.002 vs $0.003). Ideal for debugging, auditing, or verifying on-chain events at the receipt level.

## Known failure modes

- Invalid transaction hash format (not 0x + 64 hex chars) returns a validation error
- Transaction hash not found on the specified chain returns an empty or not-found response
- Unsupported chain value returns an enum validation error
- Network or RPC node timeout may cause slow or failed lookups
- Transaction still pending may return incomplete or null receipt

## How this service works

Transaction receipt via eth_getTransactionReceipt: success/revert status, gas used, effective gas price, fee in native coin, contract created, log count + raw logs. Example: {hash:"0x…", chain:"base"}. Use /tx ($0.003) for decoded transfers + confirmations. $0.002.

## Output

Returns a JSON object containing: transaction status (success/reverted), block number, from/to addresses, gas used, effective gas price in gwei, fee in native coin (ETH/POL etc.) with symbol, contract created address (or null), log count, and an array of raw log objects each with address, topics, data, and log index. Also includes chain name and chain ID.

## 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": [
      "hash"
     ],
     "properties": {
      "hash": {
       "type": "string",
       "pattern": "^0x[0-9a-fA-F]{64}$"
      },
      "chain": {
       "enum": [
        "base",
        "ethereum",
        "arbitrum",
        "optimism",
        "polygon"
       ],
       "type": "string",
       "description": "EVM chain (default base)"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "properties": {
      "fee": {
       "type": "string"
      },
      "logs": {
       "type": "array"
      },
      "status": {
       "type": "string"
      },
      "gas_used": {
       "type": "number"
      }
     }
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "to": "0x833589fcd6edb6e08f4c7c32d4f71b54bda02913",
  "fee": "0.00000182451241203",
  "from": "0x14fda13953fc30428938e6bf950d036e77214e52",
  "hash": "0x6f0d9bbb400eef11b67d1b9b41a5b9053b6790f254a3e9dea264dd1a8ded6a73",
  "logs": [
   {
    "data": "0x",
    "topics": [
     "0x98de503528ee59b575ef0c0a2576a82497bfc029a5685b209e9ec333479b10a5",
     "0x000000000000000000000000defe5f9f39d0f0a5f3c83594cd65a8e70015b370"
    ],
    "address": "0x833589fcd6edb6e08f4c7c32d4f71b54bda02913",
    "log_index": 435
   },
   {
    "data": "0x00000000000000000000000000000000000000000000000000000000000003e8",
    "topics": [
     "0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef",
     "0x000000000000000000000000defe5f9f39d0f0a5f3c83594cd65a8e70015b370"
    ],
    "address": "0x833589fcd6edb6e08f4c7c32d4f71b54bda02913",
    "log_index": 436
   }
  ],
  "block": 53551715,
  "chain": "base",
  "status": "success",
  "chain_id": 8453,
  "gas_used": 86226,
  "log_count": 2,
  "fee_symbol": "ETH",
  "contract_created": null,
  "effective_gas_price_gwei": 0.021159655
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/axiomworks-evm-transaction-receipt-lookup-86dbc114/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.axiomworks.co.uk](https://www.zero.xyz/host/api.axiomworks.co.uk/llms.txt)
