2 providers · from $0.00029 per call · $0.000 markup

CoinGecko API and Tiingo through one key: a crypto price API for live prices and history, per call

Give your agent a coin and get its price back as data: the current price in any quote currency for a whole watchlist in one call, or the price, market cap and volume series over a day, a month or the coin's whole life. CoinGecko and Tiingo answer through one treg.to key, from $0.00029 at the provider's own rate with no markup, and there is no CoinGecko key to paste into a spreadsheet, a dashboard or a device. What comes back is an aggregate price, not an order book, and it is polled, not streamed.

Start free See the comparison

$1.00 of free credit on every new team · no provider signup · no card

4 of 4 endpoints on this page are live-verified against the provider.

Try it

What’s the best way to ask ChatGPT?

1Set your agent up, once

in your agent's chat

set up treg — https://treg.to/llms.txt

2Ask for the job

the prompt

Using treg, get the current price and 24h change for bitcoin, ethereum and solana in USD in one call, then pull the last 30 days of daily prices for each and tell me which one moved most against its 30-day average. Show me the price per call first.

works in

Why this prompt works

Use CoinGecko coin ids

The call takes ids like bitcoin and ethereum, not tickers. BTC is not a coin id, and several tokens share a symbol.

Ask for the whole watchlist at once

Current price takes a comma-separated list of coins and currencies. One call for fifty coins costs the same as one call for one.

Say the window

History takes 1, 7, 30, 365 or max days, and the granularity follows the window: five-minute points under a day, hourly under 90 days, daily beyond.

Ask for the price first

treg.to returns the rate before the call, so the agent can say what a daily refresh of a hundred coins will spend.

Why treg.to

Why go through treg.to

One key, not 9 accounts

treg.to holds the provider keys. Neither you nor the agent sees them.

Price before the call

The provider's own rate, $0.000 markup, from a prepaid balance.

No subscription, no seats

Charged per call. $1.00 free per new team, no card to start.

Your own keys are free

Already pay Hunter? Register it and those calls are never metered.

Switch by changing a word

Another provider is a different word in the prompt, not a new integration.

Nothing to integrate

No SDK, no OAuth dance per vendor, no seats.

Behind the scenes

What ChatGPT sees before it calls

treg.to does not choose for you. It hands ChatGPT this comparison, with the price shown before any call, and ChatGPT picks. Or you tell it how: "cheapest", "most reliable", "the one that takes what I have", or a provider by name.

Which crypto price API is cheapest per call?

Cheapest per call

CoinGecko at $0.00029

Which one is the most reliable?

Provider	Success	Median	Sample
CoinGecko	100%	243ms	13 calls
Tiingo	100%	406ms	9 calls

Measured on treg.to traffic: real calls, real inputs, and sample sizes differ by provider. Live reliability, not a controlled benchmark.

How do CoinGecko and Tiingo compare?

Provider	Price	Accepts	Success rate	Verified
CoinGecko	$0.00029 per call	ids, vs_currencies, include_market_cap, include_24hr_vol, include_24hr_change, coin_id	100% (13 calls)	2026-08-15
Tiingo	free, 20 calls a day on treg.to's key, then your own key	tickers, startDate, resampleFreq	100% (9 calls)	2026-08-15

Run one

the cheapest verified call

treg call coingecko.simple.price --query ids=bitcoin,ethereum --query vs_currencies=usd --query include_24hr_change=true

Swap the id for any provider above. All 4 endpoints behind this job, with their parameters and captured responses, are on the Crypto Market Data shelf.

How these numbers are made

PricesEach provider’s own published rate, converted to US dollars for one chargeable event of the unit they bill in. treg.to adds $0.000. Where a provider bills in credits, the conversion uses the rate on their public pricing page, last checked 2026-08-15.

Success ratetreg.to’s own served calls over the last 30 days: 2xx counts as a success, 5xx and timeouts as a failure. A 4xx is excluded, because it usually means the caller sent bad parameters and one bad query should not make a healthy endpoint look broken.

What this is notA controlled benchmark. These are real calls with real inputs, so sample sizes and the difficulty of what was asked differ by provider. Treat the rates as live reliability, not a like-for-like test.

VerifiedThe date treg.to last called the endpoint end to end and confirmed the shape of its response and the price it charged.

From the field

What people actually struggle with

Crypto data threads are two-thirds noise: of the ~170 Reddit and X posts read in August 2026, most were token shills, subscription resellers and two 'finally found a free API' posts with the same arc in two subreddits. These five are people building something on a price feed.

The free tier's rate limit is the first thing that breaks

“There I ran into a problem with Rate limit from the Coingecko api itself.” r/coingecko

What this page can do about it: That poster was calling from Google Sheets, where every request leaves a shared Google IP. Through treg.to the call is one metered request on a paid key, a whole watchlist per call, and the sheet, the dashboard or the device holds no key at all.

Twelve months is where the free history stops

“CoinGecko only goes back 12 months, but I was hoping to go back further” r/CryptoCurrency

What this page can do about it: Per coin, the series call with days set to max returns the daily history CoinGecko holds, on the paid key treg.to serves it from. That poster wanted total market cap history, which is not this endpoint, and the page will not pretend it is.

Free is for testing; what happens at scale is the question

“Free APIs are fine for testing but I want something that scales.” r/ethdev, 6 points

What this page can do about it: Scale here means one credit a call, metered, with no plan tier to jump when the dashboard grows. What it does not mean is streaming: the feed is polled, and a bot that needs every tick is on a different product.

Nobody's number agrees with anybody else's

“CoinGecko API shows wrongs market capital data for 700M !” r/SmoothLovePotion

What this page can do about it: No comparison table can answer that. The price is the provider's aggregate and treg.to relays it as is. The cheap check is to pull the same pair as a Tiingo bar and let the agent flag the gap, which it can do in the same prompt.

The agent wrote the rate limiter

“until I had ChatGPT incorporate rate-limiting given the 500 rate limit/min” r/api_connector

What this page can do about it: The agent already does the plumbing. What it lacks is the key and the price, and one setup line gives it both: the call, the rate shown before it spends, and no CoinGecko token in its context.

The detail

What actually differs

The rate is per request, not per coin.

CoinGecko bills one credit for a successful call whatever the endpoint, and the current-price call takes a list of coin ids and a list of quote currencies, so the forum's "it only returns 28 of my 131 coins" is a pagination problem on a different endpoint, not a ceiling here. On treg.to's own key that credit is metered from your team's balance at the provider's rate; on your own CoinGecko key nothing is metered and the plan's limits are between you and CoinGecko.

History depth is CoinGecko's, and the page will not stretch it.

The series call returns per-coin prices over 1, 7, 30, 365 or max days with granularity set by the window, and the snapshot call returns one coin's price, market cap and volume on a date. Neither is a total-market-cap history and neither is a top-N-by-day table; an agent builds that by looping coins, one metered call each. Tiingo's bars are the exchange-style alternative, served free on treg.to's key at 20 calls a day per team, then on your own Tiingo key.

The price is an aggregate and it passes through unchanged.

CoinGecko's market cap and supply figures are its own, and the research has real examples of both being wrong for small tokens; treg.to relays the answer verbatim and adds no consensus, no spread and no second opinion. If a number matters, pull the Tiingo bar for the same pair and let the agent compare, which is a comparison you make, not one treg.to makes for you. Nothing here is a websocket, an order book or an exchange connection.

Background

What is the CoinGecko API?

The CoinGecko API is the query interface to CoinGecko's aggregate market data: a current price for any listed coin in any quote currency, with market cap, 24h volume and 24h change on request, and a history endpoint that returns the price, market cap and volume series for a coin over a window you choose. The number is an aggregate across the exchanges CoinGecko tracks, which is what a dashboard or an agent wants and what a trader on one exchange does not. Tiingo is the other provider here and answers a different shape: open, high, low, close and volume bars for a pair like btcusd, at a resample frequency from a minute to a day.

Questions

Before you start

Is the CoinGecko API free through treg.to?

Not free, cheap: one CoinGecko credit per successful call, metered from your team's prepaid balance at CoinGecko's own rate with $0.000 added. Each new team gets $1.00 to start, which is a lot of price calls. Register your own CoinGecko key and the calls are never metered.

How far back does the history go?

As far as CoinGecko's series for that coin goes, with days set to max, at daily granularity. Sub-daily points come only inside the recent windows: five-minute under a day, hourly under 90 days. Tiingo's bars go down to one minute for the pairs it carries, on its own history.

Can my agent stream prices or trade on them?

No. Both providers here answer a request with a number; there is no websocket, no order book and no exchange execution. An agent that refreshes a watchlist every few minutes is the fit; a bot that needs a tick feed is not.

Which provider should my agent use?

CoinGecko for coin ids, quote currencies and the aggregate market view; Tiingo for OHLCV bars on a pair. treg.to shows both with the rate and the measured success side by side; it compares, it does not route or fail over for you.