# Synapse API — Degen Token Transfers Lookup

> Synapse API — Degen Token Transfers Lookup 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 ERC-20 or native token transfer history for a given wallet address, with optional filtering by block range, contract addresses, and pagination.

## Facts

- Endpoint: POST https://synapse-api-brown.vercel.app/api/degen/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-degen-token-transfers-lookup-915b5da8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_NcFJZnM_64VjM1qBcPq-t

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-degen-token-transfers-lookup-915b5da8 -d '<json body>'
```

Example prompt: Pull the last 50 token transfers for wallet 0xABC...123, sorted newest first, and filter to only show transfers for the USDC contract at 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48.

## When to prefer this

Choose this endpoint when you need paginated, filterable token transfer history for a specific wallet address across one or more ERC-20 contracts, especially when you need block-range scoping or need to iterate through large transfer histories. Prefer this over generic blockchain explorers when you need structured JSON output suitable for downstream agent processing and are comfortable with pay-per-call pricing.

## Known failure modes

- Invalid or malformed wallet address returns an error
- Unknown or unsupported contract address silently returns empty results
- Invalid block range (fromBlock > toBlock) may return error or empty set
- Missing required 'owner' field causes request failure
- pageKey from a different query context returns unexpected results
- Rate limiting or payment failure (x402) blocks access

## 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 list of token transfer events for the specified wallet, each containing sender, receiver, token contract, amount, block number, and transaction hash. Supports cursor-based pagination via pageKey for large result sets.

## 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-degen-token-transfers-lookup-915b5da8/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)