# Xerxes Base Transaction Proof Lookup

> Xerxes Base Transaction Proof Lookup is a paid API for AI agents from ari001.tailb4ac3a.ts.net, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-15).

Fetches typed transaction proof for a Base chain transaction by hash, returning confirmation status, block details, and USDC transfer events.

## Facts

- Endpoint: GET https://ari001.tailb4ac3a.ts.net/v1/base/tx/%7Bhash%7D
- 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/xerxes-base-transaction-proof-lookup-a3f94ce7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_GDIl9wwJop7ghRNjA3gKI

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 xerxes-base-transaction-proof-lookup-a3f94ce7
```

Example prompt: Can you check whether Base transaction 0xcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcd has been confirmed and show me the USDC transfers inside it?

## When to prefer this

Use this endpoint when you specifically need typed proof of a Base chain transaction — confirmation status, block anchoring, and decoded USDC transfer events in a single call. Prefer it over raw RPC when you need structured, agent-readable output without parsing raw EVM logs. Best suited for x402 payment verification workflows where you need to confirm a USDC payment settled on Base before taking a downstream action.

## Known failure modes

- Transaction hash not found — returns error or ok:false
- Transaction is still pending — kind field will reflect pending state rather than confirmed
- Malformed or invalid hash format — likely 4xx error
- RPC backend unreachable — service-level error
- Hash belongs to a chain other than Base — incorrect or empty result

## How this service works

ARYSPHERE Base typed objects and transaction proofs behind x402. Dead RPC is unreadability, not zeros.

## Output

A JSON object with ok status, sender and recipient addresses, transaction kind (confirmed/pending/reverted), a proof object containing block hash and block number, transaction hash, log count, value in wei, total confirmations, and an array of USDC transfer events each with to/from addresses and atomic amount.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "to": "0x833589fcd6edb6e08f4c7c32d4f71b54bda02913",
  "from": "0x1111111111111111111111111111111111111111",
  "kind": "confirmed",
  "proof": {
   "block_hash": "0xabababababababababababababababababababababababababababababababab",
   "block_number": 12345678
  },
  "service": "base_tx",
  "tx_hash": "0xcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcd",
  "log_count": 1,
  "value_wei": null,
  "block_number": 12345670,
  "confirmations": 8,
  "usdc_transfers": [
   {
    "to": "0x2222222222222222222222222222222222222222",
    "from": "0x1111111111111111111111111111111111111111",
    "amount_atomic": "10000"
   }
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/xerxes-base-transaction-proof-lookup-a3f94ce7/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from ari001.tailb4ac3a.ts.net](https://www.zero.xyz/host/ari001.tailb4ac3a.ts.net/llms.txt)