ExchangeRebel EVM Reads API
The EVM Reads API from ExchangeRebel — 6 operation(s) for evm reads.
The EVM Reads API from ExchangeRebel — 6 operation(s) for evm reads.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.curl "https://apis.io/api/v1/apis/exchangerebel-com:exchangerebel-com-evm-reads-api"
curl "https://apis.io/api/v1/apis?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: ExchangeRebel — pay-per-call APIs for AI agents (x402 on…
version: 1.0.0
contact:
name: 'ExchangeRebel (operator: Rebel Data)'
url: https://exchangerebel.com
email: sound.money.investing@gmail.com
x-guidance: 'All paid operations use x402 on Solana: call without payment to get a 402 challenge (SOL recipient + USDC token account + fresh memo), pay with the memo attached via the Solana Memo program, then retry with header X-Payment-Tx: <signature> and ?toll_memo=<memo>. Challenges are dual-version: the PAYMENT-REQUIRED header carries the x402 v2 PaymentRequired object and the response body carries the same challenge in x402 v1 form for compatibility. Free operations (security: []) include each service''s /health catalog with full response shapes. Prices in x-payment-info are USD per call unless the summary says otherwise (RPC is per 1,000-request block; Telegram provisioning is per bot-month; transcription is per minute of audio).'
description: '67 data and utility APIs behind x402 tolls, settled in SOL or USDC on Solana. Call a paid endpoint without payment to receive a 402 x402 challenge (recipient + fresh memo), pay with the memo attached via the Solana Memo program, then retry with the X-Payment-Tx header and toll_memo query parameter. Free catalog/health endpoints are marked without x-payment-info. Full catalogs: GET /toll/discovery and each service''s /health.'
servers:
- url: https://exchangerebel.com
tags:
- name: EVM Reads
paths:
/toll/evm/tx-decode:
post:
tags:
- EVM Reads
summary: 'Decode an Ethereum transaction: function, args, amounts, ENS'
responses:
'200':
description: Success. Response shape is documented in the service catalog (GET /health on the service).
content:
application/json:
example:
summary: ERC-20 transfer of 1.5 DAI from alice.eth (0x1111…1111) to 0x2222…2222 via the DAI contract.
status: success
revert_reason: null
tx_hash: '0xabababababababababababababababababababababababababababababababab'
chain: ethereum-mainnet
chain_id: 1
function_name: transfer
function_signature: transfer(address,uint256)
selector: '0xa9059cbb'
decoded_args:
- name: to
type: address
value: '0x2222222222222222222222222222222222222222'
- name: amount
type: uint256
value: '1500000000000000000'
token:
address: '0xaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa'
symbol: DAI
decimals: 18
name: Dai Stablecoin
amount_formatted: '1.5'
value_eth: '0'
value_wei: '0'
from:
address: '0x1111111111111111111111111111111111111111'
ens: alice.eth
to:
address: '0xaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa'
ens: null
block_number: 4080
gas_used: '21000'
attestation:
as_of_block: 4096
as_of_block_timestamp: '2024-10-04T14:47:28.000Z'
source: Ethereum mainnet chain data read via the service's configured JSON-RPC input (own-node design; provider inputs decoded by this service — no raw RPC passthrough)
signature_source: Sourcify open-data signature set (MIT), vendored subset — see /schema for coverage
inputs_summary:
rpc_calls: eth_getTransactionByHash + eth_getTransactionReceipt + eth_blockNumber/eth_getBlockByNumber + token metadata eth_calls + ENS reverse lookups (best-effort)
selector_matched: true
envelope:
v: 1
service: evm-reads
source: Ethereum mainnet chain data via configured JSON-RPC input, decoded by this service
grade: derived
max_age_seconds: 30
changes:
supported: false
'402':
description: 'Payment Required (x402). The PAYMENT-REQUIRED response header carries the x402 v2 PaymentRequired object (base64 JSON: scheme, CAIP-2 network, amount, asset, payTo, plus the bazaar discovery extension); the response body carries the same challenge in x402 v1 form for compatibility, naming the SOL recipient and USDC token account on Solana plus a fresh memo. To pay on this service''s rail: pay with the memo attached (Solana Memo program), then retry with header ''X-Payment-Tx: <transaction signature>'' and query parameter ''toll_memo=<memo>''.'
requestBody:
content:
application/json:
schema:
type: object
properties:
tx_hash:
type: string
description: string (required) - 0x-prefixed 32-byte transaction hash
required:
- tx_hash
x-payment-info:
protocols:
- x402
price:
mode: fixed
currency: USD
amount: '0.01'
security:
- x402Payment: []
operationId: postTollEvmTxDecode
x-operation-id-source: derived
/toll/evm/address-verdict:
post:
tags:
- EVM Reads
summary: 'Classify an Ethereum address: EOA vs contract, proxy, token'
responses:
'200':
description: Success. Response shape is documented in the service catalog (GET /health on the service).
content:
application/json:
example:
verdict: externally-owned-account
summary: 0x1111…1111 is an externally owned account (EOA) — no contract code, ENS reverse name alice.eth, balance 1 ETH, nonce 5.
address: '0x1111111111111111111111111111111111111111'
chain: ethereum-mainnet
chain_id: 1
kind: eoa
code_size_bytes: 0
balance_eth: '1'
balance_wei: '1000000000000000000'
nonce: 5
ens: alice.eth
proxy:
is_proxy: false
type: null
implementation: null
interfaces:
erc165: false
erc721: false
erc1155: false
erc20_like: false
token: null
flags:
- eoa
boundary: Runtime introspection/classification from live chain state only — NOT a security audit, NOT a fund-safety verdict. Proxy/interface detection is behavioral; absence of a flag is not proof of safety.
attestation:
as_of_block: 4096
as_of_block_timestamp: '2024-10-04T14:47:28.000Z'
source: Ethereum mainnet chain data read via the service's configured JSON-RPC input (own-node design; provider inputs decoded by this service — no raw RPC passthrough)
inputs_summary:
rpc_calls: eth_getCode + eth_getBalance + eth_getTransactionCount + eth_getStorageAt (EIP-1967) + ERC-165 eth_calls + ERC-20 metadata eth_calls + ENS reverse lookup (best-effort)
envelope:
v: 1
service: evm-reads
source: Ethereum mainnet chain data via configured JSON-RPC input, decoded by this service
grade: derived
max_age_seconds: 30
changes:
supported: false
'402':
description: 'Payment Required (x402). The PAYMENT-REQUIRED response header carries the x402 v2 PaymentRequired object (base64 JSON: scheme, CAIP-2 network, amount, asset, payTo, plus the bazaar discovery extension); the response body carries the same challenge in x402 v1 form for compatibility, naming the SOL recipient and USDC token account on Solana plus a fresh memo. To pay on this service''s rail: pay with the memo attached (Solana Memo program), then retry with header ''X-Payment-Tx: <transaction signature>'' and query parameter ''toll_memo=<memo>''.'
requestBody:
content:
application/json:
schema:
type: object
properties:
address:
type: string
description: string (required) - 0x-prefixed 20-byte Ethereum address
required:
- address
x-payment-info:
protocols:
- x402
price:
mode: fixed
currency: USD
amount: '0.01'
security:
- x402Payment: []
operationId: postTollEvmAddressVerdict
x-operation-id-source: derived
/toll/evm/transfers:
post:
tags:
- EVM Reads
summary: Decoded ERC-20 transfer history for an Ethereum address
responses:
'200':
description: Success. Response shape is documented in the service catalog (GET /health on the service).
content:
application/json:
example:
summary: Found 3 ERC-20 transfer(s) for 0x1111…1111 in the disclosed lookback window (blocks 0–4096); returning 2 newest-first — more remain, use next_cursor.
address: '0x1111111111111111111111111111111111111111'
chain: ethereum-mainnet
chain_id: 1
window:
lookback_blocks: 10000
from_block: 0
to_block: 4096
note: Transfers are read from eth_getLogs over this bounded window only; older history is not claimed. The window and any truncation are disclosed here in every response.
total_in_window: 3
returned: 2
truncated: true
next_cursor: eyJ2IjoxLCJvZmYiOjJ9
transfers:
- direction: in
token:
address: '0xaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa'
symbol: DAI
decimals: 18
name: Dai Stablecoin
amount: '1'
amount_raw: '1000000000000000000'
from: '0x2222222222222222222222222222222222222222'
to: '0x1111111111111111111111111111111111111111'
counterparty: '0x2222222222222222222222222222222222222222'
tx_hash: '0x2222222222222222222222222222222222222222222222222222222222222222'
block_number: 4090
log_index: 1
- direction: out
token:
address: '0xaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa'
symbol: DAI
decimals: 18
name: Dai Stablecoin
amount: '2.5'
amount_raw: '2500000000000000000'
from: '0x1111111111111111111111111111111111111111'
to: '0x2222222222222222222222222222222222222222'
counterparty: '0x2222222222222222222222222222222222222222'
tx_hash: '0x1111111111111111111111111111111111111111111111111111111111111111'
block_number: 4085
log_index: 0
attestation:
as_of_block: 4096
as_of_block_timestamp: '2024-10-04T14:47:28.000Z'
source: Ethereum mainnet chain data read via the service's configured JSON-RPC input (own-node design; provider inputs decoded by this service — no raw RPC passthrough)
inputs_summary:
rpc_calls: eth_blockNumber/eth_getBlockByNumber + eth_getLogs (out + in) + per-token metadata eth_calls
tokens_seen: 1
envelope:
v: 1
service: evm-reads
source: Ethereum mainnet chain data via configured JSON-RPC input, decoded by this service
grade: derived
max_age_seconds: 30
changes:
supported: false
'402':
description: 'Payment Required (x402). The PAYMENT-REQUIRED response header carries the x402 v2 PaymentRequired object (base64 JSON: scheme, CAIP-2 network, amount, asset, payTo, plus the bazaar discovery extension); the response body carries the same challenge in x402 v1 form for compatibility, naming the SOL recipient and USDC token account on Solana plus a fresh memo. To pay on this service''s rail: pay with the memo attached (Solana Memo program), then retry with header ''X-Payment-Tx: <transaction signature>'' and query parameter ''toll_memo=<memo>''.'
requestBody:
content:
application/json:
schema:
type: object
properties:
address:
type: string
description: string (required) - 0x-prefixed 20-byte Ethereum address
limit:
type: integer
description: integer 1-100, default 25
cursor:
type: string
description: string - opaque cursor from a prior response's next_cursor
required:
- address
x-payment-info:
protocols:
- x402
price:
mode: fixed
currency: USD
amount: '0.01'
security:
- x402Payment: []
operationId: postTollEvmTransfers
x-operation-id-source: derived
/toll/evm/catalog:
get:
tags:
- EVM Reads
summary: 'Service catalog: endpoints, prices, semantics'
responses:
'200':
description: Success. Response shape is documented in the service catalog (GET /health on the service).
security: []
operationId: getTollEvmCatalog
x-operation-id-source: derived
/toll/evm/schema:
get:
tags:
- EVM Reads
summary: Request/response schema + validation rules
responses:
'200':
description: Success. Response shape is documented in the service catalog (GET /health on the service).
security: []
operationId: getTollEvmSchema
x-operation-id-source: derived
/toll/evm/health:
get:
tags:
- EVM Reads
summary: Check the EVM reads service status
responses:
'200':
description: Success. Response shape is documented in the service catalog (GET /health on the service).
security: []
operationId: getTollEvmHealth
x-operation-id-source: derived
components:
securitySchemes:
x402Payment:
type: apiKey
in: header
name: X-Payment-Tx
description: 'x402 toll payment proof: the Solana transaction signature of a payment carrying the memo from the 402 challenge; send together with ?toll_memo=<memo>. Payment itself is made on-chain in SOL or USDC to the recipient named in the challenge.'