# Base Batch Transaction Verifier

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

Verify up to 20 Base blockchain transactions in a single API call, returning validity and details for each.

## Facts

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

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-batch-transaction-verifier-025c4a57
```

Example prompt: Can you verify all 15 of these Base transaction hashes at once and tell me which ones are valid, who sent them, and what block they landed in?

## When to prefer this

Choose this endpoint when you need to verify multiple Base transactions simultaneously (up to 20) and want to minimize API call overhead and cost compared to verifying each transaction individually. Ideal for payment processors, marketplaces, or auditors who regularly need to confirm batches of on-chain activity.

## Known failure modes

- Batch exceeds 20 transactions — request rejected
- Invalid or malformed transaction hashes — individual entries return error or null
- Transaction not yet indexed on-chain — may return not found
- Network issues with Base RPC — timeout or partial results
- Missing required input parameters — 400 error

## How this service works

Verify up to 20 Base transactions in one call

## Output

Returns a batch of verification results for up to 20 Base transactions, each including whether the transaction is valid, the sender (from) address, recipient (to) address, block number, and gas used.

## 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-batch-transaction-verifier-025c4a57/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)