# Synapse API — opBNB Token Transfer History

> Synapse API — opBNB Token Transfer History is a paid API for AI agents from synapse-api-brown.vercel.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-13).

Retrieves token transfer history for a wallet address on the opBNB blockchain network, with filtering by block range, contract addresses, and pagination.

## Facts

- Endpoint: POST https://synapse-api-brown.vercel.app/api/opbnb/token/transfers
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/synapse-api-opbnb-token-transfer-history-c1b62402
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_3kI23TbNAbpQhSHfm-GOR

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 synapse-api-opbnb-token-transfer-history-c1b62402 -d '<json body>'
```

Example prompt: Pull all token transfers for wallet 0xABC123... on opBNB from block 1000000 to 2000000, sorted ascending, and show me up to 100 results — filter only for the USDT contract at 0xDEF456...

## When to prefer this

Use this endpoint when you specifically need token transfer history on the opBNB (BNB Chain Layer 2) network. It is the right choice when you need block-range filtering, multi-contract filtering, and paginated access to transfer history. Prefer this over generic blockchain explorers when you need programmatic, pay-per-call access without API key management, and when opBNB is the target chain.

## Known failure modes

- Invalid wallet address format returns an error
- Invalid contract address in contractAddresses array causes rejection
- fromBlock greater than toBlock returns an empty result or error
- Invalid pageKey causes pagination to fail or restart
- maxCount exceeding API limits may return a capped result set
- Network or RPC errors for opBNB may cause transient failures

## How this service works

High-speed API suite for AI processing, web scraping, and smart data utilities across 57+ blockchain networks. Pay-per-call via x402.

## Output

Returns a paginated list of token transfer events on opBNB for the queried wallet/contract criteria, including transaction hashes, sender/receiver addresses, token contract details, amounts, and block numbers. A pageKey is returned when more results are available for subsequent pagination calls.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "order": {
   "enum": [
    "asc",
    "desc"
   ],
   "type": "string"
  },
  "owner": {
   "type": "string"
  },
  "pageKey": {
   "type": "string"
  },
  "toBlock": {
   "type": "string"
  },
  "maxCount": {
   "type": "number"
  },
  "fromBlock": {
   "type": "string"
  },
  "contractAddresses": {
   "type": "array",
   "items": {
    "type": "string"
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/synapse-api-opbnb-token-transfer-history-c1b62402/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from synapse-api-brown.vercel.app](https://www.zero.xyz/host/synapse-api-brown.vercel.app/llms.txt)