# Xerxes Base Transaction Status Checker

> Xerxes Base Transaction Status Checker 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-14).

Checks whether a Base blockchain transaction has landed, returning its status (pending, confirmed, reverted, not_found, or unread) along with confirmation count, decoded USDC Transfer logs, and a proof-stamped head block reference.

## Facts

- Endpoint: GET https://ari001.tailb4ac3a.ts.net/v1/base/tx/:hash
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/xerxes-base-transaction-status-checker-1d833897
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_g6U1gJxhKF8VvFE3RTGJI

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-status-checker-1d833897
```

Example prompt: Can you check whether Base transaction 0x4a3b...f7d2 has been confirmed yet, and tell me how many confirmations it has and whether it included any USDC transfers?

## When to prefer this

Use this endpoint when you specifically need to verify the landing status of a Base (Ethereum L2) transaction by hash, especially when you also need decoded USDC Transfer event data and a cryptographic head-block proof stamp. Prefer this over generic Ethereum RPC calls when you need a single structured response covering status, confirmations, and token transfer decoding together, and when operating in an x402 payment-aware agent context on Base.

## Known failure modes

- Transaction hash not found on Base — returns not_found status
- Transaction submitted but not yet indexed — returns pending or unread
- Invalid or malformed transaction hash format — likely 4xx error
- Network or node unavailability — may return an error or timeout
- Transaction exists but has no USDC logs — logs field returns empty or null

## How this service works

Use when an agent needs to know whether a Base transaction landed. Returns pending, reverted, confirmed with confirmations, not_found, or unread. Decodes USDC Transfer logs. Proof-stamped with the head block. Missing value is null, not zero.

## Output

Returns a status field (pending, confirmed, reverted, not_found, or unread), a confirmation count when confirmed, decoded USDC Transfer log entries if present, and a proof stamp containing the current head block number. Missing numeric values are returned as null rather than zero.

## 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"
    },
    "pathParams": {
     "type": "object",
     "required": [
      "hash"
     ],
     "properties": {
      "hash": {
       "type": "string",
       "description": "32-byte 0x transaction hash on Base"
      }
     }
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/xerxes-base-transaction-status-checker-1d833897/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)