CoinAPI Market Data REST API

Name: CoinAPI Market Data REST API
Brand: CoinAPI Market Data REST API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentFinanceBankingapiKey50 EndpointsREST

For Agents

Query unified cryptocurrency market data - assets, exchanges, OHLCV, trades, quotes, and conversion rates - across hundreds of crypto venues from a single API.

Install Jentic One Beta

Connect the CoinAPI Market Data REST API to your agent

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

Convert any base asset to any quote asset using current or historical exchange rates

Retrieve OHLCV candles for crypto pairs across multiple time periods and date ranges

List supported exchanges and inspect trading symbols across spot and derivative markets

GET STARTED

Start building with CoinAPI Market Data REST API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use CoinAPI Market Data REST API for, with concrete tasks.

★ Unified Crypto Market Data Feed

Pull normalized real-time and historical data from hundreds of cryptocurrency exchanges through a single REST interface. CoinAPI standardizes asset identifiers, exchange ids, and symbol formats so trading systems and analytics dashboards do not need per-exchange adapters. Integration takes a few hours instead of weeks of per-exchange work.

Call GET /v1/exchangerate/BTC/USD and return the current rate, timestamp, and source

Backtesting Crypto Trading Strategies

Retrieve historical OHLCV candles and exchange-rate history to backtest algorithmic trading strategies. The history endpoints support multiple time periods and date ranges, returning consistently formatted data across exchanges. Useful for quant researchers and trading firms validating models before deploying capital.

Fetch hourly OHLCV history for ETH-USD between two given timestamps via GET /v1/exchangerate/ETH/USD/history and return the candle series

Portfolio Valuation in Fiat

Convert holdings of arbitrary crypto assets into a chosen fiat currency using current exchange rates. The exchangerate endpoints accept any base and quote pair and return a normalized rate sourced from aggregated venues. Suitable for portfolio trackers, accounting systems, and tax reporting tools.

For each holding in a portfolio, call GET /v1/exchangerate/{asset_id_base}/USD and sum the converted values to compute total portfolio value in USD

AI Trading Agent via Jentic

Build an AI trading agent that retrieves live crypto prices, historical context, and order book depth through Jentic. The agent expresses intents in natural language; Jentic resolves the right CoinAPI endpoint and executes the call with stored credentials. Decisions and analysis stay in the agent layer; data retrieval is one hop.

Through Jentic, fetch the latest BTC-USD rate and the last 24 hourly candles, then summarise the short-term trend

Key Endpoints

50 endpoints — jentic publishes the only available openapi specification for coinapi market data rest api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/v1/assets

List all supported assets

GET

/v1/exchanges

List supported cryptocurrency exchanges

GET

/v1/exchangerate/{asset_id_base}/{asset_id_quote}

Get current exchange rate between two assets

GET

/v1/exchangerate/{asset_id_base}/{asset_id_quote}/history

Retrieve historical exchange rates between two assets

GET

/v1/metrics/asset/listing

List metrics available for assets

GET

/v1/assets

List all supported assets

GET

/v1/exchanges

List supported cryptocurrency exchanges

GET

/v1/exchangerate/{asset_id_base}/{asset_id_quote}

Get current exchange rate between two assets

GET

/v1/exchangerate/{asset_id_base}/{asset_id_quote}/history

Retrieve historical exchange rates between two assets

GET

/v1/metrics/asset/listing

List metrics available for assets

Why Jentic?

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

Credential isolation

Your CoinAPI key 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.

Intent-based discovery

Agents search Jentic by intent such as 'get the current BTC to USD rate' or 'list supported exchanges', and Jentic returns the matching CoinAPI operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using CoinAPI Market Data REST API through Jentic.

Why is there no official OpenAPI spec for CoinAPI Market Data REST API?

CoinAPI does not publish an OpenAPI specification on its own developer portal. Jentic generates and maintains this spec so that AI agents and developers can call CoinAPI Market Data REST API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the CoinAPI Market Data REST API use?

CoinAPI uses an API key sent in the X-CoinAPI-Key header (a JWT alternative is also supported). When called through Jentic, the key is stored in your encrypted Jentic One instance and the agent receives a scoped execution token rather than the raw secret.

Can I retrieve historical OHLCV candles with this API?

Yes. Use GET /v1/exchangerate/{asset_id_base}/{asset_id_quote}/history with period_id and time_start/time_end parameters to retrieve historical candles for any supported pair. Period definitions are listed at GET /v1/exchangerate/history/periods.

What are the rate limits for the CoinAPI Market Data REST API?

CoinAPI enforces request and credit limits per subscription tier - free, startup, streamer, and enterprise. Limits are headers-driven (x-ratelimit-remaining and x-ratelimit-reset) and the OpenAPI spec does not declare them; check the tier attached to your API key for exact thresholds.

How do I get a current crypto exchange rate through Jentic?

Install the SDK with pip install jentic, then search Jentic for get current crypto exchange rate, load the schema for GET /v1/exchangerate/{asset_id_base}/{asset_id_quote}, and execute the call with your asset pair (for example BTC and USD).

Does CoinAPI support derivative and spot markets in the same endpoint set?

Yes. Symbols, trades, quotes, and OHLCV endpoints all expose spot and derivative instruments - symbol metadata indicates the type. Filter by symbol_id_filter or exchange_id to scope queries to the markets you care about.

Can I limit what my agent is allowed to do with the CoinAPI Market Data REST API?

Yes. Because you run Jentic One yourself, your own rules decide which CoinAPI operations and credentials the agent may use. Since CoinAPI market data is read-only, you scope by choosing the specific calls the agent can make, such as fetching an exchange rate through GET /v1/exchangerate/{asset_id_base}/{asset_id_quote} or listing assets and exchanges, while leaving heavier operations like full OHLCV history pulls out unless you deliberately add them. Your API key stays in your Jentic One instance and is injected only for the operations you permit.