Price it per endpoint
Every endpoint costs a different number of credits, and the same endpoint costs a different amount on each chain. Build the basket you actually call and see the monthly figure.
Access to full transaction data on all transactions & addresses
Retrieve blockchain data, balances, and transactions
Detailed blockchain history and transaction data for any address.
Full smart contracts metadata, including token symbols & token names
Access to full transaction data on all transactions & addresses
Get live crypto prices, exchange rates, supply and token contracts across protocols via one REST API.
Real-time notifications for events on top blockchains. Response under 100ms.
AML address screening across 20+ blockchains
Sync and manage HD wallets, keys and addresses
Local signing for EVM, UTXO, Tron, XRP, Kaspa and Solana
Precise blockchain transaction fee estimates based on transaction priority
Broadcast and verify transactions with real-time monitoring
Prepare EVM transactions, including token transfers
Test EVM transactions, optimize gas fees and identify security flaws
Pay for HTTP APIs, or charge for your own, in USDC stablecoin over the open x402 protocol — non-custodial, on-chain settlement.
MCP servers, CLI and skills for AI agents
Dedicated nodes infrastructure for leading blockchains using JSON-RPC
Address validation, encoding & cryptographic tasks optimizations
Shared node infrastructure for top blockchains using JSON-RPC.
Every endpoint costs a different number of credits, and the same endpoint costs a different amount on each chain. Build the basket you actually call and see the monthly figure.
Pick a chain, add the endpoints you call, and enter how many calls you make each month. Credits come from the real per-endpoint price for that chain.
| Endpoint | Credits per call | Calls per month | Credits |
|---|
No endpoints yet — add one above.
These bill whether or not you call anything, and on most accounts they are the larger half of the invoice. Monitoring is charged per address per day; syncing a transaction and delivering a callback are charged per operation.
Credit cost tracks what a request actually costs us to serve, so it varies by chain — a UTXO chain has to walk far more data to answer the same question as an account-based one. It also varies by endpoint family: reading the most recent activity is cheaper than reading full history, which has to be synced first.
A synced address bills daily monitoring for as long as it stays synced. If you only need history once — to backfill a ledger or a tax report — sync it, pull what you need, store it yourself, then stop syncing. History does not change, and there is no reason to pay to watch it.
An estimate, not a quote. Actual usage varies with retries, pagination and how much history you pull.