The blockchain infrastructure suite for Web 3

Which blockchains networks are supported?

We currently support over 50 blockchains, including their testnets and mainnets. Detailed information about the supported networks is available on each dedicated service webpage. For some products, such as "Dedicated node as a service", we offer extended support beyond the listed blockchains.

Do you support testnet networks?

Yes, we support testnet networks for mutiple blockchains. We also offer a free subscription plan to be used over testnet networks.

Do you use one node per network?

We have a pool of nodes that we use, all hosted with us. If it happens one to go offline, there is always another one that will continue processing.

Do you use your own nodes or shared ones?

We don’t use shared nodes. The pool of nodes we use is owned by Crypto APIs.

How can I contact support?

You can contact our support team via Live Chat or Support Email. When you contact us, please use the email address associated with your Crypto APIs account, or the email added as a Team member in another Crypto APIs account.

Do you offer a free plan/trial/demo for Crypto APIs?

We do not offer trial or demo for Crypto APIs products. We do however offer a free subscription instead, which can be used over testing networks.

Can I use more than one Crypto APIs product at once?

Yes, you can use as many of our services as you wish. Our blockchain infrastructure is providing flexibility and is allowing you to continue using us even after you reach your subscription plan limits.

I need more custom settings for my subscription, is it possible?

Yes. We have a Custom option for subscription. To set it up you can directly discuss it with one of our representatives by contacting our team.

What is Pay As You Go?

Pay As You Go is our pricing model designed to eliminate any restrictions that could be limiting our clients from achieving their goals exactly when they need to. It enables customers on any of our paid plans to continue using our services beyond their plan's credit limit. Once you reach your credit limit, you will be notified by mail, and our Pay As You Go will automatically let you continue using our services without interruption at a slightly higher cost.

How can I pay for the service?

We accept payment methods such as debit and credit cards (Visa, MasterCard) by using our payment provider Stripe. We can also offer you an alternative way to pay for your subscription plan, such as wire transfers, pay with cryptocurrency or PayPal. For more information, contact our business development team at [email protected]

Are payments for Crypto APIs services recurring?

Yes, our service plans are subscription-based, with payments recurring automatically until customers cancel their subscriptions. Please note that upon cancellation, clients are responsible for covering the costs of the current payment term. The subscription will be cancelled at the start of the next payment cycle.

Can I prepay for my subscription for a longer period?

Yes, you can. Please contact our team at [email protected] to discuss the duration, payment methods, and terms.

Do you offer discounts?

We may offer discounts based on your subscription. Discounts are available for larger packages and longer-term subscriptions (yearly). If you believe your subscription qualifies for a discount, please contact our team right away!

What happens when I cancel my plan subscription?

If you decide to cancel your subscription, you will continue to have access to our services until the end of your current payment cycle. After that, your paid services will be discontinued. For example, if you are on a monthly subscription and cancel halfway through the month, you will still have access to paid services for the remaining two weeks. Please note that 30 days after your subscription is canceled, all data associated with your account, including your fund balance in Wallet as a Service and Blockchain Automations Service, will be permanently deleted.

What is "Throughput"?

Throughput is the metric we use to measure the number of credits that can be spent per second. Each subscription plan includes both soft and hard throughput limits. Soft throughput represents the number of requests per second included in clients chosen subscription plan. Clients can exceed the soft limit if necessary, with slightly higher credit consumption than specified in their chosen subscription plan. However, once the hard throughput limit is reached, clients will have reached the absolute maximum allowed. To increase your hard throughput limit, please upgrade your subscription plan or contact us to create a custom plan that meets your specific needs.

How many credits does an endpoint cost?

You can see the credits cost for each endpoint in our official Documentation. Simply select the endpoint you want information for and the credits cost is displayed at the end of the page.

Does Crypto APIs work with Claude, Cursor, and n8n?

Yes. Crypto APIs ships production-ready Model Context Protocol (MCP) servers that connect to Claude, Cursor, Continue, Cline, and any host that speaks MCP, with a drop-in install and no glue code. It also provides an n8n MCP Client node so you can add blockchain data access as a step in visual n8n workflows alongside HTTP, database, queue, and email nodes.

Which blockchains does the AI Compatibility / MCP integration support?

The MCP servers cover the chains Crypto APIs supports: EVM networks (Ethereum, BNB Smart Chain, Ethereum Classic, Polygon, Avalanche C-Chain, Tron, Arbitrum, Base, Optimism), UTXO chains (Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash, Kaspa), plus the account-based chains XRP and Solana. Most chains offer both mainnet and testnet (for example Ethereum Sepolia, Solana devnet), while a few such as Kaspa are mainnet-only. Coverage varies by capability — for example latest-address data spans the EVM and UTXO chains plus XRP, Solana, and Kaspa.

What can the MCP servers actually do — is it read-only?

No, it goes beyond reads. The servers expose address data and history, transaction and block data, smart-contract data, blockchain fees, and HD wallet data, and they can also prepare transactions, simulate EVM transactions, broadcast signed transactions, and create and manage blockchain event subscriptions. The live page groups these as addresses, transactions, blocks, market data, smart contracts, fees, and wallets.

Does the MCP market data include price charts or order books?

The market data tools provide asset lists, exchange rates, and asset metadata. They do not provide OHLCV candlesticks or order-book depth. Use the exchange-rate and asset tools for pricing reference data within your AI agent.

How do I get started building an AI blockchain agent with Crypto APIs?

Get a Crypto APIs API key, then install and configure one of the MCP servers with that key. Point your MCP host (Claude, Cursor, Continue, or n8n's MCP Client node) at the server and start querying on-chain data through natural language. The live page markets a drop-in install with no glue code so you can ship your first agent quickly.

What does the Verify Address / AML API do?

It provides two AML screening capabilities. Transaction screening (KYT) checks crypto transactions in real time so exchanges, PSPs, wallets and custodians can monitor activity as it happens, and address screening checks any wallet address against sanctions and fraud signals. Both return categorized compliance flags you can act on within your own workflows.

Does the AML API screen against OFAC, EU and UN sanctions lists?

Yes. Address screening checks crypto addresses against OFAC SDN, EU and UN consolidated sanctions lists. It also flags exposure to fraud-related categories such as phishing, ransomware, darknet markets and mixers.

Which blockchains does the address screening support?

The product advertises coverage across 20+ blockchains through a single REST endpoint, including Bitcoin, Ethereum, Polygon, BNB Smart Chain, Tron, Solana, Arbitrum, Optimism and Avalanche. One integration is meant to handle addresses across the supported chains.

Can I monitor transactions for compliance (KYT), not just addresses?

Yes. The Screen Transaction endpoint provides Know Your Transaction (KYT) checks for real-time monitoring, aimed at exchanges and custodians. This complements address screening so you can evaluate both counterparties and the transactions themselves.

Are screening calls logged for audit and compliance?

Yes. The product states that every screening call is logged and retrievable, which supports audit trails for regulatory reporting.

What data does the Crypto APIs Market Data API return for a cryptocurrency?

It returns current asset details including live price, circulating and max supply, market capitalization, 24-hour trading volume, and token contract addresses across protocols. You can look up an asset by its symbol (e.g. BTC) or by its unique asset ID. Data is sourced from CoinMarketCap.

Does the Market Data API provide OHLCV candlesticks or order-book data?

No. The Market Data API provides current price and current asset-to-asset exchange rates only. It does not include OHLCV/candlestick history or per-exchange order-book data.

How do I get the exchange rate between two assets, like BTC to USD?

Use the exchange-rate endpoints, which return the current rate between any two assets. You can request the rate either by asset symbols (for example BTC to USD) or by the two assets' unique asset IDs.

How many assets does the Crypto APIs Market Data API cover?

The API covers approximately 14,600 crypto and fiat assets, sourced from CoinMarketCap. You can enumerate the full supported list via the list-supported-assets endpoint, which supports pagination and a filter for crypto or fiat asset types.

Can I look up assets by symbol or do I need an asset ID?

Both are supported. Asset details and exchange rates can be requested either by human-readable symbol (such as BTC or ETH) or by the asset's unique asset ID. Symbol-based lookups are convenient, while asset IDs disambiguate tokens that share a ticker.

What is Node as a Service and how do I connect to a blockchain node?

Node as a Service gives you managed RPC endpoints so you can interact with blockchain nodes without running your own infrastructure. You connect over the node's JSON-RPC interface and can call all supported JSON-RPC methods for the chain. Both shared node subscriptions and private dedicated nodes are available.

Which blockchains does the Node as a Service RPC API support?

The service provides RPC node access across a broad set of chains, including Bitcoin, Ethereum, XRP Ledger, Ethereum Classic, Bitcoin Cash, Dash, Litecoin, Dogecoin, Zcash, BNB Smart Chain, Polygon, TRON, Solana, NEAR, Arbitrum One, Optimism, Fantom, Filecoin, and Scroll. Coverage spans major UTXO chains, EVM networks, and non-EVM chains like Solana and TRON.

Does the Node as a Service API support Solana and TRON?

Yes. Solana and TRON are both listed among the supported networks for RPC node access, alongside EVM chains and UTXO chains. You interact with each node using its supported JSON-RPC methods.

What uptime and reliability does the shared node service offer?

The service advertises 99.9% uptime with 24/7 node monitoring and connection reliability. Nodes run on multi-geo infrastructure with region selection, and a smart load balancer spreads requests across nodes for consistent performance. You can also track node usage and logs.

Is there a difference between shared nodes and dedicated nodes?

Yes. Shared nodes are offered as a subscription and are the default, cost-effective option for accessing RPC endpoints. Private dedicated nodes are available through custom plans for teams needing isolated capacity.

Which blockchains do CryptoAPIs dedicated nodes support?

CryptoAPIs dedicated nodes list Ethereum, BNB Smart Chain, Polygon, Solana, Avalanche, Arbitrum One, Optimism, Aptos, Cronos, Gnosis and Base among the supported chains. The page states 50+ blockchains are available in total, and you can request additional chains you need. Node access is provided through a JSON-RPC endpoint documented in the developer portal.

Does CryptoAPIs offer dedicated Solana RPC nodes?

Yes. Solana is explicitly listed among the blockchains available as a CryptoAPIs dedicated node. You access it via a dedicated, isolated node using the JSON-RPC endpoint referenced in the developer docs, rather than a shared endpoint.

What uptime and latency do CryptoAPIs dedicated nodes guarantee?

The page states a 99.9% uptime guarantee and response speeds starting from 25 ms. Nodes run on a hybrid-cloud infrastructure spread across 40+ global server locations. Real-time monitoring with metrics lets you track node usage, logs and performance.

Is there a free tier for CryptoAPIs dedicated nodes, and how is pricing structured?

The dedicated-nodes page does not advertise a free tier; it is a paid, dedicated-infrastructure product. Pricing is offered through custom plans you can tailor and scale to your needs. See the CryptoAPIs pricing page for plans and custom options.

What is the difference between dedicated nodes and node-as-a-service at CryptoAPIs?

Dedicated nodes give you an isolated environment with exclusive access, private networking to cut latency, and the highest level of privacy, preventing traffic spikes and noisy-neighbor bottlenecks. CryptoAPIs also offers a broader Node-as-a-Service product covering shared, dedicated and self-managed options. Choose dedicated nodes when you need isolation and predictable performance rather than a shared endpoint.

Which blockchains does the Crypto APIs HD Wallets Management (xPub sync) API support?

The HD Wallet (xPub/yPub/zPub) sync API supports the EVM chains (such as Ethereum, Ethereum Classic, BNB Smart Chain, Tron), the UTXO chains (Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash), and XRP. You import an extended public key and Crypto APIs derives and syncs its addresses and transactions for you.

Does the HD Wallets Management API support Solana?

No. HD wallet (xPub/yPub/zPub) sync is not available for Solana. HD wallet coverage is limited to the EVM chains Ethereum, Ethereum Classic, BNB Smart Chain and Tron, the six UTXO chains (Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash) and XRP. Solana is supported by other Crypto APIs products such as transactions data and blockchain events, but not by the HD wallet endpoints.

What can I do with a synced xPub through the HD Wallets API?

Once you sync an extended public key you can list all your synced HD wallets, pull the wallet's aggregated assets and balances, retrieve wallet details, and list the wallet's transactions across all derived addresses through a single integration. The sync monitors every derived address for you, so you do not have to track individual addresses manually. Syncing and deleting an xPub each carry a subscription cost, and monitored addresses incur a daily monitoring tax.

Can I derive addresses from an xPub without calling the API or exposing keys?

Yes. Crypto APIs provides address-derivation utilities in the blockchain tools family that generate child addresses from an extended public key for EVM chains, the UTXO chains and XRP. Because HD wallets use extended public keys, derivation and wallet syncing never require your private keys. This lets you generate deposit addresses and reconcile them against a synced wallet.

Is there a free tier, and how is HD wallet usage billed?

Every API request consumes credits, with the exact amount returned in the x-credits-consumed response header and the cost varying by endpoint and blockchain. HD wallet asset and transaction reads on UTXO chains are among the heavier calls (roughly 520-530 baseline credits), and a synced xPub also adds a per-subscription cost plus daily monitoring taxes per derived address. After your monthly credit allocation is exhausted, usage continues automatically under pay-as-you-go billing. The marketing page does not state a specific free-tier allowance.

What blockchains does the CryptoAPIs Wallet-as-a-Service API support?

The API covers Bitcoin, Ethereum, and 20+ chains through one unified REST integration. Live HD wallet, address, and transaction routes span EVM chains (Ethereum, BSC, ETC), UTXO chains (Bitcoin, Litecoin, Dogecoin, Dash, Bitcoin Cash, Zcash), plus XRP; transaction and address data also cover Solana and Kaspa. You use the same API shape across all of them rather than integrating each chain separately.

Can I create and manage HD wallets and derive addresses with the API?

Yes. The service lets you create and manage hierarchical-deterministic (HD) wallets and derive addresses programmatically over REST, for EVM, UTXO, and XRP chains. There are dedicated routes to manage HD wallets and to read their per-chain data, plus a utility to derive addresses.

How do I track incoming deposits and read balances or transaction history?

You track incoming deposits with real-time blockchain event webhooks and read the latest balance, UTXOs, and full transaction history for any address through the API. Latest balances and address activity are available across EVM, UTXO, XRP, Solana, and Kaspa chains; full per-address transaction history covers EVM (Ethereum, Ethereum Classic, BSC, Polygon, Tron) and the UTXO chains (Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash). This gives a wallet backend everything it needs to reflect balances and history without running a node.

Does the API let me send transactions, and does it estimate fees?

Yes. You can prepare and broadcast transactions and get accurate fee estimates, with real-time confirmation events. Fee estimation is available for EVM, UTXO, and XRP chains, EVM transactions can be prepared and simulated before signing, and any signed transaction can be broadcast through the API.

Is there a managed or ready-made wallet, or do I build my own?

The CryptoAPIs Wallet-as-a-Service is a set of REST APIs for building your own wallet backend, not a finished wallet app. The managed wallet product moved to CryptoAPIs' sister company Vaultody, a non-custodial MPC/TSS wallet with approval policies and compliance built in. Choose the API if you want to build wallet functionality yourself; choose Vaultody if you want a ready-made non-custodial wallet.

Which blockchains does the CryptoAPIs Blockchain Events API support?

Blockchain Events covers 20+ blockchains across EVM, UTXO, and account-based networks. The EVM chains are Ethereum, Ethereum Classic, BNB Smart Chain, Polygon, Avalanche C-Chain, Tron, Arbitrum, Base, and Optimism. UTXO chains include Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, and Zcash, plus XRP, Solana, and Kaspa. Both mainnet and testnet networks are available for most chains.

Does the Blockchain Events API support Solana?

Yes. Solana is a supported chain for Blockchain Events on both mainnet and devnet, alongside XRP and Kaspa. You can subscribe to events and receive callbacks for Solana activity through the same unified subscription flow used for the EVM and UTXO chains.

What blockchain event types can I subscribe to?

You can subscribe to confirmed coin (native) transactions, unconfirmed coin transactions, internal transactions, and token transactions for an address, as well as newly mined blocks. Confirmed coin, internal, and token transaction events also offer an each-confirmation variant that fires on every confirmation. For UTXO chains, callbacks report direction (incoming or outgoing) based on input/output address matching.

How are event notifications delivered, and are the callbacks secure?

Events are delivered as HTTPS POST callbacks (webhooks) to a URL you register. The callback URL must use HTTPS and match a domain you verify in the Dashboard beforehand. You can optionally set a callback secret key so each request carries an HMAC-SHA256 x-signature header you can verify, and every callback includes an idempotencyKey so you can safely deduplicate.

What happens if my callback endpoint is down when an event fires?

CryptoAPIs retries failed callbacks with exponential backoff. Each callback allows a 5-second response timeout, and up to 5 retries follow roughly a 5, 10, 20, 40, and 80-minute schedule. If all retries fail, every subscription sharing that event type and callback URL is marked disabled, so you should monitor delivery and re-activate subscriptions as needed.

Which blockchains does the CryptoAPIs Transaction Simulator support?

The Transaction Simulator supports EVM blockchains only. You can simulate transactions on EVM mainnet and testnet networks to preview how they will behave before broadcasting. Non-EVM chains such as Bitcoin, Solana, and XRP are not covered by the simulator.

Does the transaction-simulator API support Solana?

No. The simulator is EVM-only, so Solana transactions cannot be simulated through it. Only EVM-based networks (mainnet and testnet) are supported. If you need another network, the page provides a 'Request additional blockchains' option.

Can I estimate gas and catch transaction reverts before broadcasting?

Yes. Simulating an EVM transaction lets you preview its behavior, estimate gas usage, and detect failures or reverts before it ever hits the chain. This helps you optimize gas fees and prevent costly out-of-gas or reverted transactions. It runs against realistic mainnet state without spending real funds.

How does the simulator fit with preparing and broadcasting a transaction?

The simulator works alongside CryptoAPIs' Prepare Transactions and Blockchain Fees products for EVM chains. A typical flow is to prepare an EVM transaction, simulate it to confirm expected behavior and fees, then broadcast the signed transaction. This lets you validate inputs, outputs, and structure before going on-chain.

Is the Transaction Simulator generally available or in early access?

The live page presents the multi-protocol simulator as early access, inviting users to 'be among the first' to test EVM transactions. In practice, EVM transaction simulation is the capability available today. Additional protocols are not yet available, though you can request other blockchains from the page.

Which blockchains does the CryptoAPIs Transactions Data API support?

The Transactions Data API covers 20+ blockchains across four architectures. This includes EVM chains (Ethereum, Ethereum Classic, BNB Smart Chain, Polygon, Avalanche C-Chain, Tron, Arbitrum, Base, Optimism), UTXO chains (Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash), plus XRP, Solana, and Kaspa. Both mainnet and testnet networks are available for most chains.

Does the Transactions Data API support Solana?

Yes. Solana is a live chain for the Transactions Data API, alongside XRP and Kaspa. You can retrieve detailed transaction data on Solana mainnet and its devnet network.

What data does the Transactions Data API return for a transaction?

It returns comprehensive details for any provided transaction, including the participating addresses (senders and recipients). This lets developers and businesses track and analyze blockchain activity and integrate transaction details into their applications. Coverage spans EVM, UTXO, XRP, Solana, and Kaspa chains.

Does the Transactions Data API cover Bitcoin and other UTXO chains?

Yes. UTXO chains are fully supported for transactions data, including Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, and Zcash. Both mainnet and testnet networks are available for these chains.

Can I query transactions on both mainnet and testnet?

Yes. Most supported chains expose both a mainnet and a test network, such as Ethereum mainnet and Sepolia, Bitcoin mainnet and testnet, and Solana mainnet and devnet. Kaspa is currently mainnet only.

Which blockchains does the Address History API support?

The Address History API covers two families of chains. On the account-based side it supports Ethereum, Ethereum Classic, BNB Smart Chain, Polygon, and Tron; on the UTXO side it supports Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, and Zcash. All of these are available on both mainnet and their respective testnets.

Does the Address History API support Solana?

Address History focuses on the EVM and UTXO chains plus XRP for time-ranged historical transaction data. Solana on-chain data (addresses, transactions, balances) is available through the Crypto APIs Solana endpoints; check the docs for the exact historical coverage per chain, as it varies by network.

Do I have to sync an address before I can query its history?

Yes. Address history requires you to first register (sync) the address you want to track, after which its full transaction history becomes queryable. You can add an address with the Sync Address endpoint, list your synced addresses, and later activate or delete them. Once synced, you can pull confirmed transactions, statistics, and token or internal-transaction data for that address.

How far back does the historical data go?

Address History returns the full history of a synced address from the Genesis block up to the present. For each address you can list all confirmed transactions (including in ascending or descending order, or from a given timestamp) and retrieve aggregate statistics across its entire history.

Can I get token transfers and internal transactions for an address?

Yes, on the EVM chains. For Ethereum, Ethereum Classic, BNB Smart Chain, Polygon, and Tron you can list an address's token transfers, its internal transactions, and the tokens it holds. UTXO chains such as Bitcoin and Litecoin instead expose transaction history and unspent outputs (UTXOs) rather than token or internal-transaction data.

What is x402?

x402 is an open protocol for paying for HTTP APIs with stablecoin, using the standard 402 Payment Required response. CryptoAPIs runs both halves as a managed service: the buyer side (an agent or app pays a 402-gated endpoint) and the facilitator side (verifying and settling those payments on-chain). It lets software pay for individual API requests without accounts or invoices.

Is x402 on CryptoAPIs custodial — do you hold my keys?

No. x402 on CryptoAPIs is fully non-custodial. The buyer holds its own key and signs every payment locally; there is deliberately no /sign endpoint. CryptoAPIs derives and monitors the wallet address and enforces spending policy, but never holds the private key. On the merchant side the facilitator settles with its own gas wallet and can never move funds the buyer did not authorize.

Which blockchains and assets does x402 support?

x402 payments settle in USDC stablecoin. The live networks are published per family by the merchant supported-assets endpoint; a network that is announced but not yet operational shows an empty signer set. EVM networks such as Base are supported, with additional families rolling out.

How does an agent pay for a 402-gated endpoint?

Register an agent wallet, then call the buyer authorize endpoint with the merchant's payment requirements. CryptoAPIs returns the exact payload to sign locally (EIP-712 on EVM). Your client signs it with its own key and retries the request with the signed payment attached. The buyer SDK, the x402_pay MCP tool, and the agent plugin wrap this register → authorize → sign → retry flow for you.

How do I charge for my own API with x402?

Use the CryptoAPIs x402 merchant SDK (Express, Hono or Next.js). When an unpaid request arrives, your endpoint answers with a 402 challenge describing the price; the buyer authorizes and signs it, and the CryptoAPIs facilitator verifies and settles the payment on-chain. You set your own price per endpoint, paid in USDC. The merchant SDK is non-custodial and holds no keys.

Are there spending limits for x402 buyer wallets?

Yes. A buyer wallet supports optional per-transaction, daily and monthly limits, set when you create the wallet or via a later update. A wallet created with no limits receives conservative default safety caps so it is never unlimited by accident. The buyer budget is advisory; the facilitator remains the hard settlement gate.

Which blockchains does the Address Latest API support?

The Address Latest API covers 20+ blockchains across EVM, UTXO, and account-based networks. EVM chains include Ethereum, Ethereum Classic, BNB Smart Chain, Polygon, Avalanche C-Chain, Tron, Arbitrum, Base, and Optimism; UTXO chains include Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, and Zcash; plus XRP, Solana, and Kaspa. Each is available on both mainnet and its testnet where one exists.

Does the Address Latest API support Solana?

Yes. Solana is supported by the Address Latest API through a dedicated Solana handler, on both mainnet and devnet. You can retrieve the current balance and latest transaction state for a Solana address in real time.

What can I retrieve with the Address Latest endpoints?

Address Latest returns the current on-chain state for a specific address in real time, including its balance and recent transaction activity. Depending on the blockchain, this includes confirmed and unconfirmed transactions, unspent transaction outputs (UTXOs) for UTXO chains, internal transactions for EVM chains, and the next available nonce for EVM accounts. It is designed for looking up an address's latest state rather than deep historical archives.

How is the Address Latest API priced?

Every API request consumes credits, and the exact amount depends on the endpoint and the blockchain, with the consumed amount returned in the x-credits-consumed response header. Cost scales by a per-blockchain multiplier relative to a baseline chain (Ethereum for EVM, Bitcoin for UTXO). After your monthly credit allocation is used up, usage continues automatically under pay-as-you-go billing.

Does Address Latest work on testnets as well as mainnets?

Yes. Address Latest works on both mainnets and testnets for the supported chains, so you can develop and test against networks like Ethereum Sepolia, Bitcoin testnet, and Solana devnet before going to production. Kaspa is the exception, offered on mainnet only.

What can the Block Data API do?

The Block Data API retrieves data for individual blockchain blocks and the transactions recorded in them. You can get block details by block hash or height, fetch the last mined block, list the latest mined blocks, and list the transactions contained in a given block or block height. All endpoints are read-only GET requests through a single point of integration.

Which blockchains does the Block Data API support?

Block data is available for EVM chains (such as Ethereum and other EVM networks), UTXO chains (such as Bitcoin, Litecoin, Dogecoin and similar), and XRP. It is offered on both mainnets and testnets across the networks Crypto APIs supports.

Can I list all transactions inside a specific block?

Yes. You can list the transactions in a block by either the block hash or the block height, so you can enumerate every transaction recorded in that block. This works across the supported EVM, UTXO, and XRP networks.

How do I get the latest or most recently mined block?

The API provides endpoints to get the last mined block and to list the latest mined blocks, returning up-to-date information about current blocks at the time of the request. These are available across the supported EVM, UTXO, and XRP networks on mainnets and testnets.

Does the Block Data API support Solana?

The Block Data product covers EVM chains, UTXO chains, and XRP for block-level queries. Solana block data is not part of this product's live block-data endpoints. If you need Solana data, check the transactions-data and contracts products, which include Solana coverage.

Which blockchains does the CryptoAPIs Contracts API support?

The Contracts API returns token details by contract address on Ethereum, Ethereum Classic, and Binance Smart Chain (all EVM chains), plus Solana. Each EVM chain is available on both mainnet and its test network (Sepolia, Mordor, and BSC testnet), and Solana is available on mainnet and devnet. These are the only chains covered by the Contracts product today.

Does the CryptoAPIs Contracts API support Solana tokens?

Yes. There is a dedicated Solana endpoint that returns token details by contract address on Solana mainnet and devnet. It is a separate route from the EVM endpoint, so Solana SPL token metadata is supported directly.

What token metadata can I get from a contract address?

For a given token contract address you can retrieve the token's name, symbol, standard, decimals, and total supply. This is the core capability of the Get Token Details by Contract Address endpoint. It is a read-only metadata lookup, not a full contract source or ABI download.

Can I decode a contract ABI or read arbitrary contract state with this API?

No. The Contracts product is scoped to retrieving token metadata (name, symbol, standard, decimals, total supply) by contract address. It does not expose ABI decoding, source code, event log decoding, or arbitrary read-calls to contract methods. For broader on-chain data, CryptoAPIs offers separate transactions data and blockchain data services.

How much does a token-details lookup cost in credits?

Credit cost per token-details request varies by chain: Ethereum is 30 credits, Ethereum Classic 39, and Binance Smart Chain 75, while Solana is 75. These figures are indicative and may change; the exact credits spent are returned in each response's headers.

Which blockchains does the Crypto APIs blockchain fees API support?

The fee recommendations API covers 20+ blockchains through a single integration — EVM chains (such as Ethereum, BNB Smart Chain, Polygon, Arbitrum, Base, Optimism), UTXO chains (Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash), plus XRP, Tron, Tezos, Solana and Kaspa. It returns recommended fee rates per chain so you can build and broadcast with an appropriate fee.

Does the blockchain fees API support EIP-1559 gas fee recommendations for Ethereum?

Yes. For EVM chains such as Ethereum, Arbitrum, Base, and Optimism you can retrieve EIP-1559 style fee recommendations, including priority-based estimates. The API returns fee levels by priority (slow, standard, fast) so you can choose the tradeoff between cost and confirmation speed.

Can I estimate Bitcoin and other UTXO transaction fees with Crypto APIs?

Yes. The API provides fee recommendations for six UTXO chains: Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, and Zcash. It returns recommended fee rates so you can build and broadcast a transaction with an appropriate fee for current network conditions.

Does the Crypto APIs fee API support Solana?

Yes. Fee recommendations are available for Solana, alongside EVM chains, UTXO chains, XRP, Tron, Tezos and Kaspa. The endpoint returns recommended fee levels so you can attach an appropriate fee before broadcasting.

Are testnets covered, or only mainnet fee data?

Both mainnet and testnet are supported for the covered chains. For example, Ethereum offers mainnet and Sepolia, Bitcoin offers mainnet and testnet, and XRP offers mainnet and testnet, so you can estimate fees in a test environment before going to production.

Does the Blockchain Utils API support Solana?

No. The Blockchain Utils tools cover 11 protocols — Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash, Ethereum, Ethereum Classic, BNB Smart Chain (BSC), Tron, and XRP — on both mainnet and testnet. Solana is not currently among the chains served by the address-validation, transaction-decoding, or address-derivation endpoints.

How do I validate a crypto address with Crypto APIs?

Use the validate-address action, which checks whether an address is well-formed for its chain. It works across EVM chains (Ethereum, Ethereum Classic, BNB Smart Chain, Tron), UTXO chains (Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash), and XRP, on mainnet and testnet. This is a formatting/validity check, distinct from the separate Verify Address product used for AML screening.

Can the API decode a raw transaction hex?

Yes. The decode-raw-transaction action parses a raw transaction hex into its structured fields. It is available for EVM chains (Ethereum, Ethereum Classic, BNB Smart Chain, Tron) and UTXO chains (Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash) on mainnet and testnet.

Does Crypto APIs support XRP X-Address encoding and decoding?

Yes. For XRP you can encode a classic address plus destination tag into an X-Address, and decode an X-Address back into its classic address and tag. Both operations are available on XRP mainnet and testnet.

Can I derive wallet addresses from an xPub without syncing?

Yes. The derive-addresses endpoint generates up to 10 receiving addresses (or change addresses for UTXO chains) directly from an extended public key such as an xPub, yPub, or zPub, without syncing the wallet. It supports Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash, Ethereum, Ethereum Classic, BNB Smart Chain, Tron, and XRP.

Does the Prepare Transactions API support Solana or Bitcoin?

No. The Prepare Transactions endpoint is EVM-only, covering Ethereum and other EVM-based blockchains. There is no prepare route for Solana, Bitcoin, or other UTXO/non-EVM chains on this product.

Can I prepare ERC-20 token and NFT transfers, or only native coin transfers?

Yes, both. The Prepare Transactions API supports native EVM coin transfers as well as fungible token (ERC-20) and non-fungible token (NFT) transfers from any address. It builds the unsigned transaction payload ready for you to sign locally.

How do I go from a prepared transaction to a confirmed on-chain transaction?

Prepare the unsigned EVM transaction with Prepare Transactions, sign it, then submit it with the Broadcast Signed Transaction endpoint. You can also estimate gas costs beforehand using the EVM Blockchain Fees endpoint.

Can I estimate gas fees for an EVM transaction before sending it?

Yes. CryptoAPIs provides an EVM Blockchain Fees endpoint to retrieve current fee estimates so you can set gas parameters before signing and broadcasting. This pairs directly with the Prepare Transactions workflow.

Can I test what an EVM transaction will do before broadcasting it?

Yes. CryptoAPIs offers an EVM transaction simulation endpoint that lets you preview the outcome of a transaction before it is signed and broadcast. This helps you catch failures or unexpected results without spending gas on-chain.

What is the CryptoAPIs Broadcast Transactions API and how does it work?

It lets you push a transaction you have already signed locally to the blockchain network through a single specialized endpoint. You keep your private keys on your side, sign the raw transaction offline, and CryptoAPIs relays the signed payload to a node for you. This means CryptoAPIs never handles your keys while still giving you node access for broadcasting.

Which blockchains does the Broadcast Transactions API support?

Broadcasting is available across 20+ blockchains. This covers EVM chains (Ethereum, Ethereum Classic, BNB Smart Chain, Polygon, Avalanche C-Chain, Tron, Arbitrum, Base, and Optimism), UTXO chains (Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, and Zcash), plus XRP, Solana, and Kaspa.

Does the Broadcast Transactions API support Solana and Bitcoin?

Yes. Solana is supported for broadcasting locally signed transactions, as are Bitcoin and the other UTXO chains (Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash). XRP and Kaspa are also covered, alongside the EVM chains.

Can I broadcast transactions on testnets as well as mainnet?

Yes. Broadcasting works on both mainnets and testnets across the networks CryptoAPIs supports. For example EVM chains offer testnets such as Sepolia, Amoy, Fuji, Nile and Mordor, and UTXO chains such as Bitcoin, Litecoin and Dogecoin offer their standard testnets. Kaspa is currently mainnet only.

Does broadcasting a transaction with CryptoAPIs mean they hold my private keys?

No. The model is non-custodial for signing: you sign the transaction locally with your own keys and only send the already-signed transaction to the broadcast endpoint. CryptoAPIs relays that signed payload to a node and never sees or stores your private keys.