# Synapse API — Bob Token Transfers

> Synapse API — Bob Token Transfers 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 given wallet address (owner) across blockchain networks, with filtering by block range, contract addresses, and pagination support.

## Facts

- Endpoint: POST https://synapse-api-brown.vercel.app/api/bob/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-bob-token-transfers-1fff6736
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_pHaC0PgVxIej0UF-H6Frf

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-bob-token-transfers-1fff6736 -d '<json body>'
```

Example prompt: Show me all token transfers for wallet 0xAbc123...def in descending order, filtering to only USDC and USDT contract addresses, starting from block 18000000 up to block 19000000, and return at most 50 results.

## When to prefer this

Use this endpoint when you need to retrieve on-chain token transfer history for a specific wallet address with fine-grained control over block range, contract filtering, sort order, and pagination. Prefer it over generic blockchain explorers when you need programmatic, pay-per-call access without API key registration, or when working within an x402-compatible agent workflow that handles micropayments automatically.

## Known failure modes

- Invalid or malformed owner address returns an error
- Unknown or unsupported contract addresses may return empty results
- Invalid block numbers (toBlock less than fromBlock) may cause errors
- Missing required owner field results in a 400 bad request
- Payment not included or insufficient USDC causes 402 payment required
- pageKey from a different query context may cause pagination errors

## 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 for the specified owner address, including transfer details such as token contract address, sender, recipient, amount, block number, and transaction hash. A pageKey is included when more results are available for subsequent 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-bob-token-transfers-1fff6736/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)