# Aether Base Token Transfer History

> Aether Base Token Transfer History is a paid API for AI agents from aether-x402.vercel.app, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-12).

Fetches on-chain ERC-20 or native token transfer history for a given address or token contract on the Base network over a specified block range.

## Facts

- Endpoint: POST https://aether-x402.vercel.app/v1/base/transfers?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/aether-base-token-transfer-history-467cf5ad
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__gdqlD0VOPkJsF2Dd_WyB

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 aether-base-token-transfer-history-467cf5ad -d '<json body>'
```

Example prompt: Pull all token transfers for wallet 0xAbC...123 on Base over the last 500 blocks and show me who sent and received funds and in what amounts.

## When to prefer this

Choose this endpoint when you need raw, granular transfer-level data for a specific wallet or token on the Base L2 network, paid per-call via USDC over x402. Prefer it over general blockchain explorers when you need programmatic, machine-readable transfer lists in a defined block range for agent workflows, token risk audits, or wallet activity monitoring on Base specifically.

## Known failure modes

- Invalid Ethereum address format returns a 400 error
- blocks value exceeding 2000 returns a validation error
- No transfers found in the block range returns an empty transfers array
- Payment failure via x402/USDC causes a 402 Payment Required response
- Token contract address does not exist on Base returns empty or error
- Base RPC node unavailability causes a 503 or timeout

## How this service works

Pay-per-call Base onchain data, token risk verdicts and x402 payability audits over x402 (USDC on Base).

## Output

Returns a JSON object with fromBlock and toBlock (the queried range) and a transfers array, each entry containing the sender address (from), recipient address (to), transaction hash (tx), and raw token value transferred.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "token": {
   "type": "string",
   "pattern": "^0x[0-9a-fA-F]{40}$"
  },
  "blocks": {
   "type": "integer",
   "maximum": 2000,
   "minimum": 1
  },
  "address": {
   "type": "string",
   "pattern": "^0x[0-9a-fA-F]{40}$"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "toBlock": "...",
  "fromBlock": "...",
  "transfers": [
   {
    "to": "0x...",
    "tx": "0x...",
    "from": "0x...",
    "value": "1000000"
   }
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/aether-base-token-transfer-history-467cf5ad/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from aether-x402.vercel.app](https://www.zero.xyz/host/aether-x402.vercel.app/llms.txt)