# Onchain Toolkit - Transaction Status Lookup

> Onchain Toolkit - Transaction Status Lookup is a paid API for AI agents from onchain-toolkit.bowling-anthony.workers.dev, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-15).

Fetches the status, block, sender, recipient, value, gas used, and fee paid for a blockchain transaction by hash.

## Facts

- Endpoint: GET https://onchain-toolkit.bowling-anthony.workers.dev/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/onchain-toolkit-transaction-status-lookup-4836ee64
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_AY_mlF2ISSvVPQsx4L-Ld

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-toolkit-transaction-status-lookup-4836ee64
```

Example prompt: Can you check the status of this transaction — was it successful, and how much gas and fee did it actually end up paying? The tx hash is 0xabc123...

## When to prefer this

Use this endpoint when you need a quick, low-cost single-transaction status and detail lookup on a blockchain, especially for confirming payments, debugging failed transactions, or auditing fee data. It is well-suited for AI agents that need to programmatically verify on-chain activity without running a full node. Prefer this over block explorer UIs when you need structured, parseable data in an agent workflow.

## Known failure modes

- Transaction hash not found or invalid — returns an error or empty result
- Network/chain not specified or unsupported — may default to one chain or return an error
- Transaction is still pending — status returned as pending with limited fields
- Rate limiting or payment failure for the $0.001 USDC per-call fee
- Malformed query parameters leading to a 400 bad request

## How this service works

Whether a transaction succeeded, failed or is pending, with block, sender, recipient, value, gas used and the fee actually paid.

## Output

Returns whether the transaction succeeded, failed, or is pending, along with the block number it was included in, the sender and recipient addresses, the value transferred, gas used, and the actual fee paid in native currency.

## 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"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "status": "success",
  "blockNumber": 50372336
 }
}
```

## More

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