# Base Transaction Verifier

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

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

## Facts

- Endpoint: GET https://pyfile-agent.taile3ff35.ts.net:10000/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-e361f199
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_V_yOna3g-FSm3_Bee6-38

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-e361f199
```

Example prompt: Can you verify the Base transaction 0x3a1b2c4d5e6f... and tell me its status, which block it landed in, who sent it, who received it, and what value was transferred?

## When to prefer this

Choose this endpoint when you need to verify or audit a specific transaction on Base L2 — especially for confirming payment receipt, debugging failures, or auditing agent-initiated on-chain actions. It is purpose-built for Base and returns a clean structured summary (status, block, from, to, value, method) without requiring direct RPC access or a full blockchain node.

## Known failure modes

- Invalid or malformed transaction hash returns an error response
- Transaction hash not yet indexed (very recent tx) may return not-found or pending
- Hash for a non-Base chain transaction will return no result
- Network or RPC node downtime may cause timeouts
- Missing ?hash= query parameter returns a 400-level error

## How this service works

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

## Output

Returns transaction status (success/failed/pending), block number, from address, to address, transferred value (in wei or ETH), and the contract method called, all keyed to the provided transaction hash on Base L2.

## 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-e361f199/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from pyfile-agent.taile3ff35.ts.net:10000](https://www.zero.xyz/host/pyfile-agent.taile3ff35.ts.net%3A10000/llms.txt)