# Base Transaction Verifier

> Base Transaction Verifier is a paid API for AI agents from risk-api-production-af85.up.railway.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-30).

Verifies a Base blockchain transaction by hash, returning validity status, sender, recipient, block number, and gas used

## Facts

- Endpoint: GET https://risk-api-production-af85.up.railway.app/tx-verify?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-30
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/base-transaction-verifier-2bd6b2aa
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_aTPk8GQlKjm4HX5HrI5fN

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-2bd6b2aa
```

Example prompt: Can you verify the Base transaction with hash 0x4f3b2a... and tell me if it's valid, who sent it, who received it, which block it landed in, and how much gas was used?

## When to prefer this

Use this endpoint when you need to confirm the on-chain status and details of a specific Base transaction by hash — ideal for verifying payments, auditing DeFi interactions, or resolving disputes about whether a transaction occurred. Prefer this over the batch endpoint when checking a single transaction. For risk scoring of a transaction before sending, use the sibling pre-send risk scoring endpoint instead.

## Known failure modes

- Invalid or malformed transaction hash returns an error or invalid result
- Transaction hash not found on Base network (may not exist or be from another chain)
- Network latency or RPC downtime causing lookup failure
- Rate limiting or payment failure for the $0.01 USDC per call fee
- Transaction hash from a non-Base chain (e.g. Ethereum mainnet) may return not found

## How this service works

Verify any Base transaction by hash. Returns validity, from, to, block, gas used.

## Output

Returns a structured response containing: whether the transaction is valid (boolean), the from address (sender), the to address (recipient), the block number it was included in, and the gas used for execution

## 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": {}
    }
   },
   "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/base-transaction-verifier-2bd6b2aa/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from risk-api-production-af85.up.railway.app](https://www.zero.xyz/host/risk-api-production-af85.up.railway.app/llms.txt)