# io.github.CryptoAPIs-io/mcp (remote · ai.cryptoapis.io) Combined Crypto APIs MCP server — all 14 products in one process - Trust score: 67/100 (medium) - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-10-23 ## Components - remote · `ai.cryptoapis.io`: 67/100 (this document), [markdown](https://verifymcp.io/servers/cryptoapis-io-mcp/ai.md), [page](https://verifymcp.io/servers/cryptoapis-io-mcp/ai) - npm · `@cryptoapis-io/mcp`: 50/100, [markdown](https://verifymcp.io/servers/cryptoapis-io-mcp/cryptoapis-io-mcp.md), [page](https://verifymcp.io/servers/cryptoapis-io-mcp/cryptoapis-io-mcp) ## Channel facts - Endpoint: `https://ai.cryptoapis.io/mcp` - Transports: `streamable-http` - Auth: `required (not validated)` - Version: `0.5.0` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-10-23. - **Endpoint Security**: 71/100 - The endpoint's TLS certificate is valid, in date, and uses a strong key. - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. - HSTS check failed: the Strict-Transport-Security header is absent. - DNSSEC check failed: this domain isn't protected by DNSSEC. - **Transport & Reachability**: 100/100 - Verified streamable-http transport via a live MCP handshake. - **Schema Quality & AI Usability**: 56/100 - AI-judged instruction clarity (good). - Context-footprint check failed: tool/resource definitions use about 18804 tokens (~313/item across 60 items; 60 tools + 0 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 7/100 - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - We read all 60 captured tool definition(s), and no name or description among them implies an irreversible operation. - An AI judge read all 60 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. ## Install ### How do I install the io.github.CryptoAPIs-io/mcp server? io.github.CryptoAPIs-io/mcp is a hosted endpoint at https://ai.cryptoapis.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation. ### Claude ```bash claude mcp add --transport http cryptoapis-io-mcp 'https://ai.cryptoapis.io/mcp' ``` ### Cursor ```json { "mcpServers": { "cryptoapis-io-mcp": { "url": "https://ai.cryptoapis.io/mcp" } } } ``` ### VS Code ```json { "servers": { "cryptoapis-io-mcp": { "type": "http", "url": "https://ai.cryptoapis.io/mcp" } } } ``` ### Codex ```toml [mcp_servers.cryptoapis-io-mcp] url = "https://ai.cryptoapis.io/mcp" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "cryptoapis-io-mcp": { "type": "remote", "url": "https://ai.cryptoapis.io/mcp", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add cryptoapis-io-mcp --url 'https://ai.cryptoapis.io/mcp' --transport streamable-http ``` ### Hermes ```yaml mcp_servers: cryptoapis-io-mcp: url: "https://ai.cryptoapis.io/mcp" ``` ### Netclaw ```json { "McpServers": { "cryptoapis-io-mcp": { "Transport": "http", "Url": "https://ai.cryptoapis.io/mcp" } } } ``` ### Vellum ```bash assistant mcp add cryptoapis-io-mcp -t streamable-http -u 'https://ai.cryptoapis.io/mcp' ``` ### Other ```json { "mcpServers": { "cryptoapis-io-mcp": { "type": "http", "url": "https://ai.cryptoapis.io/mcp" } } } ``` The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs. ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-10-22 (score 67, +1) - [functional improvement] Stability: unverified → 0.03 ### 2026-10-21 (score 66) First indexed and scored. ## MCP tools (60) ### `address_history__manage_address` (~512 tokens) Manage synced addresses for Address History APIs. Cursor pagination for 'list': use 'nextStartingAfter' as 'startingAfter'. Actions: • sync: Add new address to sync (requires 'address') • list: Get all synced addresses for blockchain/network • activate: Reactivate a paused address (requires 'address') • delete: Remove synced address (requires 'address') Blockchain → Networks: • ethereum: mainnet, sepolia • ethereum-classic: mainnet, mordor • binance-smart-chain: mainnet, testnet • polygon: mainnet, amoy • tron: mainnet, nile • avalanche (C-Chain): mainnet, fuji • arbitrum: mainnet, sepolia • base: mainnet, sepolia • optimism: mainnet, sepolia • bitcoin: mainnet, testnet • bitcoin-cash: mainnet, testnet • litecoin: mainnet, testnet • dogecoin: mainnet, testnet • dash: mainnet, testnet • zcash: mainnet, testnet Note: 'sync', 'activate', 'delete' actions require confirmation. They return a preview with a one-time token instead of executing immediately. Credits by action (source: OpenAPI): • activate: 30 • delete: 30 • list: 30 • sync: 30 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `action` (string, required): Action to perform: sync, list, activate, delete - `address` (string): Address (required for sync, activate, delete) - `blockchain` (string, required): Blockchain protocol - `confirmationToken` (string): Confirmation token from a previous preview response. IMPORTANT: You MUST present the warning and impact to the user and receive their explicit approval before passing this token. NEVER auto-confirm —… - `context` (string): Optional context for the request - echoed back in response - `limit` (integer): Number of items to return (max 50) - `network` (string, required): Network name - `sortingOrder` (string): Sort order: ascending (oldest first) or descending (newest first) - `startingAfter` (string): Pagination cursor - use nextStartingAfter from previous response ### `address_history__evm_address_history` (~609 tokens) Query EVM address full history (requires synced address). Cursor pagination: use 'nextStartingAfter' from response as 'startingAfter'. Actions & supported blockchains: • get-statistics: ethereum, ethereum-classic • list-transactions: ethereum, ethereum-classic, binance-smart-chain, polygon, tron • list-transactions-by-timestamp: ethereum, ethereum-classic (requires timestamp) • list-token-transfers: ethereum, polygon, tron, ethereum-classic, binance-smart-chain • list-internal-transactions: ethereum, polygon, tron, ethereum-classic, binance-smart-chain • list-tokens: ethereum, polygon, tron, ethereum-classic, binance-smart-chain Blockchain → Networks: • ethereum: mainnet, sepolia • ethereum-classic: mainnet, mordor • binance-smart-chain: mainnet, testnet • polygon: mainnet, amoy • tron: mainnet, nile • avalanche (C-Chain): mainnet, fuji • arbitrum: mainnet, sepolia • base: mainnet, sepolia • optimism: mainnet, sepolia Credits by action (source: OpenAPI): • get-statistics: binance-smart-chain 575, ethereum 230, ethereum-classic 299, polygon 460, tron 345 • list-internal-transactions: binance-smart-chain 825, ethereum 330, ethereum-classic 429, polygon 660, tron 495 • list-token-transfers: binance-smart-chain 575, ethereum 230, ethereum-classic 299, polygon 460, tron 345 • list-tokens: binance-smart-chain 575, ethereum 230, ethereum-classic 299, polygon 460, tron 345 • list-transactions: binance-smart-chain 325, ethereum 130, ethereum-classic 169, polygon 260, tron 195 • list-transactions-by-timestamp: binance-smart-chain 575, ethereum 230, ethereum-classic 299, polygon 460, tron 345 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `action` (string, required): Action to perform - `address` (string, required): Address to query - `blockchain` (string, required): Blockchain protocol - `context` (string): Optional context for the request - echoed back in response - `limit` (integer): Number of items to return (max 50) - `network` (string, required): Network name - `sortingOrder` (string): Sort order: ascending (oldest first) or descending (newest first) - `startingAfter` (string): Pagination cursor - use nextStartingAfter from previous response - `timestamp` (integer): Unix timestamp (starting point) for list-transactions-by-timestamp action ### `address_history__utxo_address_history` (~537 tokens) Query UTXO address full history (requires synced address). Pagination: • list-transactions, list-transactions-by-timestamp: cursor pagination (use 'nextStartingAfter' → 'startingAfter') • list-unspent-outputs: offset pagination (use 'offset', response has 'total') Actions & supported blockchains: • get-statistics: bitcoin, bitcoin-cash • list-transactions: bitcoin, bitcoin-cash, litecoin, dogecoin, dash, zcash • list-transactions-by-timestamp: bitcoin, bitcoin-cash (requires timestamp) • list-unspent-outputs: bitcoin, bitcoin-cash, litecoin, dogecoin, dash, zcash (uses offset pagination) Blockchain → Networks: • bitcoin: mainnet, testnet • bitcoin-cash: mainnet, testnet • litecoin: mainnet, testnet • dogecoin: mainnet, testnet • dash: mainnet, testnet • zcash: mainnet, testnet Credits by action (source: OpenAPI): • get-statistics: bitcoin 530, bitcoin-cash 689, dash 583, dogecoin 583, litecoin 583, zcash 689 • list-transactions: bitcoin 130, bitcoin-cash 169, dash 143, dogecoin 143, litecoin 143, zcash 169 • list-transactions-by-timestamp: bitcoin 530, bitcoin-cash 689, dash 583, dogecoin 583, litecoin 583, zcash 689 • list-unspent-outputs: bitcoin 530, bitcoin-cash 689, dash 583, dogecoin 583, litecoin 583, zcash 689 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `action` (string, required): Action to perform - `address` (string, required): Address to query - `blockchain` (string, required): Blockchain protocol - `context` (string): Optional context for the request - echoed back in response - `limit` (integer): Number of items to return (max 50) - `network` (string, required): Network name - `offset` (integer): Pagination offset - `sortingOrder` (string): Sort order: ascending (oldest first) or descending (newest first) - `startingAfter` (string): Pagination cursor - use nextStartingAfter from previous response - `timestamp` (integer): Unix timestamp (starting point) for list-transactions-by-timestamp action ### `address_history__system_info` (~174 tokens) CryptoAPIs reference documentation — no API call, no credits consumed. Actions: • blockchains — Supported blockchains, networks, products per chain, denominations, fiat currencies • errors — Complete error code table (HTTP status, error code, message) • credits — Credit charging structure, cost multipliers per blockchain, monitoring & operations taxes (xPub, synced addresses, blockchain events), pay-as-you-go • callbacks — Webhook mechanics: URL requirements, retry strategy (5 retries, exponential backoff), HMAC security, idempotency • limits — Throughput soft/hard limits per plan, 2.1x penalty multiplier, rate limiting behavior Input parameters: - `action` (string, required): Reference topic to retrieve - `context` (string): Optional context for the request - echoed back in response ### `address_latest__evm_address_latest` (~696 tokens) Query latest EVM address data (last 14 days). Cursor pagination: use 'nextStartingAfter' from response as 'startingAfter'. Actions & supported blockchains: • get-balance: ethereum, ethereum-classic, binance-smart-chain, tron, polygon, avalanche (C-Chain), arbitrum, base, optimism • get-next-nonce: ethereum, ethereum-classic, binance-smart-chain (mainnet, mordor, testnet, sepolia) • list-transactions: ethereum, ethereum-classic, binance-smart-chain, arbitrum, polygon, avalanche (C-Chain), base, optimism, tron • list-token-transfers: ethereum, ethereum-classic, binance-smart-chain, tron, polygon, avalanche (C-Chain), arbitrum, base, optimism • list-internal-transactions: ethereum, ethereum-classic, binance-smart-chain, polygon, avalanche (C-Chain), arbitrum, base, optimism, tron Blockchain → Networks: • ethereum: mainnet, sepolia • ethereum-classic: mainnet, mordor • binance-smart-chain: mainnet, testnet • polygon: mainnet, amoy • tron: mainnet, nile • avalanche (C-Chain): mainnet, fuji • arbitrum: mainnet, sepolia • base: mainnet, sepolia • optimism: mainnet, sepolia Credits by action (source: OpenAPI): • get-balance: arbitrum 48, avalanche 54, base 36, binance-smart-chain 75, ethereum 30, ethereum-classic 39, optimism 42, polygon 60, tron 45 • get-next-nonce: arbitrum 32, avalanche 36, base 24, binance-smart-chain 50, ethereum 20, ethereum-classic 26, optimism 28, polygon 40, tron 30 • list-internal-transactions: arbitrum 512, avalanche 576, base 384, binance-smart-chain 800, ethereum 320, ethereum-classic 416, optimism 448, polygon 640, tron 480 • list-token-transfers: arbitrum 352, avalanche 396, base 264, binance-smart-chain 550, ethereum 220, ethereum-classic 286, optimism 308, polygon 440, tron 330 • list-transactions: arbitrum 192, avalanche 216, base 144, binance-smart-chain 300, ethereum 120, ethereum-classic 156, optimism 168, polygon 240, tron 180 Credits are indicative only and may change at any time. The actual credits spent for each API request are… Input parameters: - `action` (string, required): Action to perform - `address` (string, required): Address to query - `blockchain` (string, required): Blockchain protocol - `context` (string): Optional context for the request - echoed back in response - `limit` (integer): Number of items to return (max 50) - `network` (string, required): Network name - `sortingOrder` (string): Sort order: ascending (oldest first) or descending (newest first) - `startingAfter` (string): Pagination cursor - use nextStartingAfter from previous response ### `address_latest__utxo_address_latest` (~493 tokens) Query latest UTXO address data (last 14 days). • get-balance: no pagination • list-transactions: cursor pagination - use 'nextStartingAfter' from response as 'startingAfter' • list-unconfirmed-transactions: offset pagination - use 'limit' and 'offset' (lists unconfirmed/mempool transactions) Actions & supported blockchains: • get-balance: bitcoin, bitcoin-cash, litecoin, dash, dogecoin, zcash • list-transactions: bitcoin, bitcoin-cash, dash, dogecoin, litecoin, zcash • list-unconfirmed-transactions: bitcoin, bitcoin-cash, litecoin, dogecoin, dash, zcash Blockchain → Networks: • bitcoin: mainnet, testnet • bitcoin-cash: mainnet, testnet • litecoin: mainnet, testnet • dogecoin: mainnet, testnet • dash: mainnet, testnet • zcash: mainnet, testnet Credits by action (source: OpenAPI): • get-balance: bitcoin 510, bitcoin-cash 612, dash 561, dogecoin 561, litecoin 561, zcash 663 • list-transactions: bitcoin 110, bitcoin-cash 132, dash 121, dogecoin 121, litecoin 121, zcash 143 • list-unconfirmed-transactions: bitcoin 110, bitcoin-cash 132, dash 121, dogecoin 121, litecoin 121, zcash 143 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `action` (string, required): Action to perform: get-balance, list-transactions, list-unconfirmed-transactions - `address` (string, required): Address to query - `blockchain` (string, required): Blockchain protocol - `context` (string): Optional context for the request - echoed back in response - `limit` (integer): Number of items to return (max 50) - `network` (string, required): Network name - `offset` (integer): Pagination offset - `sortingOrder` (string): Sort order: ascending (oldest first) or descending (newest first) - `startingAfter` (string): Pagination cursor - use nextStartingAfter from previous response ### `address_latest__solana_address_latest` (~270 tokens) Query latest Solana address data (last 14 days). Cursor pagination: use 'nextStartingAfter' from response as 'startingAfter'. Actions: • get-balance: Get address SOL balance • list-transactions: Get address transactions • list-tokens: Get SPL tokens held by address Networks: mainnet, devnet Credits by action (source: OpenAPI): • get-balance: solana 75 • list-tokens: solana 120 • list-transactions: solana 90 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `action` (string, required): Action to perform: get-balance, list-transactions, list-tokens - `address` (string, required): Solana address to query - `context` (string): Optional context for the request - echoed back in response - `limit` (integer): Number of items to return (max 50) - `network` (string, required): Network name: mainnet or devnet - `sortingOrder` (string): Sort order: ascending (oldest first) or descending (newest first) - `startingAfter` (string): Pagination cursor - use nextStartingAfter from previous response ### `address_latest__xrp_address_latest` (~270 tokens) Query latest XRP (Ripple) address data. Cursor pagination: use 'nextStartingAfter' from response as 'startingAfter'. Actions: • get-balance: Get address XRP balance • list-transactions: Get address transactions • get-next-sequence: Get next available sequence number for transactions Networks: mainnet, testnet Credits by action (source: OpenAPI): • get-balance: xrp 20 • get-next-sequence: xrp 20 • list-transactions: xrp 110 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `action` (string, required): Action to perform: get-balance, list-transactions, get-next-sequence - `address` (string, required): XRP address to query - `context` (string): Optional context for the request - echoed back in response - `limit` (integer): Number of items to return (max 50) - `network` (string, required): Network name: mainnet or testnet - `sortingOrder` (string): Sort order: ascending (oldest first) or descending (newest first) - `startingAfter` (string): Pagination cursor - use nextStartingAfter from previous response ### `address_latest__kaspa_address_latest` (~241 tokens) Query latest Kaspa address data. Cursor pagination: use 'nextStartingAfter' from response as 'startingAfter'. Actions: • get-balance: Get address KAS balance • list-transactions: Get address transactions Networks: mainnet (only) Credits by action (source: OpenAPI): • get-balance: kaspa 918 • list-transactions: kaspa 918 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `action` (string, required): Action to perform: get-balance, list-transactions - `address` (string, required): Kaspa address to query - `context` (string): Optional context for the request - echoed back in response - `limit` (integer): Number of items to return (max 50) - `network` (string, required): Network name: mainnet (only mainnet available) - `sortingOrder` (string): Sort order: ascending (oldest first) or descending (newest first) - `startingAfter` (string): Pagination cursor - use nextStartingAfter from previous response ### `address_latest__system_info` (~174 tokens) CryptoAPIs reference documentation — no API call, no credits consumed. Actions: • blockchains — Supported blockchains, networks, products per chain, denominations, fiat currencies • errors — Complete error code table (HTTP status, error code, message) • credits — Credit charging structure, cost multipliers per blockchain, monitoring & operations taxes (xPub, synced addresses, blockchain events), pay-as-you-go • callbacks — Webhook mechanics: URL requirements, retry strategy (5 retries, exponential backoff), HMAC security, idempotency • limits — Throughput soft/hard limits per plan, 2.1x penalty multiplier, rate limiting behavior Input parameters: - `action` (string, required): Reference topic to retrieve - `context` (string): Optional context for the request - echoed back in response ### `aml__aml` (~674 tokens) AML (Anti-Money Laundering) risk checks for addresses and transactions. Actions: • verify-address: Check if a blockchain address is flagged or associated with fraud, sanctions, ransomware, exploits, darknet markets, or other AML risk categories. Returns risk score, risk band, and the flagging sources. • screen-transaction: Screen a transaction against AML data. Returns whether the transaction is flagged, its risk score/band, and the flagged participant addresses with their roles, scores, severities and categories. • get-address-exposure: Get an address's exposure to risky entities/categories across the AML exposure graph. Params: blockchain, address. Costs 200,000 credits per request. • list-address-exposure-paths: List the paths connecting an address to risky entities in the AML exposure graph. Params: blockchain, address; optional rootAddress (only return routes originating from this flagged root address), limit (1-50, defaults to 10), startingAfter (pagination cursor). Costs 100,000 credits per page - pass the response's next cursor back as startingAfter to fetch subsequent pages. get-address-exposure and list-address-exposure-paths only support a subset of chains - see the blockchain parameter description. Note: the credit cost of these endpoints is significant — see credits below. Credits by action (source: OpenAPI): • get-address-exposure: 200000 • list-address-exposure-paths: 100000 • screen-transaction: 500000 • verify-address: 200000 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `action` (string, required): Action to perform - `address` (string): Blockchain address - required for verify-address, get-address-exposure, and list-address-exposure-paths - `blockchain` (string): Blockchain protocol - required for screen-transaction, get-address-exposure and list-address-exposure-paths. screen-transaction accepts: ethereum, ethereum-classic, binance-smart-chain, bitcoin, bitc… - `context` (string): Optional context for the request - echoed back in response - `limit` (integer): Number of exposure paths to return per page (1-50, defaults to 10) - applies to list-address-exposure-paths only - `rootAddress` (string): Only return routes that originate from this flagged root address (one of the roots[].rootAddress values returned by get-address-exposure) - optional, applies to list-address-exposure-paths only - `startingAfter` (string): Pagination cursor - pass the nextStartingAfter value from the previous response to fetch the next page; applies to list-address-exposure-paths only - `transactionHash` (string): Transaction hash to screen against AML data - required for screen-transaction ### `aml__system_info` (~173 tokens) CryptoAPIs reference documentation — no API call, no credits consumed. Actions: • blockchains — Supported blockchains, networks, products per chain, denominations, fiat currencies • errors — Complete error code table (HTTP status, error code, message) • credits — Credit charging structure, cost multipliers per blockchain, monitoring & operations taxes (xPub, synced addresses, blockchain events), pay-as-you-go • callbacks — Webhook mechanics: URL requirements, retry strategy (5 retries, exponential backoff), HMAC security, idempotency • limits — Throughput soft/hard limits per plan, 2.1x penalty multiplier, rate limiting behavior Input parameters: - `action` (string, required): Reference topic to retrieve - `context` (string): Optional context for the request - echoed back in response ### `block_data__evm_block_data` (~690 tokens) Get EVM block details (Block Data product). Actions: • get-block-by-height: Get block details by block height (number) • get-block-by-hash: Get block details by block hash • list-transactions-by-block-hash: List transactions in a block by block hash • list-transactions-by-block-height: List transactions in a block by block height • get-last-mined-block: Get the latest mined block details • list-latest-mined-blocks: List the latest mined blocks Blockchain → Networks: • ethereum: mainnet, sepolia • ethereum-classic: mainnet, mordor • binance-smart-chain: mainnet, testnet • polygon: mainnet, amoy • tron: mainnet, nile • avalanche (C-Chain): mainnet, fuji • arbitrum: mainnet, sepolia • base: mainnet, sepolia • optimism: mainnet, sepolia Credits by action (source: OpenAPI): • get-block-by-hash: arbitrum 48, avalanche 54, base 36, binance-smart-chain 75, ethereum 30, ethereum-classic 39, optimism 42, polygon 60, tron 45 • get-block-by-height: arbitrum 48, avalanche 54, base 36, binance-smart-chain 75, ethereum 30, ethereum-classic 39, optimism 42, polygon 60, tron 45 • get-last-mined-block: arbitrum 48, avalanche 54, base 36, binance-smart-chain 75, ethereum 30, ethereum-classic 39, optimism 42, polygon 60, tron 45 • list-latest-mined-blocks: arbitrum 48, avalanche 54, base 36, binance-smart-chain 75, ethereum 30, ethereum-classic 39, optimism 42, polygon 60, tron 45 • list-transactions-by-block-hash: arbitrum 48, avalanche 54, base 36, binance-smart-chain 75, ethereum 30, ethereum-classic 39, optimism 42, polygon 60, tron 45 • list-transactions-by-block-height: arbitrum 48, avalanche 54, base 36, binance-smart-chain 75, ethereum 30, ethereum-classic 39, optimism 42, polygon 60, tron 45 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `action` (string, required): Action to perform - `blockHash` (string): Block hash (required for get-block-by-hash, list-transactions-by-block-hash) - `blockHeight` (integer): Block height (required for get-block-by-height, list-transactions-by-block-height) - `blockchain` (string, required): Blockchain protocol - `context` (string): Optional context for the request - echoed back in response - `count` (integer): Number of blocks to return (for list-latest-mined-blocks) - `limit` (integer): Number of items to return (max 50) - `network` (string, required): Network name - `offset` (integer): Pagination offset ### `block_data__utxo_block_data` (~578 tokens) Get UTXO block details (Block Data product). Actions: • get-block-by-height: Get block details by block height (number) • get-block-by-hash: Get block details by block hash • list-transactions-by-block-height: List transactions in a block by block height • list-transactions-by-block-hash: List transactions in a block by block hash • get-last-mined-block: Get the latest mined block details • list-latest-mined-blocks: List the latest mined blocks Blockchain → Networks: • bitcoin: mainnet, testnet • bitcoin-cash: mainnet, testnet • litecoin: mainnet, testnet • dogecoin: mainnet, testnet • dash: mainnet, testnet • zcash: mainnet, testnet Credits by action (source: OpenAPI): • get-block-by-hash: bitcoin 20, bitcoin-cash 24, dash 22, dogecoin 22, litecoin 22, zcash 26 • get-block-by-height: bitcoin 20, bitcoin-cash 24, dash 22, dogecoin 22, litecoin 22, zcash 26 • get-last-mined-block: bitcoin 20, bitcoin-cash 24, dash 22, dogecoin 22, litecoin 22, zcash 26 • list-latest-mined-blocks: bitcoin 20, bitcoin-cash 24, dash 22, dogecoin 22, litecoin 22, zcash 26 • list-transactions-by-block-hash: bitcoin 20, bitcoin-cash 24, dash 22, dogecoin 22, litecoin 22, zcash 26 • list-transactions-by-block-height: bitcoin 20, bitcoin-cash 24, dash 22, dogecoin 22, litecoin 22, zcash 26 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `action` (string, required): Action to perform - `blockHash` (string): Block hash (required for get-block-by-hash, list-transactions-by-block-hash) - `blockHeight` (integer): Block height (required for get-block-by-height, list-transactions-by-block-height) - `blockchain` (string, required): Blockchain protocol - `context` (string): Optional context for the request - echoed back in response - `count` (integer): Number of blocks to return (for list-latest-mined-blocks) - `limit` (integer): Number of items to return (max 50) - `network` (string, required): Network name - `offset` (integer): Pagination offset ### `block_data__xrp_block_data` (~370 tokens) Get XRP block details (Block Data product). Path uses network only (no blockchain). Networks: mainnet, testnet. Actions: • get-block-by-height: Get block details by block height (number) • get-block-by-hash: Get block details by block hash • list-transactions-by-block-height: List transactions in a block by block height • list-transactions-by-block-hash: List transactions in a block by block hash • get-last-mined-block: Get the latest mined block details • list-latest-mined-blocks: List the latest mined blocks Credits by action (source: OpenAPI): • get-block-by-hash: 20 • get-block-by-height: 20 • get-last-mined-block: 20 • list-latest-mined-blocks: 20 • list-transactions-by-block-hash: 20 • list-transactions-by-block-height: 20 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `action` (string, required): Action to perform - `blockHash` (string): Block hash (required for get-block-by-hash, list-transactions-by-block-hash) - `blockHeight` (integer): Block height (required for get-block-by-height, list-transactions-by-block-height) - `context` (string): Optional context for the request - echoed back in response - `count` (integer): Number of blocks to return (for list-latest-mined-blocks) - `limit` (integer): Number of items to return (max 50) - `network` (string, required): Network name: mainnet or testnet - `offset` (integer): Pagination offset ### `block_data__system_info` (~174 tokens) CryptoAPIs reference documentation — no API call, no credits consumed. Actions: • blockchains — Supported blockchains, networks, products per chain, denominations, fiat currencies • errors — Complete error code table (HTTP status, error code, message) • credits — Credit charging structure, cost multipliers per blockchain, monitoring & operations taxes (xPub, synced addresses, blockchain events), pay-as-you-go • callbacks — Webhook mechanics: URL requirements, retry strategy (5 retries, exponential backoff), HMAC security, idempotency • limits — Throughput soft/hard limits per plan, 2.1x penalty multiplier, rate limiting behavior Input parameters: - `action` (string, required): Reference topic to retrieve - `context` (string): Optional context for the request - echoed back in response ### `blockchain_events__blockchain_events_manage` (~357 tokens) Manage existing webhook subscriptions for on-chain events. Use this to view, delete, or re-activate event subscriptions created via blockchain_events_create. Actions: • list-subscriptions: List all active subscriptions for a blockchain/network (paginated) • get-subscription: Get details of a specific subscription by its referenceId • delete-subscription: Remove a subscription (stops webhook delivery) • activate-subscription: Re-activate a previously deactivated subscription Note: 'delete-subscription', 'activate-subscription' actions require confirmation. They return a preview with a one-time token instead of executing immediately. Credits by action (source: OpenAPI): • activate-subscription: 12 • delete-subscription: 12 • get-subscription: 12 • list-subscriptions: 12 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `action` (string, required): Action to perform - `blockchain` (string): Blockchain (required for all actions) - `confirmationToken` (string): Confirmation token from a previous preview response. IMPORTANT: You MUST present the warning and impact to the user and receive their explicit approval before passing this token. NEVER auto-confirm —… - `context` (string): Optional context for the request - echoed back in response - `limit` (number): Max results per page (list-subscriptions only) - `network` (string): Network (required for all actions) - `offset` (number): Pagination offset (list-subscriptions only) - `referenceId` (string): Subscription reference ID (for get, delete, activate) ### `blockchain_events__blockchain_events_create` (~621 tokens) Create a webhook subscription for on-chain events. When the specified event occurs, CryptoAPIs sends a POST request to your callbackUrl with the event data. Subscriptions persist until deleted. Event types (supported blockchains vary per type — an invalid blockchain for the chosen eventType is rejected before calling the API): • address-coins-transactions-unconfirmed: fires when an unconfirmed coin transaction touches the address • address-coins-transactions-confirmed: fires once a coin transaction confirms (optionally on an exact confirmation via receiveCallbackOn) • address-coins-transactions-confirmed-each-confirmation: fires on every confirmation up to confirmationsCount (required) • address-tokens-transactions-confirmed: fires once a token transfer confirms • address-tokens-transactions-confirmed-each-confirmation: fires on every confirmation up to confirmationsCount (required) • address-internal-transactions-confirmed: fires once a confirmed internal (contract-internal) transaction touches the address • address-internal-transactions-confirmed-each-confirmation: fires on every confirmation up to confirmationsCount (required) • block-mined: fires on every new block (no address field) All event types except block-mined require an address. Note: 'create' actions require confirmation. They return a preview with a one-time token instead of executing immediately. Credits per call: 30 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `address` (string): Address to monitor (required for all event types except block-mined) - `allowDuplicates` (boolean): Whether to allow duplicate subscriptions for the same address/event. The API requires this field even though the spec marks it optional (verified live) — defaults to false. - `blockchain` (string, required): Blockchain protocol (e.g. bitcoin, ethereum); supported chains vary per eventType - `callbackSecretKey` (string): Secret key for HMAC-signing webhook payloads (recommended for verifying authenticity) - `callbackUrl` (string, required): Webhook callback URL - `confirmationToken` (string): Confirmation token from a previous preview response. IMPORTANT: You MUST present the warning and impact to the user and receive their explicit approval before passing this token. NEVER auto-confirm —… - `confirmationsCount` (integer): Number of confirmations to track, sending a callback on each one (required for the '-each-confirmation' event types) - `context` (string): Optional context for the request - echoed back in response - `eventType` (string, required): Event type to subscribe to - `network` (string, required): Network name (e.g. mainnet, testnet, sepolia); supported networks vary per eventType - `receiveCallbackOn` (integer): Exact confirmation number to receive the callback on (address-coins-transactions-confirmed, address-tokens-transactions-confirmed, address-internal-transactions-confirmed only) ### `blockchain_events__system_info` (~174 tokens) CryptoAPIs reference documentation — no API call, no credits consumed. Actions: • blockchains — Supported blockchains, networks, products per chain, denominations, fiat currencies • errors — Complete error code table (HTTP status, error code, message) • credits — Credit charging structure, cost multipliers per blockchain, monitoring & operations taxes (xPub, synced addresses, blockchain events), pay-as-you-go • callbacks — Webhook mechanics: URL requirements, retry strategy (5 retries, exponential backoff), HMAC security, idempotency • limits — Throughput soft/hard limits per plan, 2.1x penalty multiplier, rate limiting behavior Input parameters: - `action` (string, required): Reference topic to retrieve - `context` (string): Optional context for the request - echoed back in response ### `blockchain_fees__blockchain_fees_utxo` (~312 tokens) Get fee recommendations for UTXO blockchains (bitcoin, bitcoin-cash, litecoin, dogecoin, dash, zcash). Use this before preparing or signing a transaction to determine the appropriate fee rate. Actions: • get-fee-recommendations: Get recommended fee-per-byte tiers (slow/standard/fast) from the mempool • estimate-transaction-smart-fee: Estimate the fee rate needed for confirmation within a target number of blocks Credits by action (source: OpenAPI): • estimate-transaction-smart-fee: bitcoin 510, bitcoin-cash 612, dash 561, dogecoin 561, litecoin 561, zcash 663 • get-fee-recommendations: bitcoin 510, bitcoin-cash 612, dash 561, dogecoin 561, litecoin 561, zcash 663 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `action` (string, required): Action to perform - `blockchain` (string, required): Blockchain protocol - `confirmationTarget` (integer): Target number of blocks for confirmation (estimate-transaction-smart-fee only) - `context` (string): Optional context for the request - echoed back in response - `feeRatePriority` (string): Fee rate priority: ECONOMICAL or CONSERVATIVE (estimate-transaction-smart-fee only) - `network` (string, required): Network name ### `blockchain_fees__blockchain_fees_evm` (~664 tokens) Get fee recommendations and estimate gas costs for EVM blockchains. Use this before preparing or signing a transaction to determine appropriate gas parameters. Actions: • get-fee-recommendations: Get recommended gas price tiers (slow/standard/fast) • get-eip-1559-fee-recommendations: Get EIP-1559 fee parameters (baseFee, maxPriorityFee) for supported chains • estimate-native-coin-transfer-gas: Estimate gas for a native coin transfer (e.g. ETH, BNB) • estimate-token-transfer-gas: Estimate gas for an ERC-20/ERC-721 token transfer • estimate-contract-interaction-gas: Estimate gas for a smart contract call Credits by action (source: OpenAPI): • estimate-contract-interaction-gas: arbitrum 192, avalanche 216, base 144, binance-smart-chain 300, ethereum 120, ethereum-classic 156, optimism 168, polygon 240, tron 180 • estimate-native-coin-transfer-gas: arbitrum 192, avalanche 216, base 144, binance-smart-chain 300, ethereum 120, ethereum-classic 156, optimism 168, polygon 240, tron 180 • estimate-token-transfer-gas: arbitrum 192, avalanche 216, base 144, binance-smart-chain 300, ethereum 120, ethereum-classic 156, optimism 168, polygon 240, tron 180 • get-eip-1559-fee-recommendations: arbitrum 48, avalanche 54, base 36, binance-smart-chain 75, ethereum 30, ethereum-classic 39, optimism 42, polygon 60, tron 45 • get-fee-recommendations: arbitrum 48, avalanche 54, base 36, binance-smart-chain 75, ethereum 30, ethereum-classic 39, optimism 42, polygon 60, tron 45 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `action` (string, required): Action to perform - `amount` (string): Token amount to transfer (required for estimate-token-transfer-gas) - `blockchain` (string, required): Blockchain protocol - `context` (string): Optional context for the request - echoed back in response - `contractAddress` (string): Token contract address (required for estimate-token-transfer-gas and estimate-contract-interaction-gas) - `contractType` (string): Token standard: ERC-20 or ERC-721 (estimate-token-transfer-gas only; defaults to ERC-20) - `data` (string): Hex-encoded calldata (required for estimate-contract-interaction-gas) - `fromAddress` (string): Sender address (required for gas estimation actions) - `network` (string, required): Network name - `toAddress` (string): Recipient address (required for native coin and token transfer gas estimation) - `value` (string): Amount in native coin's smallest unit, e.g. wei (required for estimate-native-coin-transfer-gas; optional for estimate-contract-interaction-gas) ### `blockchain_fees__blockchain_fees_xrp` (~91 tokens) Blockchain Fees XRP: get fee recommendations. Networks: mainnet, testnet. Credits per call: 20 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `context` (string): Optional context for the request - echoed back in response - `network` (string, required): Network name ### `blockchain_fees__blockchain_fees_tezos` (~392 tokens) Blockchain Fees Tezos: fee recommendations and fee estimation for XTZ, FA1.2, and FA2 transfers. Actions: • get-fee-recommendations: Get current minimal fee/cost rates from the mempool • estimate-transfer: Estimate the fee for a native XTZ transfer • estimate-fa12-transfer: Estimate the fee for an FA1.2 token transfer • estimate-fa2-transfer: Estimate the fee for an FA2 token transfer Credits by action (source: OpenAPI): • estimate-fa12-transfer: 52 • estimate-fa2-transfer: 52 • estimate-transfer: 52 • get-fee-recommendations: 52 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `action` (string, required): Action to perform - `amount` (string): Amount in mutez (transfer) or token base units (fa12/fa2) as an integer string - required for all estimate actions - `context` (string): Optional context for the request - echoed back in response - `contractAddress` (string): FA1.2/FA2 token contract address - required for estimate-fa12-transfer, estimate-fa2-transfer - `network` (string, required): Network name - `recipient` (string): Recipient address - required for estimate-transfer, estimate-fa12-transfer, estimate-fa2-transfer - `sender` (string): Sender address - required for estimate-transfer, estimate-fa12-transfer, estimate-fa2-transfer - `senderPublicKey` (string): Sender's public key - required only when the source account is unrevealed (all estimate actions) - `tokenId` (string): FA2 token ID as an integer STRING (e.g. "0") - estimate-fa2-transfer only; the API rejects a number ### `blockchain_fees__blockchain_fees_solana` (~471 tokens) Blockchain Fees Solana: fee recommendations and compute-unit estimation. Solana uses compute units (not gas), so this is a distinct cost model from EVM. Actions: • get-fee-recommendations: Get current priority fee recommendations from the mempool • estimate-native-coin-transfer-compute-units: Estimate compute units for a native SOL transfer • estimate-token-transfer-compute-units: Estimate compute units for an SPL token transfer • estimate-program-invocation-compute-units: Estimate compute units for an arbitrary program instruction call Credits by action (source: OpenAPI): • estimate-native-coin-transfer-compute-units: 120 • estimate-program-invocation-compute-units: 120 • estimate-token-transfer-compute-units: 120 • get-fee-recommendations: 90 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `accounts` (array): Accounts referenced by the instruction, in the order the program expects them (estimate-program-invocation-compute-units only; may be empty) - `action` (string, required): Action to perform - `amount` (string): Amount in lamports (native) or token base units (token) - required for estimate-native-coin-transfer-compute-units, estimate-token-transfer-compute-units - `context` (string): Optional context for the request - echoed back in response - `contractAddress` (string): SPL token mint address - required for estimate-token-transfer-compute-units - `instructionData` (string): Base58/base64-encoded instruction data for the program call - required for estimate-program-invocation-compute-units - `network` (string, required): Network name - `programId` (string): On-chain program address to invoke - required for estimate-program-invocation-compute-units - `recipient` (string): Recipient address - required for estimate-native-coin-transfer-compute-units, estimate-token-transfer-compute-units - `sender` (string): Sender address - required for all estimate actions - `tokenStandard` (string): SPL token program standard - required for estimate-token-transfer-compute-units ### `blockchain_fees__system_info` (~175 tokens) CryptoAPIs reference documentation — no API call, no credits consumed. Actions: • blockchains — Supported blockchains, networks, products per chain, denominations, fiat currencies • errors — Complete error code table (HTTP status, error code, message) • credits — Credit charging structure, cost multipliers per blockchain, monitoring & operations taxes (xPub, synced addresses, blockchain events), pay-as-you-go • callbacks — Webhook mechanics: URL requirements, retry strategy (5 retries, exponential backoff), HMAC security, idempotency • limits — Throughput soft/hard limits per plan, 2.1x penalty multiplier, rate limiting behavior Input parameters: - `action` (string, required): Reference topic to retrieve - `context` (string): Optional context for the request - echoed back in response ### `broadcast__broadcast_signed_transaction` (~301 tokens) Broadcast locally signed transaction (Broadcast product). Submit a signed transaction hex to the network. Supported blockchains and networks vary; see credits for per-chain cost. Note: 'broadcast-signed-transaction' actions require confirmation. They return a preview with a one-time token instead of executing immediately. Credits by action (source: OpenAPI): • broadcast-signed-transaction: arbitrum 80, avalanche 90, base 60, binance-smart-chain 125, bitcoin 50, bitcoin-cash 60, dash 55, dogecoin 55, ethereum 50, ethereum-classic 65, litecoin 55, optimism 70, polygon 100, solana 150, tezos 65, tron 75, xrp 50, zcash 65 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `blockchain` (string, required): Blockchain protocol - `confirmationToken` (string): Confirmation token from a previous preview response. IMPORTANT: You MUST present the warning and impact to the user and receive their explicit approval before passing this token. NEVER auto-confirm —… - `context` (string): Optional context for the request - echoed back in response - `network` (string, required): Network name - `signedTransactionHex` (string, required): Signed transaction hex to broadcast ### `broadcast__system_info` (~173 tokens) CryptoAPIs reference documentation — no API call, no credits consumed. Actions: • blockchains — Supported blockchains, networks, products per chain, denominations, fiat currencies • errors — Complete error code table (HTTP status, error code, message) • credits — Credit charging structure, cost multipliers per blockchain, monitoring & operations taxes (xPub, synced addresses, blockchain events), pay-as-you-go • callbacks — Webhook mechanics: URL requirements, retry strategy (5 retries, exponential backoff), HMAC security, idempotency • limits — Throughput soft/hard limits per plan, 2.1x penalty multiplier, rate limiting behavior Input parameters: - `action` (string, required): Reference topic to retrieve - `context` (string): Optional context for the request - echoed back in response ### `contracts__evm_contract_data` (~206 tokens) Get EVM contract token details (Contracts product). Actions: • get-token-details-by-contract-address: Get token details (name, symbol, standard, decimals, totalSupply) by contract address Blockchain → Networks: • ethereum: mainnet, sepolia • ethereum-classic: mainnet, mordor • binance-smart-chain: mainnet, testnet Credits by action (source: OpenAPI): • get-token-details-by-contract-address: binance-smart-chain 75, ethereum 30, ethereum-classic 39 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `action` (string, required): Action to perform - `blockchain` (string, required): Blockchain protocol - `context` (string): Optional context for the request - echoed back in response - `contractAddress` (string, required): Contract address (token contract) - `network` (string, required): Network name ### `contracts__solana_contract_data` (~148 tokens) Get Solana contract token details (Contracts product). Actions: • get-token-details-by-contract-address: Get token details by contract address Networks: mainnet, devnet Credits by action (source: OpenAPI): • get-token-details-by-contract-address: 75 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `action` (string, required): Action to perform - `context` (string): Optional context for the request - echoed back in response - `contractAddress` (string, required): Contract address (token contract) - `network` (string, required): Network name: mainnet or devnet ### `contracts__system_info` (~173 tokens) CryptoAPIs reference documentation — no API call, no credits consumed. Actions: • blockchains — Supported blockchains, networks, products per chain, denominations, fiat currencies • errors — Complete error code table (HTTP status, error code, message) • credits — Credit charging structure, cost multipliers per blockchain, monitoring & operations taxes (xPub, synced addresses, blockchain events), pay-as-you-go • callbacks — Webhook mechanics: URL requirements, retry strategy (5 retries, exponential backoff), HMAC security, idempotency • limits — Throughput soft/hard limits per plan, 2.1x penalty multiplier, rate limiting behavior Input parameters: - `action` (string, required): Reference topic to retrieve - `context` (string): Optional context for the request - echoed back in response ### `hd_wallet__manage_hd_wallet` (~404 tokens) Manage HD wallets identified by extended public key (xPub/yPub/zPub). Private keys never leave the user's device — only the extended public key is sent to CryptoAPIs for address derivation and balance tracking. Actions: • sync-wallet: Register an xPub to start syncing its addresses and balances • list-wallets: List all synced HD wallets for a blockchain/network • activate-wallet: Re-activate a previously deleted wallet • delete-wallet: Remove an xPub from tracking (can be re-activated later) • get-status: Check the sync status of a wallet (syncing, synced, etc.) Note: 'sync-wallet', 'activate-wallet', 'delete-wallet' actions require confirmation. They return a preview with a one-time token instead of executing immediately. Credits by action (source: OpenAPI): • activate-wallet: 12 • delete-wallet: 12 • get-status: 10 • list-wallets: 12 • sync-wallet: 36 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `action` (string, required): Action to perform - `blockchain` (string): Blockchain; required for all actions - `confirmationToken` (string): Confirmation token from a previous preview response. IMPORTANT: You MUST present the warning and impact to the user and receive their explicit approval before passing this token. NEVER auto-confirm —… - `context` (string): Optional context for the request - echoed back in response - `extendedPublicKey` (string): xPub/yPub/zPub; required for sync, activate, delete, get-status - `limit` (number): Max results per page (list-wallets only) - `network` (string): Network; required for all actions - `offset` (number): Pagination offset (list-wallets only) ### `hd_wallet__hd_wallet_data_utxo` (~518 tokens) Query HD wallet data for UTXO blockchains (bitcoin, litecoin, bitcoin-cash, dogecoin, dash, zcash) by extended public key (xPub/yPub/zPub). The wallet must first be synced via manage_hd_wallet. Offset pagination: use 'limit' and 'offset' for paged results. Actions: • derive-receiving-address: Derive the next unused receiving address • derive-change-address: Derive the next unused change address • list-addresses: List all derived addresses for the wallet • list-transactions: List transactions across all wallet addresses • list-utxos: List unspent transaction outputs (UTXOs) for the wallet • prepare-transaction: Build an unsigned UTXO transaction with automatic input selection • list-assets: List token/asset balances held by the wallet • get-details: Get wallet summary (total balance, address count, sync status) Credits by action (source: OpenAPI): • derive-change-address: 24 • derive-receiving-address: 24 • get-details: 12 • list-addresses: 12 • list-assets: 12 • list-transactions: 120 • list-utxos: 120 • prepare-transaction: 24 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `action` (string, required): Action to perform - `addressFormat` (string): UTXO list-addresses: address format - `blockchain` (string): UTXO blockchain (e.g. bitcoin, litecoin, bitcoin-cash, dogecoin, dash, zcash); required for all actions - `context` (string): Optional context for the request - echoed back in response - `derivation` (string): UTXO list-utxos / list-transactions: derivation type - `extendedPublicKey` (string): xPub/yPub/zPub for this chain - `feePriority` (string): Fee priority level (prepare-transaction only; defaults to standard) - `limit` (number): Max results per page (for list-* actions) - `network` (string): Network (e.g. mainnet, testnet); required for all actions - `offset` (number): Pagination offset (for list-* actions) - `recipients` (array): Array of {address, amount} objects (required for prepare-transaction) ### `hd_wallet__hd_wallet_data_evm` (~461 tokens) Query HD wallet data for EVM blockchains by extended public key (xPub). The wallet must first be synced via manage_hd_wallet. Offset pagination: use 'limit' and 'offset' for paged results. Actions: • derive-receiving-address: Derive the next unused receiving address • list-addresses: List all derived addresses for the wallet • list-transactions: List transactions across all wallet addresses • prepare-transaction: Build an unsigned EVM transaction from a wallet address • list-assets: List token balances (ERC-20, ERC-721, etc.) held by the wallet • get-details: Get wallet summary (total balance, address count, sync status) Credits by action (source: OpenAPI): • derive-receiving-address: 24 • get-details: 12 • list-addresses: 12 • list-assets: 12 • list-transactions: 120 • prepare-transaction: 24 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `action` (string, required): Action to perform - `blockchain` (string): EVM blockchain (e.g. ethereum, binance-smart-chain, polygon); required for all actions - `context` (string): Optional context for the request - echoed back in response - `data` (string): Hex-encoded calldata for contract interaction (prepare-transaction only) - `extendedPublicKey` (string): xPub/yPub/zPub for this chain - `feePriority` (string): Fee priority level (prepare-transaction only; defaults to standard) - `fromAddress` (string): Sender address (required for prepare-transaction) - `limit` (number): Max results per page (for list-* actions) - `network` (string): Network (e.g. mainnet, sepolia); required for all actions - `offset` (number): Pagination offset (for list-* actions) - `toAddress` (string): Recipient address (required for prepare-transaction) - `value` (string): Amount in the native coin's smallest unit, e.g. wei (required for prepare-transaction) ### `hd_wallet__hd_wallet_data_xrp` (~344 tokens) Query HD wallet data for XRP (Ripple) by extended public key (xPub). The wallet must first be synced via manage_hd_wallet. Offset pagination: use 'limit' and 'offset' for paged results. Actions: • derive-receiving-address: Derive the next unused receiving address • list-addresses: List all derived addresses for the wallet • list-transactions: List transactions across all wallet addresses • list-assets: List token/asset balances held by the wallet • get-details: Get wallet summary (total balance, address count, sync status) Credits by action (source: OpenAPI): • derive-receiving-address: 24 • get-details: 12 • list-addresses: 12 • list-assets: 12 • list-transactions: 90 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `action` (string, required): Action to perform - `addressFormat` (string): XRP list-addresses: address format - `context` (string): Optional context for the request - echoed back in response - `derivation` (string): XRP list-transactions: derivation type - `extendedPublicKey` (string): xPub for XRP - `isChangeAddress` (boolean): XRP list-addresses: filter change addresses - `limit` (number): Max results per page (for list-* actions) - `network` (string): XRP network (mainnet or testnet); required for all actions - `offset` (number): Pagination offset (for list-* actions) ### `hd_wallet__system_info` (~174 tokens) CryptoAPIs reference documentation — no API call, no credits consumed. Actions: • blockchains — Supported blockchains, networks, products per chain, denominations, fiat currencies • errors — Complete error code table (HTTP status, error code, message) • credits — Credit charging structure, cost multipliers per blockchain, monitoring & operations taxes (xPub, synced addresses, blockchain events), pay-as-you-go • callbacks — Webhook mechanics: URL requirements, retry strategy (5 retries, exponential backoff), HMAC security, idempotency • limits — Throughput soft/hard limits per plan, 2.1x penalty multiplier, rate limiting behavior Input parameters: - `action` (string, required): Reference topic to retrieve - `context` (string): Optional context for the request - echoed back in response ### `market_data__market_data_metadata` (~149 tokens) Market Data metadata (list supported assets). Actions: • list-supported-assets: List supported crypto and fiat assets (optional pagination and type filter) Credits by action (source: OpenAPI): • list-supported-assets: 10 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `action` (string, required): Action to perform - `context` (string): Optional context for the request - echoed back in response - `limit` (integer): Number of items to return (max 50) - `offset` (integer): Pagination offset - `type` (string): Asset type filter (crypto or fiat) ### `market_data__market_data_exchange_rates` (~262 tokens) Market Data exchange rates. Actions: • get-exchange-rate-by-asset-symbols: Get exchange rate between two assets by symbol (e.g. BTC, USD) • get-exchange-rate-by-asset-ids: Get exchange rate between two assets by asset ID Credits by action (source: OpenAPI): • get-exchange-rate-by-asset-ids: 10 • get-exchange-rate-by-asset-symbols: 10 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `action` (string, required): Action to perform - `context` (string): Optional context for the request - echoed back in response - `fromAssetId` (string): From asset ID - for get-exchange-rate-by-asset-ids - `fromAssetSymbol` (string): From asset symbol (e.g. BTC) - for get-exchange-rate-by-asset-symbols - `toAssetId` (string): To asset ID - for get-exchange-rate-by-asset-ids - `toAssetSymbol` (string): To asset symbol (e.g. USD) - for get-exchange-rate-by-asset-symbols ### `market_data__market_data_assets` (~196 tokens) Market Data assets (asset details). Actions: • get-asset-details-by-asset-id: Get asset details by unique asset ID • get-asset-details-by-asset-symbol: Get asset details by symbol (e.g. BTC, ETH) Credits by action (source: OpenAPI): • get-asset-details-by-asset-id: 10 • get-asset-details-by-asset-symbol: 10 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `action` (string, required): Action to perform - `assetId` (string): Asset ID - for get-asset-details-by-asset-id - `assetSymbol` (string): Asset symbol (e.g. BTC) - for get-asset-details-by-asset-symbol - `context` (string): Optional context for the request - echoed back in response ### `market_data__system_info` (~174 tokens) CryptoAPIs reference documentation — no API call, no credits consumed. Actions: • blockchains — Supported blockchains, networks, products per chain, denominations, fiat currencies • errors — Complete error code table (HTTP status, error code, message) • credits — Credit charging structure, cost multipliers per blockchain, monitoring & operations taxes (xPub, synced addresses, blockchain events), pay-as-you-go • callbacks — Webhook mechanics: URL requirements, retry strategy (5 retries, exponential backoff), HMAC security, idempotency • limits — Throughput soft/hard limits per plan, 2.1x penalty multiplier, rate limiting behavior Input parameters: - `action` (string, required): Reference topic to retrieve - `context` (string): Optional context for the request - echoed back in response ### `prepare_transactions__prepare_transactions_evm` (~395 tokens) Build unsigned EVM transactions ready for signing. Returns the raw unsigned transaction hex and fee details. After preparing, use a signing tool (e.g. evm_sign) to sign locally, then broadcast via broadcast_signed_transaction. Actions: • prepare-transaction-from-address: Build an unsigned native coin transfer (e.g. ETH, BNB) • prepare-fungible-token-transfer: Build an unsigned ERC-20 token transfer • prepare-nft-transfer: Build an unsigned ERC-721 NFT transfer Credits by action (source: OpenAPI): • prepare-fungible-token-transfer: 24 • prepare-nft-transfer: 24 • prepare-transaction-from-address: 24 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `action` (string, required): Action to perform - `amount` (string): Token amount to transfer (required for prepare-fungible-token-transfer) - `blockchain` (string, required): Blockchain protocol - `context` (string): Optional context for the request - echoed back in response - `contractAddress` (string): Token contract address (required for prepare-fungible-token-transfer and prepare-nft-transfer) - `fromAddress` (string): Sender address (required for all actions) - `gasLimit` (string): Custom gas limit override (prepare-transaction-from-address only; auto-estimated if omitted) - `gasPrice` (string): Custom gas price in wei (prepare-transaction-from-address only; auto-estimated if omitted) - `network` (string, required): Network name - `toAddress` (string): Recipient address (required for all actions) - `tokenId` (string): NFT token ID (required for prepare-nft-transfer) - `value` (string): Amount in native coin's smallest unit, e.g. wei (required for prepare-transaction-from-address) ### `prepare_transactions__prepare_transactions_tezos` (~366 tokens) Build unsigned Tezos operations ready for signing. Returns the forged (unsigned) operation bytes and fee details. After preparing, sign locally and broadcast via broadcast_signed_transaction. Actions: • native-coins: Build an unsigned native XTZ transfer • fa1-2-tokens: Build an unsigned FA1.2 token transfer • fa2-tokens: Build an unsigned FA2 token transfer Credits by action (source: OpenAPI): • fa1-2-tokens: 104 • fa2-tokens: 104 • native-coins: 78 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `action` (string, required): Action to perform - `amount` (string): Amount to send, in mutez for native-coins, or in the token's base units for fa1-2-tokens/fa2-tokens (required for all actions) - `context` (string): Optional context for the request - echoed back in response - `contractAddress` (string): FA1.2/FA2 token contract address (KT1...) - required for fa1-2-tokens, fa2-tokens - `feePriority` (string): Fee priority tier - defaults to standard if omitted - `fromAddress` (string): Sender's Tezos address (required for all actions) - `fromPublicKey` (string): Sender's public key - required only when the source account is unrevealed - `network` (string, required): Network name - `toAddress` (string): Recipient's Tezos address (required for all actions) - `tokenId` (string): FA2 token ID - required for fa2-tokens ### `prepare_transactions__prepare_transactions_solana` (~266 tokens) Build unsigned Solana transactions ready for signing. Returns the unsigned transaction and fee details. After preparing, sign locally and broadcast via broadcast_signed_transaction. Actions: • native-coins: Build an unsigned native SOL transfer • spl-tokens: Build an unsigned SPL token transfer Credits by action (source: OpenAPI): • native-coins: 180 • spl-tokens: 240 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `action` (string, required): Action to perform - `amount` (string): Amount in lamports for native-coins, or token base units for spl-tokens (required for all actions) - `context` (string): Optional context for the request - echoed back in response - `feePriority` (string): Fee priority tier - defaults to standard if omitted - `fromAddress` (string): Sender address (required for all actions) - `network` (string, required): Network name - `toAddress` (string): Recipient address (required for all actions) - `tokenContract` (string): SPL token mint address (required for spl-tokens) - `tokenStandard` (string): SPL token program standard (spl-tokens only) ### `prepare_transactions__prepare_transactions_kaspa` (~273 tokens) Build unsigned Kaspa transactions ready for signing. Returns the unsigned transaction and fee details. After preparing, sign locally (kaspa_sign) and broadcast via broadcast_signed_transaction. Actions: • native-coins: Build an unsigned native KAS transfer, supporting multiple recipients in one transaction Credits by action (source: OpenAPI): • native-coins: 60 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `action` (string, required): Action to perform - `context` (string): Optional context for the request - echoed back in response - `exactFee` (string): Exact fee override in KAS - bypasses mass-based fee calculation when set - `feePriority` (string): Fee priority tier - defaults to standard if omitted - `fromAddress` (string): Sender's Kaspa address (required) - `locktime` (integer): Transaction locktime - `network` (string, required): Network name - Kaspa is mainnet-only - `prepareStrategy` (string): UTXO selection strategy - `recipients` (array): Recipients as {address, amount} objects, amount in KAS main units - one output per entry, multiple recipients supported in a single transaction (required) ### `prepare_transactions__prepare_transactions_xrp` (~230 tokens) Build unsigned XRP transactions ready for signing. Returns the unsigned transaction and fee details. After preparing, sign locally (xrp_sign) and broadcast via broadcast_signed_transaction. Actions: • native-coins: Build an unsigned native XRP transfer Credits by action (source: OpenAPI): • native-coins: 60 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `action` (string, required): Action to perform - `amount` (string): Amount in drops (required) - `context` (string): Optional context for the request - echoed back in response - `destinationTag` (string): Destination tag - commonly required when sending to an exchange address - `feePriority` (string): Fee priority tier - defaults to standard if omitted - `fromAddress` (string): Sender's XRP address (required) - `network` (string, required): Network name - `sequence` (string): Override the account sequence number (advanced use) - `toAddress` (string): Recipient's XRP address (required) ### `prepare_transactions__prepare_transactions_utxo` (~323 tokens) Build unsigned UTXO transactions ready for signing (Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash). Returns the unsigned transaction and fee details. After preparing, sign locally (utxo_sign) and broadcast via broadcast_signed_transaction. Actions: • native-coins: Build an unsigned native coin transfer, supporting multiple recipients in one transaction. Requires either feePriority or exactFee. Credits by action (source: OpenAPI): • native-coins: 530 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `action` (string, required): Action to perform - `additionalData` (string): OP_RETURN data to embed in the transaction - `blockchain` (string, required): Blockchain protocol - `context` (string): Optional context for the request - echoed back in response - `exactFee` (string): Exact fee override in the chain's main denomination - required unless feePriority is given - `feePriority` (string): Fee priority tier - required unless exactFee is given - `fromAddress` (string): Sender's address (required) - `locktime` (integer): Transaction locktime - `network` (string, required): Network name - `prepareStrategy` (string): UTXO selection strategy - `recipients` (array): Recipients as {address, amount} objects, amount in the chain's main denomination - one output per entry (required) - `replaceable` (boolean): Mark the transaction as RBF-replaceable ### `prepare_transactions__prepare_transactions_tron` (~365 tokens) Build unsigned Tron transactions ready for signing. Returns the unsigned transaction and fee details. After preparing, sign locally (tron_sign) and broadcast via broadcast_signed_transaction. These are Tron's dedicated prepare-transactions endpoints, distinct from the generic EVM ones used for other chains. Actions: • native-coins: Build an unsigned native TRX transfer • trc20-tokens: Build an unsigned TRC-20 token transfer • non-fungible-tokens: Build an unsigned TRC-721/TRC-1155 NFT transfer Credits by action (source: OpenAPI): • native-coins: 90 • non-fungible-tokens: 128 • trc20-tokens: 120 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `action` (string, required): Action to perform - `amount` (string): Amount in sun for native-coins, or token base units for trc20-tokens (required for native-coins, trc20-tokens) - `context` (string): Optional context for the request - echoed back in response - `contract` (string): Token contract address (required for trc20-tokens, non-fungible-tokens) - `feeLimit` (integer): Max TRX fee limit in sun (trc20-tokens, non-fungible-tokens only) - `network` (string, required): Network name - `recipient` (string): Recipient's Tron address (required for all actions) - `sender` (string): Sender's Tron address (required for all actions) - `tokenId` (string): NFT token ID (required for non-fungible-tokens) ### `prepare_transactions__system_info` (~174 tokens) CryptoAPIs reference documentation — no API call, no credits consumed. Actions: • blockchains — Supported blockchains, networks, products per chain, denominations, fiat currencies • errors — Complete error code table (HTTP status, error code, message) • credits — Credit charging structure, cost multipliers per blockchain, monitoring & operations taxes (xPub, synced addresses, blockchain events), pay-as-you-go • callbacks — Webhook mechanics: URL requirements, retry strategy (5 retries, exponential backoff), HMAC security, idempotency • limits — Throughput soft/hard limits per plan, 2.1x penalty multiplier, rate limiting behavior Input parameters: - `action` (string, required): Reference topic to retrieve - `context` (string): Optional context for the request - echoed back in response ### `simulate__simulate_evm` (~255 tokens) Dry-run an Ethereum transaction without broadcasting it to the network (mainnet or sepolia only — this endpoint does not support other EVM chains). Returns estimated gas usage, execution success/failure, and any revert reason. Use this to validate transactions before signing and broadcasting — helpful for catching errors, estimating costs, and debugging contract interactions. Credits per call: 48 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `context` (string): Optional context for the request - echoed back in response - `data` (string): Hex-encoded calldata for contract interaction or deployment bytecode - `fromAddress` (string, required): Sender address - `gasLimit` (string): Custom gas limit override (auto-estimated if omitted) - `gasPrice` (string): Custom gas price in wei (auto-estimated if omitted) - `network` (string, required): Network name (Ethereum only — mainnet or sepolia) - `toAddress` (string): Recipient or contract address (omit for contract deployment simulation) - `value` (string): Amount in native coin's smallest unit, e.g. wei (defaults to '0') ### `simulate__system_info` (~173 tokens) CryptoAPIs reference documentation — no API call, no credits consumed. Actions: • blockchains — Supported blockchains, networks, products per chain, denominations, fiat currencies • errors — Complete error code table (HTTP status, error code, message) • credits — Credit charging structure, cost multipliers per blockchain, monitoring & operations taxes (xPub, synced addresses, blockchain events), pay-as-you-go • callbacks — Webhook mechanics: URL requirements, retry strategy (5 retries, exponential backoff), HMAC security, idempotency • limits — Throughput soft/hard limits per plan, 2.1x penalty multiplier, rate limiting behavior Input parameters: - `action` (string, required): Reference topic to retrieve - `context` (string): Optional context for the request - echoed back in response ### `transactions_data__transactions_data_utxo` (~233 tokens) Transactions Data UTXO: get transaction details or raw transaction data by hash. Actions: get-transaction-details, get-raw-transaction-data. Blockchains: bitcoin, bitcoin-cash, litecoin, dogecoin, dash, zcash. Networks: mainnet, testnet. Credits by action (source: OpenAPI): • get-raw-transaction-data: bitcoin 110, bitcoin-cash 132, dash 121, dogecoin 121, litecoin 121, zcash 143 • get-transaction-details: bitcoin 110, bitcoin-cash 132, dash 121, dogecoin 121, litecoin 121, zcash 143 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `action` (string, required): Action to perform - `blockchain` (string, required): Blockchain protocol - `context` (string): Optional context for the request - echoed back in response - `network` (string, required): Network name - `transactionHash` (string, required): Transaction hash ### `transactions_data__transactions_data_evm` (~338 tokens) Transactions Data EVM: get transaction details, internal transactions, token transfers, or logs by transaction hash. Actions: get-transaction-details, list-internal-transactions, list-token-transfers, list-logs. Credits by action (source: OpenAPI): • get-transaction-details: arbitrum 192, avalanche 216, base 144, binance-smart-chain 300, ethereum 120, ethereum-classic 156, optimism 168, polygon 240, tron 180 • list-internal-transactions: arbitrum 512, avalanche 576, base 384, binance-smart-chain 800, ethereum 320, ethereum-classic 416, optimism 448, polygon 640, tron 480 • list-logs: arbitrum 192, avalanche 216, base 144, binance-smart-chain 300, ethereum 120, ethereum-classic 156, optimism 168, polygon 240, tron 180 • list-token-transfers: arbitrum 352, avalanche 396, base 264, binance-smart-chain 550, ethereum 220, ethereum-classic 286, optimism 308, polygon 440, tron 330 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `action` (string, required): Action to perform - `blockchain` (string, required): Blockchain protocol - `context` (string): Optional context for the request - echoed back in response - `network` (string, required): Network name - `transactionHash` (string, required): Transaction hash ### `transactions_data__transactions_data_solana` (~106 tokens) Transactions Data Solana: get transaction details by transaction hash (signature). Networks: mainnet, devnet. Credits per call: 90 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `context` (string): Optional context for the request - echoed back in response - `network` (string, required): Network name - `transactionHash` (string, required): Transaction hash (signature) ### `transactions_data__transactions_data_xrp` (~101 tokens) Transactions Data XRP: get transaction details by transaction hash. Networks: mainnet, testnet. Credits per call: 110 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `context` (string): Optional context for the request - echoed back in response - `network` (string, required): Network name - `transactionHash` (string, required): Transaction hash ### `transactions_data__transactions_data_kaspa` (~100 tokens) Transactions Data Kaspa: get transaction details by transaction ID. Network: mainnet. Credits per call: 918 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `context` (string): Optional context for the request - echoed back in response - `network` (string, required): Network name - `transactionId` (string, required): Transaction ID ### `transactions_data__system_info` (~174 tokens) CryptoAPIs reference documentation — no API call, no credits consumed. Actions: • blockchains — Supported blockchains, networks, products per chain, denominations, fiat currencies • errors — Complete error code table (HTTP status, error code, message) • credits — Credit charging structure, cost multipliers per blockchain, monitoring & operations taxes (xPub, synced addresses, blockchain events), pay-as-you-go • callbacks — Webhook mechanics: URL requirements, retry strategy (5 retries, exponential backoff), HMAC security, idempotency • limits — Throughput soft/hard limits per plan, 2.1x penalty multiplier, rate limiting behavior Input parameters: - `action` (string, required): Reference topic to retrieve - `context` (string): Optional context for the request - echoed back in response ### `utils__utxo_utils` (~369 tokens) UTXO utils (Utils product): validate address, decode raw transaction hex, convert Bitcoin Cash address. Actions: • validate-address: Check if a UTXO address is valid • decode-raw-transaction: Decode a raw transaction hex • convert-bitcoin-cash-address: Convert Bitcoin Cash address (legacy ↔ cash format); Bitcoin Cash only, no blockchain parameter (network + address) Blockchain → Networks: • bitcoin: mainnet, testnet • bitcoin-cash: mainnet, testnet • litecoin: mainnet, testnet • dogecoin: mainnet, testnet • dash: mainnet, testnet • zcash: mainnet, testnet Credits by action (source: OpenAPI): • convert-bitcoin-cash-address: bitcoin-cash 12 • decode-raw-transaction: bitcoin 10, bitcoin-cash 12, dash 11, dogecoin 11, litecoin 11, zcash 13 • validate-address: bitcoin 10, bitcoin-cash 12, dash 11, dogecoin 11, litecoin 11, zcash 13 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `action` (string, required): Action to perform - `address` (string): Address (required for validate-address and convert-bitcoin-cash-address) - `blockchain` (string): Blockchain protocol (required for validate-address and decode-raw-transaction) - `context` (string): Optional context for the request - echoed back in response - `network` (string, required): Network name - `rawTransactionHex` (string): Raw transaction hex (required for decode-raw-transaction) ### `utils__evm_utils` (~265 tokens) EVM utils (Utils product): validate address, decode raw transaction hex. Actions: • validate-address: Check if an EVM address is valid • decode-raw-transaction: Decode a raw transaction hex Blockchain → Networks: • ethereum: mainnet, sepolia • ethereum-classic: mainnet, mordor • binance-smart-chain: mainnet, testnet • tron: mainnet, nile Credits by action (source: OpenAPI): • decode-raw-transaction: binance-smart-chain 25, ethereum 10, ethereum-classic 13, tron 15 • validate-address: binance-smart-chain 25, ethereum 10, ethereum-classic 13, tron 15 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `action` (string, required): Action to perform - `address` (string): Address (required for validate-address) - `blockchain` (string, required): Blockchain protocol - `context` (string): Optional context for the request - echoed back in response - `network` (string, required): Network name - `rawTransactionHex` (string): Raw transaction hex (required for decode-raw-transaction) ### `utils__xrp_utils` (~241 tokens) XRP utils (Utils product): validate address, decode/encode X-Address. Actions: • validate-address: Check if an XRP address is valid • decode-x-address: Decode X-Address to classic address and tag • encode-x-address: Encode classic address and tag to X-Address Networks: mainnet, testnet Credits by action (source: OpenAPI): • decode-x-address: 10 • encode-x-address: 10 • validate-address: 10 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `action` (string, required): Action to perform - `address` (string): Address (required for validate-address) - `addressTag` (integer): Destination tag (required for encode-x-address) - `classicAddress` (string): Classic address (required for encode-x-address) - `context` (string): Optional context for the request - echoed back in response - `network` (string, required): Network name: mainnet or testnet - `xAddress` (string): X-Address (required for decode-x-address) ### `utils__derive_addresses` (~309 tokens) Utils: derive HD wallet (xPub, yPub, zPub) change or receiving addresses without syncing. GET /utils/{blockchain}/{network}/xpubs/{extendedPublicKey}/derive-addresses Derives up to 10 addresses. By default creates receiving/deposit address; set isChange=true for change address (UTXO only). Credits by action (source: OpenAPI): • binance-smart-chain: 25 • bitcoin: 10 • bitcoin-cash: 12 • dash: 11 • dogecoin: 11 • ethereum: 10 • ethereum-classic: 13 • litecoin: 11 • tron: 15 • xrp: 10 • zcash: 13 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. Input parameters: - `addressFormat` (string): Address format - `addressesCount` (integer): Number of addresses to derive (up to 10) - `blockchain` (string, required): Blockchain protocol - `context` (string): Optional context for the request - echoed back in response - `extendedPublicKey` (string, required): xPub/yPub/zPub for the HD wallet - `isChange` (boolean): If true derive change address(es); if false derive receiving/deposit - `network` (string, required): Network name - `startIndex` (integer): Starting index for derivation ### `utils__system_info` (~173 tokens) CryptoAPIs reference documentation — no API call, no credits consumed. Actions: • blockchains — Supported blockchains, networks, products per chain, denominations, fiat currencies • errors — Complete error code table (HTTP status, error code, message) • credits — Credit charging structure, cost multipliers per blockchain, monitoring & operations taxes (xPub, synced addresses, blockchain events), pay-as-you-go • callbacks — Webhook mechanics: URL requirements, retry strategy (5 retries, exponential backoff), HMAC security, idempotency • limits — Throughput soft/hard limits per plan, 2.1x penalty multiplier, rate limiting behavior Input parameters: - `action` (string, required): Reference topic to retrieve - `context` (string): Optional context for the request - echoed back in response ## Diagnostics Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/cryptoapis-io-mcp/ai#diagnostics ## Score history - 2026-10-23: 67 - 2026-10-22: 67 - 2026-10-21: 66 ## Common questions ### What is the io.github.CryptoAPIs-io/mcp server? io.github.CryptoAPIs-io/mcp is listed in the public MCP registry as io.github.CryptoAPIs-io/mcp. Combined Crypto APIs MCP server, all 14 products in one process. This page covers its hosted endpoint (https://ai.cryptoapis.io/mcp). ### Is the io.github.CryptoAPIs-io/mcp server safe to use? io.github.CryptoAPIs-io/mcp scores 67 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm. ### What tools does the io.github.CryptoAPIs-io/mcp server expose? io.github.CryptoAPIs-io/mcp exposes 60 tools: address_history__manage_address, address_history__evm_address_history, address_history__utxo_address_history, address_history__system_info, address_latest__evm_address_latest, and 55 more. Their descriptions and schemas cost roughly 18,804 tokens of context every time the server is loaded. ### Does the io.github.CryptoAPIs-io/mcp server require authentication? Yes. io.github.CryptoAPIs-io/mcp asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything. ### Is the io.github.CryptoAPIs-io/mcp server still maintained? io.github.CryptoAPIs-io/mcp is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced. ## Links - Remote endpoint: https://ai.cryptoapis.io/mcp - Authorisation metadata: https://ai.cryptoapis.io/.well-known/oauth-protected-resource/mcp - Repository: https://github.com/CryptoAPIs-io/cryptoapis-mcp-hub - Changelog RSS feed: https://verifymcp.io/servers/cryptoapis-io-mcp/ai.xml - Changelog JSON feed: https://verifymcp.io/servers/cryptoapis-io-mcp/ai.json - HTML version of this page: https://verifymcp.io/servers/cryptoapis-io-mcp/ai