Retrieve historical coin data (price, market cap, volume) for any date via CoinGecko, paid per-call on Tempo L2.
What it does
This endpoint returns historical snapshot data for a specific cryptocurrency on a given date, sourced from CoinGecko's comprehensive market database. You provide a coin ID (e.g. "bitcoin") and a date in DD-MM-YYYY format, and receive back the coin's price, market cap, volume, and other metadata as it was on that day. An optional localization flag controls whether multi-language name translations are included.
The endpoint is part of a broader CoinGecko proxy service hosted on the Locus MPP gateway at coingecko.mpp.paywithlocus.com. Sibling endpoints cover simple prices, market charts, trending coins, exchange rates, global stats, categories, top gainers/losers, and more — all sharing the same payment structure. Each call costs 60,000 base units of pathUSD (currency 0x20c…b50) on Tempo L2, which equals $0.06 per request. The payment intent is "charge" (one-shot per call).
Note: The endpoint accepts POST requests only. HEAD and GET probes returned 404, which is expected since the OpenAPI spec defines only a POST method. The service's root URL also returns 404 with a helpful pointer to skill.md and llms.txt documentation. No response schema is documented in the OpenAPI spec, so the exact shape of the returned JSON must be inferred from CoinGecko's upstream /coins/{id}/history endpoint.
Capabilities
Use cases
- —Retrieve the price and market cap of Bitcoin on a specific historical date for backtesting or reporting
- —Build historical comparison charts showing how a coin's valuation changed over time
- —Populate research dashboards with point-in-time cryptocurrency snapshots
- —Verify historical token prices for accounting or tax purposes
- —Feed historical data into trading strategy simulations
Fit
Best for
- —Agents needing point-in-time crypto snapshots without managing CoinGecko API keys
- —Automated workflows that need pay-per-call access to historical coin data
- —Developers building crypto analytics tools who want simple micropayment-based access
Not for
- —High-frequency real-time price feeds (this returns historical snapshots, not live streams)
- —Bulk historical data downloads spanning many dates (each date is a separate paid call at $0.06)
Quick start
curl -X POST https://coingecko.mpp.paywithlocus.com/coingecko/coin-history \
-H "Content-Type: application/json" \
-d '{"id": "bitcoin", "date": "01-01-2023"}'Example
Request
{
"id": "bitcoin",
"date": "01-01-2023",
"localization": false
}Endpoint
Quality
The OpenAPI spec provides a clear request schema with required fields and payment info, but no response schema or examples are documented. The endpoint only accepts POST (HEAD/GET return 404, which is expected). No crawled pages returned useful documentation beyond error messages pointing to external docs.
Warnings
- —HEAD and GET probes returned 404; endpoint requires POST — not a liveness issue but the probe marked is_live=false incorrectly
- —No response schema documented in the OpenAPI spec; response shape must be inferred from upstream CoinGecko API
- —No example responses available from probe or crawl
- —Currency address 0x20c000000000000000000000b9537d11c60e8b50 assumed to be pathUSD with 6 decimals; if decimals differ, the $0.06 price would be wrong
Citations
- —Endpoint is defined as POST with required fields id and date, costing 60000 base units of pathUSD on Tempo L2https://coingecko.mpp.paywithlocus.com
- —CoinGecko API reference available at docs.coingecko.comhttps://docs.coingecko.com
- —LLM-oriented docs referenced at beta.paywithlocus.com/mpp/coingecko.mdhttps://beta.paywithlocus.com/mpp/coingecko.md