CryptAPI

Name: CryptAPI API
Brand: CryptAPI
Availability: InStock

★ Only Publicly Available OpenAPI DocumentPaymentsPayment Processingnone7 EndpointsREST

For Agents

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

Install Jentic One Beta

Connect the CryptAPI to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the CryptAPI, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with CryptAPI API.

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

GET STARTED

Start building with CryptAPI API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use CryptAPI API for, with concrete tasks.

★ 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.

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.

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.

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 the Jentic vault, then polls the logs endpoint for confirmations. This avoids embedding secrets in agent context and removes the need to scrape CryptAPI documentation at runtime.

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

Key Endpoints

7 endpoints — cryptapi provides a non-custodial cryptocurrency payment gateway that creates fresh forwarding addresses for each customer and routes funds straight to a merchant wallet.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

CryptAPI is keyless, but merchant wallet addresses and callback URL secrets are stored in the Jentic vault (MAXsystem) so they never appear in agent context or logs.

Intent-based discovery

Agents search by intent (for example 'accept a bitcoin payment') and Jentic returns the matching CryptAPI operation with its input schema, so the agent can call /{ticker}/create/ without browsing CryptAPI documentation.

Time to first call

Direct CryptAPI integration: half a day for callback handling and per-chain testing. Through Jentic: under 30 minutes — search, load schema, execute.

FAQs

Specific to using CryptAPI API through Jentic.

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 the Jentic vault 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.