canonical: https://jentic.com/apis/cryptapi.io/cryptapi

# CryptAPI

CryptAPI provides a non-custodial cryptocurrency payment gateway that creates fresh forwarding addresses for each customer and routes funds straight to a merchant wallet. The API supports multiple chains including Bitcoin, Ethereum, Litecoin, Bitcoin Cash, and several stablecoins, and exposes helpers for QR code generation, fee estimation, and fiat-to-crypto price conversion. There are no per-transaction API fees beyond the small forwarding fee, and no signup or KYC is required to start accepting payments.

## For AI agents

Generate per-payment cryptocurrency addresses, track confirmations through webhook callbacks, and convert between crypto and fiat amounts across multiple blockchains.

## Scope

Does not handle fiat card processing, custodial wallet storage, or KYC/AML verification - use for non-custodial crypto payment forwarding only.

## Capabilities

- Create a unique forwarding address for a specific cryptocurrency that routes incoming payments to a merchant wallet
- Generate a QR code image for a payment address with optional amount embedded for one-click mobile wallet scans
- Estimate the network fee required to confirm a transaction on a given blockchain before quoting a customer
- Convert a fiat amount such as USD or EUR into the equivalent crypto value at the current market rate
- Retrieve the callback log and confirmation status for every payment associated with a generated address
- List the supported blockchains and tickers along with their minimum transaction sizes and fee structures

## Use cases

### Non-Custodial Crypto Checkout

Accept cryptocurrency payments on an e-commerce site without ever touching customer funds. CryptAPI generates a fresh forwarding address per order, watches the chain for incoming transactions, and forwards confirmed funds straight to the merchant wallet while firing a callback so the storefront can mark the order paid. Integration takes a few hours because there is no signup, KYC, or settlement account to configure.

Example prompt: Call /{ticker}/create/ for ticker btc with the merchant address and a callback URL, then return the generated payment address and QR code to the checkout page.

### Multi-Chain Donation Page

Run a single donations page that accepts Bitcoin, Ethereum, Litecoin, and major stablecoins by generating a per-visitor address for each chain. CryptAPI normalises the address creation and callback flow across blockchains, so a creator does not have to integrate separate SDKs for each network. Fee estimation and fiat conversion endpoints let the page show donors how much their pledge is worth in their local currency before they send.

Example prompt: For each supported ticker (btc, eth, ltc, usdt_trc20), call /{ticker}/create/ and /{ticker}/qrcode/ to produce a four-chain donation widget.

### Invoicing in Local Currency

Issue invoices in USD or EUR while letting customers settle in crypto. The /{ticker}/convert/ endpoint returns the live conversion rate so an invoice can be locked at a fiat amount and converted to crypto at the moment of payment, and /{ticker}/estimate/ surfaces the network fee so the buyer is not surprised. Suitable for B2B invoicing where prices are quoted in fiat but settlement happens on-chain.

Example prompt: Call /{ticker}/convert/ for ticker usdt_trc20 with value=2500 and from=USD to compute the crypto amount, then call /{ticker}/create/ to issue the address.

### AI Agent Crypto Payment Flow

AI agents acting on behalf of a user or merchant can accept crypto payments end-to-end through Jentic. The agent searches for the CryptAPI create-address operation, loads its schema, and executes the call with credentials sourced from your Jentic One instance, then polls the logs endpoint for confirmations. This avoids embedding secrets in agent context and removes the need to scrape CryptAPI documentation at runtime.

Example prompt: Search Jentic for 'create a cryptocurrency payment address', load the CryptAPI create operation, and execute it with merchant address and callback URL.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/info/` | List supported blockchains and tickers |
| GET | `/{ticker}/info/` | Get details and minimums for a specific ticker |
| GET | `/{ticker}/create/` | Create a forwarding payment address |
| GET | `/{ticker}/logs/` | Retrieve callback log for a payment address |
| GET | `/{ticker}/qrcode/` | Generate a QR code for a payment address |
| GET | `/{ticker}/estimate/` | Estimate network fee for a transaction |
| GET | `/{ticker}/convert/` | Convert between fiat and crypto amounts |

## Key resources

- **Info** — List supported blockchains, tickers, and per-chain minimum transaction sizes
- **Payment** — Create forwarding addresses and retrieve callback logs for a specific ticker
- **Tools** — Generate QR codes, estimate network fees, and convert between fiat and crypto

## Why Jentic

- **Setup:** Wiring CryptAPI by hand means constructing its ticker-scoped GET paths for create, logs, estimate, and convert, and standardizing the call shape yourself. Through Jentic you install once, import CryptAPI from the API Directory, and your agent calls it, with any merchant wallet or callback secret stored for you.
- **Permission scoping:** CryptAPI is a keyless public forwarding service, so limit the agent to the operations it needs, such as creating a payment address or reading callback logs for a ticker. You choose the operations it may call, so anything beyond payment forwarding is not included unless you add it.
- **Credential handling:** CryptAPI itself needs no key, but any merchant wallet address or callback secret you supply is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'accept a bitcoin payment' or 'estimate a forwarding fee', and Jentic returns the matching CryptAPI operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **NOWPayments API** — Custodial crypto payment processor with auto-conversion to fiat or stablecoins
- **Blockchain.com API** — Wallet and on-chain data API for Bitcoin and other major chains
- **CoinGecko API** — Market data feed for crypto prices and exchange rates

## FAQ

### What authentication does the CryptAPI use?

CryptAPI does not require API keys or signup. Callers identify themselves through the merchant address supplied when creating a forwarding address. When called through Jentic, any per-merchant identifiers stay inside your Jentic One instance rather than the agent context.

### Can I accept stablecoins like USDT with the CryptAPI?

Yes. CryptAPI supports USDT on Tron and other chains alongside Bitcoin, Ethereum, Litecoin, Bitcoin Cash, and several other tickers. Call /info/ to retrieve the current list of supported tickers and their minimum transaction sizes before generating an address.

### What are the rate limits for the CryptAPI?

CryptAPI does not publish a hard request limit, but the official documentation asks integrators to keep callback URLs idempotent and avoid polling /{ticker}/logs/ more frequently than once every few seconds per address. Use the callback URL passed to /{ticker}/create/ for confirmations rather than polling.

### How do I create a Bitcoin payment address with the CryptAPI through Jentic?

Search Jentic for 'create a cryptocurrency payment address', load the CryptAPI create operation, and execute it with ticker=btc, the merchant address, and a callback URL. The endpoint /{ticker}/create/ returns the address and QR code parameters in a single response.

### Is the CryptAPI free?

There are no per-call API fees. CryptAPI takes a small percentage of each forwarded transaction as a service fee, which is deducted from the forwarded amount on-chain rather than billed separately. Network fees are paid by the sender.

### How do I track whether a payment confirmed?

Pass a callback URL to /{ticker}/create/ and CryptAPI will POST confirmation events to it. To reconcile after the fact, call /{ticker}/logs/ with the address and the callback URL to fetch every callback event and current confirmation count.

### Can I limit what my agent is allowed to do with the CryptAPI?

Yes. Because you run Jentic One yourself, your own rules decide which CryptAPI operations the agent may call, so you can restrict it to just what it needs, such as creating a forwarding address with /{ticker}/create/ and reading callback logs with /{ticker}/logs/. Anything beyond payment forwarding, like fee estimation via /{ticker}/estimate/ or fiat conversion via /{ticker}/convert/, is excluded unless you explicitly allow it. Since CryptAPI is keyless, any merchant wallet address or callback secret you supply stays inside your self-hosted instance and is injected only at execution time, never entering the agent's context.