# Base Transaction Verifier

> Base Transaction Verifier is a paid API for AI agents from pyfile-agent.taile3ff35.ts.net, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-15).

Looks up and returns status, block, from/to addresses, value, and method for a Base blockchain transaction by hash

## Facts

- Endpoint: GET https://pyfile-agent.taile3ff35.ts.net/data/tx
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/base-transaction-verifier-3b8036f0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_aZRsbTce1NYzo0CuxOCKF

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-verifier-3b8036f0
```

Example prompt: Can you verify Base transaction 0x4a3f...d9b2 and tell me its status, what block it landed in, the sender and receiver addresses, and how much value was transferred?

## When to prefer this

Use this endpoint when you need to verify or audit a specific transaction on the Base L2 blockchain by its hash. Prefer this over general block explorers when you need machine-readable structured output for agent workflows. Best for confirming payments, auditing DeFi interactions, or debugging failed transactions on Base specifically — not for Ethereum mainnet or other chains.

## Known failure modes

- Invalid or malformed tx hash returns an error or empty result
- Transaction not yet indexed returns pending/null status
- Non-Base chain tx hashes (e.g. Ethereum mainnet) may return not found
- Network timeout if Base RPC is slow
- Missing ?hash= parameter returns a bad request error

## How this service works

Verify a Base transaction: status, block, from/to, value, method. ?hash=0x...

## Output

Returns structured details about the Base chain transaction including: confirmation status (success/pending/failed), block number, sender address (from), recipient address (to), ETH/token value transferred, and the contract method called (if applicable).

## 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",
     "properties": {}
    }
   }
  },
  "output": {
   "type": "object"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/base-transaction-verifier-3b8036f0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from pyfile-agent.taile3ff35.ts.net](https://www.zero.xyz/host/pyfile-agent.taile3ff35.ts.net/llms.txt)