# Tollkit Transaction Lookup

> Tollkit Transaction Lookup is a paid API for AI agents from extract.tollkit.dev, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-10).

Given a transaction hash on Base, Ethereum, or Solana, returns full transaction details including status, block time, sender/receiver, ETH value, gas fee paid, and all decoded ERC-20 token transfers.

## Facts

- Endpoint: POST https://extract.tollkit.dev/chain/tx?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tollkit-transaction-lookup-192d6e26
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_-eTeLe-YREHVvNL781V05

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 tollkit-transaction-lookup-192d6e26 -d '<json body>'
```

Example prompt: Can you look up this Ethereum transaction for me — 0x4a3b2c1d... — and tell me whether it succeeded, how much ETH was moved, what the gas fee was, and if any ERC-20 tokens were transferred?

## When to prefer this

Choose this endpoint when you need a comprehensive, decoded view of a single transaction including ERC-20 transfer logs — especially for DeFi swaps, token payments, or debugging reverts. It covers Base, Ethereum, and Solana. Prefer it over raw RPC calls when you want human-readable decoded token amounts and symbols without manually decoding ABI logs. It is cost-effective at $0.002/call with no charge for missing hashes.

## Known failure modes

- Transaction hash not found on the specified chain — not charged, returns a not-found response
- Malformed or invalid hash format — rejected by schema validation before payment
- Transaction is still pending — status returned as pending with partial data
- Wrong chain specified — hash exists on a different chain but returns not-found on the requested one
- Node/RPC unavailability causing a temporary lookup failure

## How this service works

Transaction lookup on Base or Ethereum: give a tx hash, get its status (success, reverted, pending), block time, from, to, ETH value, fee paid and every ERC-20 transfer it made, decoded with token symbols and amounts. $0.003 per call; a hash that isn't found is not charged.

## Output

Returns the transaction's execution status (success, reverted, or pending), block timestamp, sender address (from), recipient address (to), native ETH value transferred, total gas fee paid in ETH, and a list of every ERC-20 token transfer decoded from the logs — each with the token symbol, human-readable amount, sender, and recipient.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "hash": {
   "type": "string",
   "pattern": "^(0x[0-9a-fA-F]{64}|[1-9A-HJ-NP-Za-km-z]{64,88})$",
   "description": "Transaction hash, or base58 signature on Solana."
  },
  "chain": {
   "enum": [
    "base",
    "ethereum",
    "solana"
   ],
   "type": "string",
   "default": "base",
   "description": "Which chain to read: \"base\" (default), \"ethereum\" or \"solana\"."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tollkit-transaction-lookup-192d6e26/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from extract.tollkit.dev](https://www.zero.xyz/host/extract.tollkit.dev/llms.txt)