getCryptoPriceHistorical
Returns historical OHLCV candles for a cryptocurrency at a chosen interval and time range. Requires a symbol such as BTCUSD or ETHBTC. Symbols ending in USD are priced in real US dollars; other fiat quotes (e.g. BTCEUR) are not supported on this endpoint. For the live price use /cryptoprice.
This record as markdown: /tools/com-api-ninjas-mcp/getcryptopricehistorical.md
What getCryptoPriceHistorical does on API Ninjas
AI agents call getCryptoPriceHistorical to retrieve information from API Ninjas without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
end | integer | — | End timestamp in Unix seconds. Defaults to now. |
limit | integer | — | Maximum number of data points to return. Default 100, maximum 1000. |
start | integer | — | Start timestamp in Unix seconds. If omitted, the most recent `limit` data points are returned. |
symbol | string | Yes | Cryptocurrency symbol, e.g. BTCUSD (US dollars), ETHUSDT (Tether) or ETHBTC. USD and crypto quotes only. |
interval | string | — | Time interval between data points. Default is 1h. |
Parameters from the server's own tool schema.
Why getCryptoPriceHistorical is rated Low
Even though getCryptoPriceHistorical only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs getCryptoPriceHistorical safely
PolicyLayer is an MCP gateway: it sits between your AI agents and API Ninjas, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getCryptoPriceHistorical, this is the rule to start with:
getCryptoPriceHistorical is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect API Ninjas, apply this rule, and every getCryptoPriceHistorical call is checked against it from then on.
Questions about getCryptoPriceHistorical
Returns historical OHLCV candles for a cryptocurrency at a chosen interval and time range. Requires a symbol such as BTCUSD or ETHBTC. Symbols ending in USD are priced in real US dollars; other fiat quotes (e.g. BTCEUR) are not supported on this endpoint. For the live price use /cryptoprice. It is categorised as a Read tool in the API Ninjas MCP Server, which means it retrieves data without modifying state.
getCryptoPriceHistorical accepts 5 parameters: end, limit, start, symbol, interval. Required: symbol. The full parameter table on this page comes from the server's own tool schema.
Register the API Ninjas MCP server in PolicyLayer and add a rule for getCryptoPriceHistorical: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches API Ninjas. Nothing to install.
getCryptoPriceHistorical is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the getCryptoPriceHistorical rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for getCryptoPriceHistorical. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
getCryptoPriceHistorical is provided by the API Ninjas MCP server (https://mcp.api-ninjas.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on API Ninjas, and thousands of servers like it.
This server
Across the catalogue