78trust / 100

Crypto Address History

by 2s in Onchain & crypto

x402 APIPassing, checked 3 h ago

Transaction history for an Ethereum address (via Etherscan V2). Returns normal transactions newest-first: hash, block, timestamp, from/to, value (wei + ETH), gas used, gas price, decoded method id + function name, error flag, and any contract created. Paginate with page + offset; bound with startBlock/endBlock. Defaults to Ethereum mainnet; other EVM chains are reachable by chainId where upstream coverage allows. Net-new vs crypto.tx (single-hash receipt).

GET
https://2s.io/api/crypto/address-history
Price
$0.0036
per call in USDC
Uptime
100%
last 30 days
Response time
264 ms
388 ms slowest 5%
Last check
Passed
3 h ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed · Watch with other listings

How to call it

GET https://2s.io/api/crypto/address-history

Each call costs $0.0036 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://2s.io/api/crypto/address-history?address=example&chainId=1&endBlock=0&offset=1&page=1&sort=asc&startBlock=0

Parameters

ParameterTypeRequiredDescription
addressstringYes
chainIdintegerNoEVM chain id; defaults to 1 (Ethereum). Other chains (8453 Base, 137 Polygon, 42161 Arbitrum…) require upstream multichain coverage. Default: 1.
endBlockintegerNo
offsetintegerNo
pageintegerNo
sortstringNo One of: asc, desc.
startBlockintegerNo

Example response

The listing has no example response.

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.0036.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://2s.io/api/crypto/address-history?address=example&chainId=1&endBlock=0&offset=1&page=1&sort=asc&startBlock=0'

# 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://2s.io/api/crypto/address-history?address=example&chainId=1&endBlock=0&offset=1&page=1&sort=asc&startBlock=0' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: 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.0036 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.0036" });
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.0036 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2F2s.io%2Fapi%2Fcrypto%2Faddress-history
const res = await pay("https://2s.io/api/crypto/address-history?address=example&chainId=1&endBlock=0&offset=1&page=1&sort=asc&startBlock=0");
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.0036 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.0036"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.get("https://2s.io/api/crypto/address-history?address=example&chainId=1&endBlock=0&offset=1&page=1&sort=asc&startBlock=0")
    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

WhenResultHTTPTimePrice
3 h agoPassed402218 ms$0.0036
7 h agoPassed402241 ms$0.0036
12 h agoPassed402216 ms$0.0036
16 h agoPassed402304 ms$0.0036
26 h agoPassed402263 ms$0.0036
Show 10 older checks
30 h agoPassed402320 ms$0.0036
34 h agoPassed402536 ms$0.0036
39 h agoPassed402291 ms$0.0036
43 h agoPassed402190 ms$0.0036
47 h agoPassed402388 ms$0.0036
2 days agoPassed402290 ms$0.0036
2 days agoPassed402252 ms$0.0036
2 days agoPassed402328 ms$0.0036
3 days agoPassed402261 ms$0.0036
3 days agoPassed402245 ms$0.0036