Token transfers, zkSync Era
List a wallet's recent transfers of one ERC-20 token (default USDC) on zkSync Era, in and out, over the last N blocks (1-2,000, default 1,000): direction, counterparty, amount and transaction, newest first, up to 50. Use to confirm a payment arrived or see what was sent; for the current balance use zksync_token_balance. Malformed addresses are rejected with 400, uncharged.
Inputs
| Name | Type | Description |
|---|---|---|
address (required) | string | 0x wallet address |
token | string | Token: a ticker such as USDT or WETH, or the 0x ERC-20 contract (default: USDC on this network) |
blocks | integer | How many recent blocks to scan (1-2000, default 1000; 2,000 blocks is about 33 minutes on zkSync Era) |
Request
Over HTTP, with a card key from /credits:
curl -H "Authorization: Bearer adt_…" "https://agent-data-tools.revmesh2074.workers.dev/zksync/token-transfers?address=0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"
Or one of your 25 free calls, no key:
curl "https://agent-data-tools.revmesh2074.workers.dev/zksync/token-transfers?address=0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045&trial=1"
Without a key, the same URL answers 402 Payment Required with x402 and MPP terms, so an agent with a wallet pays per call in USDC (Base, Polygon, Arbitrum or Solana over x402; Base or Tempo over MPP) and retries.
Example result
{
"chain": "zkSync Era",
"chainId": 324,
"address": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
"fromBlock": 123456290,
"toBlock": 123456789,
"count": 1,
"truncated": false,
"transfers": [
{
"block": 123456780,
"tx": "0x…",
"token": "0x1d17CBcF0D6D143135aE902365D2E5e2A16538D4",
"symbol": "USDC",
"direction": "in",
"counterparty": "0x…",
"amount": "2.5",
"raw": "2500000"
}
]
}
From an AI agent (MCP)
Add the MCP server to Claude, Cursor or any MCP client. This tool is zksync_token_transfers, and the first 25 successful calls are free:
https://agent-data-tools.revmesh2074.workers.dev/mcp