Crypto APIs

Developer Tools Finance

v0.4.0

Last updated Oct 20, 2026

n8n community node for Crypto APIs — blockchain infrastructure for 15+ protocols

51 Weekly Downloads

300 Monthly Downloads

View on NPM GitHub Repository

Included Nodes

Crypto APIs

Description

n8n-nodes-cryptoapis

This is an n8n community node for Crypto APIs. It lets you use Crypto APIs blockchain services directly in your n8n workflows.

Crypto APIs provides unified blockchain APIs for 15+ blockchains including Bitcoin, Ethereum, Polygon, Avalanche (C-Chain), XRP, Solana, and more.

n8n is a fair-code licensed workflow automation platform.

Installation

Follow the installation guide in the n8n community nodes documentation.

Credentials

You need a Crypto APIs API key to use this node. Get one at app.cryptoapis.io.

The credential supports an optional API URL field for users with custom API setups. The default is https://rest.cryptoapis.io.

A note on masked fields

Token Amount and Token ID fields render as masked inputs (dots instead of characters). They are not secrets — they are public on-chain values such as a transfer amount, an ERC-721 NFT index, or a Tezos FA2 token index, and none of them are sensitive.

They are masked because n8n’s community-node rules treat any parameter whose name contains “token” as a credential, and the rule’s exemption list cannot be extended by a package. Renaming the fields would remove the masking, but n8n discards a saved parameter whose name no longer matches the node, which would silently break existing workflows. The rename is planned for the next major version, with a migration note.

If you need to check what you typed, you can widen the field or paste the value into a Set node first.

Resources & Operations

AML

Anti-money-laundering risk checks. Verify Address flags an address associated with fraud, sanctions, ransomware, exploits or darknet markets, returning a risk score, risk band and the flagging sources. Screen Transaction screens a transaction across 19 blockchains (EVM, UTXO, XRP, Solana, Tezos, Kaspa, Tron), returning the flagged participants with their roles, scores, severities and categories. Get Address Exposure returns the risky entities (sanctions, darknet markets, ransomware, etc) an address is connected to and the share of funds involved. List Address Exposure Paths returns the fund-flow paths that connect an address to those risky entities, with cursor-based pagination (Limit, Starting After, optional Root Address) — it fetches one page per call and does not auto-paginate, so feed the returned nextStartingAfter back into a subsequent call yourself.

The two exposure operations support a narrower set of 13 blockchains — ethereum, binance-smart-chain, ethereum-classic, polygon, tron, bitcoin, bitcoin-cash, litecoin, dogecoin, dash, zcash, xrp, solana — since not every chain Screen Transaction covers has an exposure graph.

> These are among the most expensive endpoints in the API — 200,000 credits per address verification, 500,000 per transaction screening, 200,000 per address exposure request, and 100,000 per exposure-paths page. Put them behind an IF node or a filtered branch rather than calling them on every item in a loop.

Address Latest

Query current balances and recent transactions (last 14 days) across EVM, UTXO, Solana, XRP, and Kaspa blockchains.

Address History

Full transaction history for synced addresses. Requires address sync first. Supports EVM and UTXO blockchains.

Block Data

Get block details by height or hash, list transactions within blocks, and retrieve latest mined blocks for EVM, UTXO, and XRP.

Blockchain Fee

Fee recommendations and gas estimation for EVM (including EIP-1559), UTXO smart fee estimation, XRP fee recommendations, Tezos fee estimates for native XTZ / FA1.2 / FA2 transfers, and Solana compute-unit estimates for native, SPL token, and program-invocation transactions.

Transaction Data

Transaction details, internal transactions, token transfers, and event logs across EVM, UTXO, Solana, XRP, and Kaspa.

Market Data

Asset details, exchange rates, and supported asset metadata (crypto and fiat).

Contract

Token details by contract address for EVM (Ethereum, BSC, Ethereum Classic) and Solana.

HD Wallet

HD wallet management (sync, list, activate, delete), address derivation, balance queries, and transaction preparation for EVM, UTXO, and XRP.

Prepare Transaction

Build unsigned transactions across six chain families: EVM (native coin, ERC-20, ERC-721), Tezos (native XTZ, FA1.2, FA2), Solana (native SOL, SPL tokens), XRP, Kaspa, and UTXO. Kaspa and UTXO support multiple outputs in one transaction.

Simulate

Dry-run Ethereum transactions to preview outcomes without broadcasting.

Broadcast

Broadcast signed transactions to any supported blockchain network.

Blockchain Event

Create and manage webhook subscriptions for blockchain events (confirmed/unconfirmed transactions, new blocks, etc.).

Utility

Address validation, raw transaction decoding, address derivation from xPub, Bitcoin Cash address conversion, and XRP X-Address encode/decode.

AI Agent Integration

Using as an AI Tool (usableAsTool)

The main Crypto APIs node has usableAsTool: true, so it can be used directly as a tool by n8n’s AI Agent node — just connect it to an AI Agent and it will expose its operations as tool calls.

MCP Client Tool

You can also use n8n’s built-in MCP Client Tool node to connect to the hosted Crypto APIs MCP server at https://ai.cryptoapis.io/mcp or a self-hosted instance. This gives AI agents access to 50+ blockchain tools via MCP.

Supported Blockchains & Networks

EVM

UTXO

Other

Development

npm install
npm run build       # Compiles to dist/
npm run dev         # Watch mode
npm run lint        # Type check + ESLint (n8n node rules)
npm run typecheck   # Type check only

To check the package against n8n’s own verification gate:

npx @n8n/scan-community-package @cryptoapis-io/n8n-nodes-cryptoapis

Local testing

Install in local n8n
cd ~/.n8n
npm install /path/to/cryptoapis-n8n-nodes
Then restart n8n

Changelog

CHANGELOG.md‘s entries up to v0.3.0 were backfilled by hand from the
published GitHub releases; every release since then is generated by
auto-changelog (see CLAUDE.md “Release”), which lists only the commits
after the latest tag, deduplicated and with hosting-generated PR merge
commits excluded, leaving
the backfilled entries untouched. Verify it before a release:

git fetch https://github.com/CryptoAPIs-io/cryptoapis-n8n-nodes.git 'refs/tags/:refs/tags/'
npm run changelog:check

changelog:check is a dry run — it never writes CHANGELOG.md, bumps the
version, or touches any tag. This flow has so far only been verified by dry
run: the full round-trip on the joined history (release, tag, npm publish,
GitHub release) is verified on the next functional n8n-nodes release, not by
a docs-only version.

License

MIT