Wallet Transfers
by TickersFeed in Onchain & crypto
Token transfer history for any wallet address on Base or Ethereum — inbound/outbound transfers with token, amount, direction, and timestamp as JSON. Powered by Dune Analytics. Use for: wallet activity tracking, onchain transaction history, USDC transfer audit, address monitoring. $0.003 USDC per call.
https://api.tickersfeed.net/wallet/:address/transfers- Price
- $0.003
- per call in USDC
- Uptime
- 0.0%
- last 30 days
- Response time
- -
- no timed checks yet
- Last check
- Failed
- 27 min ago, next in 31 min
Reliability
Latest check failed 27 min ago: Expected HTTP 402, got 404
How to call it
GET https://api.tickersfeed.net/wallet/:address/transfers
Each call costs $0.003 in USDC on Base, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
GET https://api.tickersfeed.net/wallet/:address/transfers?address=0x0567abB38E84FF9676A5B9B469b0255CdabE13f4&chain=base&days=30&limit=10Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
address | string | No | Wallet address (0x...) |
chain | string | No | Blockchain: base (default) or ethereum |
days | number | No | Lookback days, max 90 (default 30) |
limit | number | No | Max results, up to 100 (default 25) |
Example response
The provider's example. We can't check it without paying.
{
"address": "0xE82E...",
"chain": "base",
"transfers": [
{
"amount_usdc": 0.003,
"block_time": "2026-06-11",
"direction": "IN"
}
]
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.003.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://api.tickersfeed.net/wallet/:address/transfers?address=0x0567abB38E84FF9676A5B9B469b0255CdabE13f4&chain=base&days=30&limit=10'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://api.tickersfeed.net/wallet/:address/transfers?address=0x0567abB38E84FF9676A5B9B469b0255CdabE13f4&chain=base&days=30&limit=10' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.003 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.003" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.003 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fapi.tickersfeed.net%2Fwallet%2F%3Aaddress%2Ftransfers
const res = await pay("https://api.tickersfeed.net/wallet/:address/transfers?address=0x0567abB38E84FF9676A5B9B469b0255CdabE13f4&chain=base&days=30&limit=10");
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.003 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.003"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.get("https://api.tickersfeed.net/wallet/:address/transfers?address=0x0567abB38E84FF9676A5B9B469b0255CdabE13f4&chain=base&days=30&limit=10")
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 27 min ago | Expected HTTP 402, got 404 | 404 | 431 ms | - |
| 5 h ago | Expected HTTP 402, got 404 | 404 | 413 ms | - |
| 10 h ago | Expected HTTP 402, got 404 | 404 | 577 ms | - |
| 14 h ago | Expected HTTP 402, got 404 | 404 | 489 ms | - |
| 19 h ago | Expected HTTP 402, got 404 | 404 | 483 ms | - |
Show 10 older checks
| 23 h ago | Expected HTTP 402, got 404 | 404 | 432 ms | - |
| 28 h ago | Expected HTTP 402, got 404 | 404 | 405 ms | - |
| 32 h ago | Expected HTTP 402, got 404 | 404 | 358 ms | - |
| 36 h ago | Expected HTTP 402, got 404 | 404 | 350 ms | - |
| 40 h ago | Expected HTTP 402, got 404 | 404 | 472 ms | - |
| 44 h ago | Expected HTTP 402, got 404 | 404 | 464 ms | - |
| 2 days ago | Expected HTTP 402, got 404 | 404 | 410 ms | - |
| 2 days ago | Expected HTTP 402, got 404 | 404 | 351 ms | - |
| 2 days ago | Expected HTTP 402, got 404 | 404 | 323 ms | - |
| 3 days ago | Expected HTTP 402, got 404 | 404 | 423 ms | - |