Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Coinranking 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcoinranking.com%2Fcoinranking" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcoinranking.com%2Fcoinranking" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with Coinranking API.
List ranked coins and their live prices, market caps, and 24h changes via GET /coins
Pull price history at multiple timeframes via GET /coin/{uuid}/price-history
Retrieve OHLCV candles for technical analysis via GET /coin/{uuid}/ohlcv
Resolve a token by blockchain contract address via GET /blockchain/{uuid}/contract-address/{contractAddress}
GET STARTED
Track BTC dominance and global market cap history via GET /stats/btc-dominance-history and /stats/market-cap-history
Compare centralised exchanges and DEXs through /exchanges, /dexs, and their per-venue coin and market listings
Surface trending coins via GET /coins/trending
Patterns agents use Coinranking API for, with concrete tasks.
★ Live Crypto Market Dashboard
Power a market dashboard with ranked coin lists, live prices, and 24h change pulled from /coins along with global stats from /stats. Coinranking returns market cap, volume, change, and rank in a single paginated response so a dashboard can render the top 100 coins without coordinating multiple endpoints. Reference currency is configurable via referenceCurrencyUuid for fiat or stablecoin denomination.
Call GET /coins?limit=100&orderBy=marketCap and GET /stats together, then return a JSON object with top coins and total market cap
Price History Charts
Render price charts for any listed coin by fetching /coin/{uuid}/price-history at the desired timeframe (24h, 7d, 30d, 1y, 5y). Coinranking returns timestamped price points ready for charting libraries with no further transformation. Pair with /coin/{uuid}/ohlcv when candlestick rendering is required.
Fetch GET /coin/Qwsogvtv82FCd/price-history?timePeriod=30d for Bitcoin and return the price array for charting
DEX and Token Discovery
Investigate decentralised-exchange activity by listing DEXs via /dexs and their markets via /dex/{uuid}/markets. Combine with /blockchain/{uuid}/contract-address/{contractAddress} to identify unknown tokens encountered on-chain. This supports research workflows that need to attribute on-chain activity back to named coins and venues.
Call GET /blockchain/ethereum/contract-address/0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48 to identify the token, then GET /coin/{uuid}/exchanges to list where it trades
Macro Crypto Research
Track macro indicators such as BTC dominance and global market cap over time via /stats/btc-dominance-history and /stats/market-cap-history. Researchers and reporting tools can pull multi-year series in a single call to power newsletters, models, or quarterly reports without scraping public chart sites.
Call GET /stats/btc-dominance-history?timePeriod=1y and return the dominance percentage series
AI Agent Crypto Lookup via Jentic
Give an AI agent live crypto context through Jentic by searching for the operation it needs (price lookup, OHLCV, DEX listings) and executing it with the returned schema. The x-access-token credential is held in your Jentic One instance so it is never exposed in agent prompts or logs. Agents can access market data without parsing Coinranking's raw documentation.
Use Jentic to search 'get crypto price history', load the GET /coin/{uuid}/price-history schema, and execute it for uuid=Qwsogvtv82FCd with timePeriod=7d
34 endpoints — jentic publishes the only available openapi specification for coinranking api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/coins
List ranked coins with live prices
/coin/{uuid}/price-history
Get historical price series for a coin
/coin/{uuid}/ohlcv
Get OHLCV candles for a coin
/blockchain/{uuid}/contract-address/{contractAddress}
Resolve token by contract address
/stats/btc-dominance-history
Historical BTC dominance percentage
/exchanges
List centralised exchanges
/coins/trending
List trending coins
/coins
List ranked coins with live prices
/coin/{uuid}/price-history
Get historical price series for a coin
/coin/{uuid}/ohlcv
Get OHLCV candles for a coin
/blockchain/{uuid}/contract-address/{contractAddress}
Resolve token by contract address
/stats/btc-dominance-history
Historical BTC dominance percentage
/exchanges
List centralised exchanges
/coins/trending
List trending coins
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Coinranking by hand means setting its x-access-token header on the api.coinranking.com host and handling pagination and reference-currency parameters across its coin, exchange, and stats endpoints yourself. Through Jentic you install once, import Coinranking from the API Directory, store the token once, and your agent calls it.
Permission scoping
Coinranking serves read-only market data, so you scope by choosing the operations the agent may call: limit it to what it needs, such as listing coins or reading trending coins, and heavier calls like full price history are not included unless you add them.
Credential isolation
Your Coinranking access token is stored once, encrypted, by your own Jentic One instance and injected into the request header at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'get crypto price history' or 'find trending coins', and Jentic returns the matching Coinranking operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Coinranking API through Jentic.
Why is there no official OpenAPI spec for Coinranking API?
Coinranking does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Coinranking 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 Coinranking API use?
Coinranking expects an API key in the x-access-token header on every request to api.coinranking.com/v2. Through Jentic the key is stored encrypted in the vault and injected at execution so it never appears in agent prompts or logs.
Can I get OHLCV candle data with the Coinranking API?
Yes. GET /coin/{uuid}/ohlcv returns open-high-low-close-volume candles for any listed coin. Combine with /coin/{uuid}/price-history when you only need closing-price series for charting.
What are the rate limits for the Coinranking API?
Rate limits are tier-based and enforced by the x-access-token. The OpenAPI spec does not enumerate exact quotas; consult your Coinranking developer dashboard for your current tier limits. HTTP 429 indicates you have exceeded them.
How do I look up a token by contract address with the Coinranking API through Jentic?
Search Jentic for 'lookup token by contract address', load the GET /blockchain/{uuid}/contract-address/{contractAddress} schema, and execute it with the blockchain uuid (e.g. ethereum) and the token's contract address. Jentic returns the matching coin record without manual auth setup.
Does Coinranking cover decentralised exchanges?
Yes. GET /dexs lists DEXs and GET /dex/{uuid}/markets returns the trading pairs on each. This makes Coinranking suitable for research that needs both centralised exchange and DEX coverage in one feed.
Can I limit what my agent is allowed to do with the Coinranking API?
Yes. Because you run Jentic One yourself, your own rules decide which Coinranking operations and credentials the agent may use. Since Coinranking is read-only market data, you scope access by picking the operations you import, so you can allow lighter calls like GET /coins or GET /coins/trending while leaving heavier ones such as GET /coin/{uuid}/price-history or GET /coin/{uuid}/ohlcv out unless you explicitly add them. Your access token is held by your own instance and injected only for the operations you have permitted.
Know of an official OpenAPI document? Contribute it →
For Agents
Query 34 endpoints for live and historical crypto coin prices, OHLCV candles, exchange and DEX listings, and global market statistics including BTC dominance.
Use for: Get the current price and market cap of Bitcoin, Retrieve 30 days of price history for Ethereum, Find which exchanges list a specific coin, Look up a token by its contract address on Polygon
Not supported: Does not handle order execution, wallet balances, or on-chain transactions - use for read-only crypto market data only.
Jentic publishes the only available OpenAPI specification for Coinranking API, keeping it validated and agent-ready. Coinranking provides real-time and historical cryptocurrency market data covering coins, exchanges, decentralised exchanges, markets, blockchains, and global statistics. The API exposes 34 read-only endpoints including coin price history, OHLCV candles, market-cap and volume history, BTC dominance, exchange and DEX details, and contract-address lookups across blockchains. Authentication is via the x-access-token header against api.coinranking.com/v2.