# Synapse API — Ink Network Token Transfers

> Synapse API — Ink Network 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-15).

Retrieves token transfer history for a given owner address on the Ink blockchain network, with filtering by block range, contract addresses, and pagination support.

## Facts

- Endpoint: POST https://synapse-api-brown.vercel.app/api/ink/token/transfers
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/synapse-api-ink-network-token-transfers-319376f0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_jKmRM6TObSoWRqpRsXZnp

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-ink-network-token-transfers-319376f0 -d '<json body>'
```

Example prompt: Pull all token transfers for wallet 0xAbC...123 on the Ink network, sorted in descending order, limited to the last 100 transfers, and only from contract 0xDef...456.

## When to prefer this

Use this endpoint when you need token transfer history specifically on the Ink blockchain network. Prefer this over generic blockchain explorers when you need programmatic, paginated, filterable access to transfer data for a specific wallet or set of token contracts on Ink, particularly for automated portfolio tracking, audit trails, or DeFi analytics.

## Known failure modes

- Invalid owner address format returns an error
- Unknown or malformed contract address in contractAddresses array
- Invalid block range (fromBlock greater than toBlock) causes empty or error response
- Invalid pageKey causes pagination failure
- Network unavailability or RPC node issues result in timeout
- Missing required owner field returns validation error

## 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 owner on the Ink blockchain, each containing sender, receiver, token contract address, amount, block number, and transaction hash, along with a page key for pagination if more results exist.

## 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-ink-network-token-transfers-319376f0/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)