Crypto APIs Blockchain REST API

Name: Crypto APIs Blockchain REST API
Brand: Crypto APIs Blockchain REST API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring ObservabilityapiKey8 EndpointsREST

For Agents

Look up balances, transactions, and blocks across multiple blockchains, generate wallet addresses, and subscribe to on-chain confirmation callbacks.

Install Jentic One Beta

Connect the Crypto APIs Blockchain REST API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Crypto APIs Blockchain REST API, 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 Crypto APIs Blockchain REST API.

Look up the balance and transaction history for an address on a specific blockchain and network

Retrieve a transaction by hash including its inputs, outputs, fee, and confirmation count

Fetch a block by height or hash and inspect every transaction it contains

GET STARTED

Start building with Crypto APIs Blockchain REST API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Crypto APIs Blockchain REST API for, with concrete tasks.

★ Multi-Chain Deposit Reconciliation

Reconcile customer deposits across Bitcoin, Ethereum, and Litecoin by querying address transactions through a single API instead of running a node per chain. The agent fetches each customer's deposit address transactions, matches confirmed amounts against expected payments, and updates the ledger. This replaces bespoke node infrastructure with a hosted REST surface that scales with traffic.

Call GET /blockchain-data/{blockchain}/{network}/addresses/{address}/transactions for each customer address and reconcile confirmed transactions against expected payments.

Address Generation for Wallet-as-a-Service

Run a custodial product that issues a fresh receiving address per customer without managing private keys directly. Crypto APIs' wallet-as-a-service generates addresses inside a managed wallet and ties them back to the parent wallet for withdrawal aggregation. The same API surface works across blockchains so onboarding a new chain only changes the path parameter.

Call POST /wallet-as-a-service/wallets/{walletId}/{blockchain}/{network}/addresses to generate a fresh deposit address for a customer.

On-Chain Confirmation Webhooks

Trigger backend workflows the moment an incoming transaction confirms instead of polling the chain. Crypto APIs' address-coins-transactions-confirmed subscription sends a callback with the transaction hash and confirmation count, letting an order processor mark a payment received in near real time. Combined with address validation, this prevents writing funds to malformed destination strings.

Call POST /blockchain-events/{blockchain}/{network}/subscriptions/address-coins-transactions-confirmed with the deposit address and a callback URL.

AI Agent Blockchain Lookups

Agents answering 'what is the balance of this wallet' or 'did this transaction confirm' need a stable, schema'd blockchain backend rather than scraping block explorers. Through Jentic the agent searches for the relevant Crypto APIs operation, loads its schema, and executes against the x-api-key stored in the vault. Latency is predictable because the API is hosted, not run on commodity nodes.

Search Jentic for 'look up a blockchain transaction', load the Crypto APIs operation, and execute it with blockchain=bitcoin, network=mainnet, and the transaction hash.

Key Endpoints

8 endpoints — crypto apis provides unified blockchain rest endpoints across bitcoin, ethereum, litecoin, and other major chains so developers do not have to run their own nodes.

METHOD

PATH

DESCRIPTION

GET

/blockchain-data/{blockchain}/{network}/addresses/{address}

Get address balance and metadata

GET

/blockchain-data/{blockchain}/{network}/addresses/{address}/transactions

List transactions for an address

GET

/blockchain-data/{blockchain}/{network}/transactions/{transactionId}

Get a transaction by hash

GET

/blockchain-data/{blockchain}/{network}/blocks/{blockId}

Get a block by height or hash

GET

/blockchain-data/{blockchain}/{network}/blocks/last

Get the latest block

POST

/wallet-as-a-service/wallets/{walletId}/{blockchain}/{network}/addresses

Generate a wallet receiving address

POST

/blockchain-events/{blockchain}/{network}/subscriptions/address-coins-transactions-confirmed

Subscribe to confirmation callbacks

GET

/blockchain-tools/{blockchain}/{network}/addresses/validate

Validate an address string

GET

/blockchain-data/{blockchain}/{network}/addresses/{address}

Get address balance and metadata

GET

/blockchain-data/{blockchain}/{network}/addresses/{address}/transactions

List transactions for an address

GET

/blockchain-data/{blockchain}/{network}/transactions/{transactionId}

Get a transaction by hash

GET

/blockchain-data/{blockchain}/{network}/blocks/{blockId}

Get a block by height or hash

GET

/blockchain-data/{blockchain}/{network}/blocks/last

Get the latest block

Why Jentic?

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

Credential isolation

Crypto APIs x-api-key is stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access and never see the raw key, so a leaked agent transcript cannot expose blockchain account quotas.

Intent-based discovery

Agents search by intent (for example 'look up an address balance' or 'subscribe to a blockchain confirmation') and Jentic returns the matching Crypto APIs operation with its input schema.

Time to first call

Direct Crypto APIs integration: 1-2 days for auth, plan handling, and webhook setup. Through Jentic: under 30 minutes — search, load schema, execute.

FAQs

Specific to using Crypto APIs Blockchain REST API through Jentic.

What authentication does the Crypto APIs Blockchain REST API use?

Crypto APIs uses an x-api-key header. Every request must include the header with a key issued from the Crypto APIs dashboard. Through Jentic the key is sourced from the vault and never reaches the agent context.

Can I look up an Ethereum balance with the Crypto APIs Blockchain REST API?

Yes. Call GET /blockchain-data/{blockchain}/{network}/addresses/{address} with blockchain=ethereum and network=mainnet to retrieve the address balance and metadata. The same path supports Bitcoin and other blockchains by changing the path parameter.

What are the rate limits for the Crypto APIs Blockchain REST API?

Limits depend on the Crypto APIs plan tier and reset monthly rather than per second. The dashboard reports remaining calls per plan; treat the API as request-budgeted rather than rate-bursted.

How do I subscribe to a confirmation callback through Jentic?

Search Jentic for 'subscribe to a blockchain confirmation' and execute the loaded operation against POST /blockchain-events/{blockchain}/{network}/subscriptions/address-coins-transactions-confirmed with the address and callback URL.

Is the Crypto APIs Blockchain REST API free?

Crypto APIs offers a free tier with a monthly request quota and paid tiers above that. Pricing is published at https://cryptoapis.io/pricing.

How do I validate a Bitcoin address before sending funds?

Call GET /blockchain-tools/{blockchain}/{network}/addresses/validate with blockchain=bitcoin to verify the address is syntactically valid and correctly checksummed for the target network.