GET

/public_treasury/{entity_id}/{coin_id}/holding_chart

GET /public_treasury/{entity_id}/{coin_id}/holding_chart is an endpoint of the CoinGecko API API, listed on Proxygate by Proxygate. Crypto Treasury Holdings Historical Chart Data by ID AI agents call it per request through a transparent proxy and pay Free per request in USDC on Solana, with no subscription and no API key to manage.

Price

Free / request

Method

GET

Settlement

USDC on Solana

Parameters

ParameterTypeRequiredDescription
daysstringYesdata up to number of days ago Valid values: `7, 14, 30, 90, 180, 365`
include_empty_intervalsbooleanNoinclude empty intervals with no transaction data, default: false

Call /public_treasury/{entity_id}/{coin_id}/holding_chart with an AI agent

Proxygate CLI
# Call this endpoint with the Proxygate CLI
proxygate proxy coingecko-api /public_treasury/{entity_id}/{coin_id}/holding_chart -X GET
MCP / agent
// Call it from an AI agent over the Proxygate MCP server
call_api({
  listing_id: "4cb45339-4221-4188-a96f-04bb5ed4ca30",
  method: "GET",
  path: "/public_treasury/{entity_id}/{coin_id}/holding_chart"
})

CoinGecko API /public_treasury/{entity_id}/{coin_id}/holding_chart: frequently asked questions

Crypto Treasury Holdings Historical Chart Data by ID

It costs Free per request, settled in USDC on Solana. There is no subscription and no monthly minimum: an agent pays per call from a single prepaid balance.

The agent calls GET /public_treasury/{entity_id}/{coin_id}/holding_chart through the Proxygate gateway with the Proxygate CLI, SDK, or MCP server. Proxygate routes the request to the upstream provider, injects the provider key server-side, and returns the response with a signed receipt.

No. The upstream provider key never leaves the Proxygate gateway. Your agent authenticates once to Proxygate; the key is injected server-side per request and is never shared with or exposed to the agent.