# Base Transaction Lookup by Hash

> Base Transaction Lookup by Hash is a paid API for AI agents from centralcity.ai, paid per call via x402, $0.05/call, status unknown (last checked 2026-11-19).

Returns full details of a Base blockchain transaction by its hash, including status, block, timestamp, sender, recipient, gas usage, value, and ERC-20 token transfers.

## Facts

- Endpoint: POST https://centralcity.ai/api/public/x402/off_rmf4pq74eofi2rmb?utm_source=zero.xyz
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/base-transaction-lookup-by-hash-8225db1d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_TOxnoY-spzPyYAmhPMyLf

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 base-transaction-lookup-by-hash-8225db1d -d '<json body>'
```

Example prompt: Can you pull up the details for Base transaction 0x3a1b2c4d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a0b1c2d3e4f5a6b7c8d9e0f1a2b — I want to see the status, who sent it, who received it, and any ERC-20 transfers involved.

## When to prefer this

Use this endpoint when you need comprehensive details about a single Base (Coinbase L2) transaction by hash, especially when ERC-20 token transfer data is needed alongside native transaction metadata. Prefer this over a general Ethereum explorer API when the transaction is specifically on the Base network and you want a structured, machine-readable JSON response with all relevant fields in one call.

## Known failure modes

- Invalid hash format (not 0x + 64 hex chars) returns a validation error
- Transaction hash not found on Base returns a not-found error
- Transaction still pending may return incomplete block/time fields
- Network connectivity issues to Base RPC may cause timeouts
- Rate limiting or payment failure returns a 402 or 429 error

## How this service works

A Base transaction by hash: status, block, time, from, to, gas, value and its ERC-20 transfers.

## Output

Returns a structured object containing the transaction status (success/failure/pending), block number, block timestamp, sender address (from), recipient address (to), gas limit and gas used, ETH value transferred, and a list of ERC-20 token transfer events within the transaction including token addresses, sender, recipient, and amounts.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "hash": {
   "type": "string",
   "pattern": "^0x[0-9a-fA-F]{64}$",
   "description": "The transaction hash (0x and 64 hex digits)."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/base-transaction-lookup-by-hash-8225db1d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from centralcity.ai](https://www.zero.xyz/host/centralcity.ai/llms.txt)
