# onchain Transaction Status Lookup

> onchain Transaction Status Lookup is a paid API for AI agents from onchain.x402utils.workers.dev, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-02).

Fetches on-chain transaction details (status, gas used, confirmations, value, block) for a given tx hash on Base or Ethereum.

## Facts

- Endpoint: GET https://onchain.x402utils.workers.dev/v1/tx?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/onchain-transaction-status-lookup-8b651fc7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_SdKhZSpPA4LE7MGDyel-R

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 onchain-transaction-status-lookup-8b651fc7
```

Example prompt: Can you check whether this Base transaction confirmed — hash is 0x4a3b2c1d8e9f0a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0c1d2e3f4a5b — and tell me how many confirmations it has?

## When to prefer this

Choose this endpoint when you need a lightweight, pay-per-call lookup of a specific transaction by hash on Base or Ethereum without standing up your own RPC node. Ideal for agents that need to verify payment settlement, debug failures, or check confirmation depth as a one-off read.

## Known failure modes

- Invalid or malformed tx hash returns an error
- Transaction not found on the specified chain returns 404 or empty result
- Network congestion may delay RPC response
- Specifying the wrong chain for a hash returns not-found
- Very recent transactions may show 0 confirmations or pending status

## How this service works

Live Base and Ethereum reads for AI agents: balances (ETH + USDC), gas, transaction status, ERC-20 metadata. $0.001 per call via x402 (USDC on Base).

## Output

A JSON object with the transaction's status (success/failed/pending), sender and recipient addresses, block number, ETH value transferred, gas used, and number of confirmations.

## 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",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "hash"
     ],
     "properties": {
      "hash": {
       "type": "string",
       "description": "0x-prefixed 32-byte tx hash"
      },
      "chain": {
       "enum": [
        "base",
        "ethereum"
       ],
       "type": "string",
       "description": "base (default) or ethereum"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "to": "0x…",
  "from": "0x…",
  "block": 39000000,
  "status": "success",
  "gas_used": 21000,
  "value_eth": "0.0",
  "confirmations": 12
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/onchain-transaction-status-lookup-8b651fc7/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from onchain.x402utils.workers.dev](https://www.zero.xyz/host/onchain.x402utils.workers.dev/llms.txt)