Developer Guides

Build with CryptoAPIs

Practical, step-by-step guides for building crypto payments and blockchain apps on our APIs — non-custodial by design, across 35+ networks. Every guide leads with real requests you can run today.

Payments

Accept and move crypto without giving up your keys — the API handles the public data and the heavy lifting; you sign offline.

Payments · Non-custodial

How to accept crypto payments

Take Bitcoin, Ethereum and stablecoin payments to an address you control — single-address or per-order — watch for payment with a webhook, and sweep by signing offline.

Read the guide →
Payments · Non-custodial

How to automate payment forwarding

Auto-forward incoming deposits to your treasury without a custodian — watch, prepare an unsigned sweep, sign offline and broadcast, on a loop. Your keys never leave your infrastructure.

Read the guide →

Wallets & events

Build wallets and react to on-chain activity in real time — non-custodial, no nodes to run.

Wallets · Non-custodial

How to build a crypto wallet

Ship a wallet where users keep their keys — derive addresses from an xPub, track balances and transactions across 35+ networks, and send by signing offline.

Read the guide →
Events

How to monitor addresses with webhooks

Get a real-time callback the moment an address receives a payment, a token transfer or a new block — no polling, no node.

Read the guide →

AI

Give AI agents live, non-custodial blockchain access.

AI · MCP

How to use CryptoAPIs with AI agents

Connect blockchain tools to Claude Desktop, Cursor or n8n over MCP — read balances and transactions, watch addresses and sign locally across 35+ networks.

Read the guide →

Frequently Asked Questions

Where should I start if I have never used the API?

Read an address balance first — one call, no setup, no webhook. Once that works, monitoring addresses with webhooks is the next step, because almost every integration is built on knowing when money arrives.

Do the guides assume a particular language?

No. They are written against the REST endpoints, so the requests are the same whatever you call them from. Where a guide uses code it is illustrative — the offline signer is the one place a specific package matters, and that one is Node.

Can I follow these without spending real funds?

Yes. Most chains we serve have a testnet on the same endpoints, so you change the network parameter and nothing else. Build and verify the whole flow there before you touch mainnet.