canonical: https://jentic.com/apis/hirak.site/hirak-exchange-rates-api

# Hirak Site Hirak Exchange Rates API

Jentic publishes the only available OpenAPI specification for Hirak Exchange Rates API, keeping it validated and agent-ready. The Hirak Exchange Rates API delivers current, historical, and time-series foreign exchange rates plus cryptocurrency pairs through six GET endpoints, including a convenience /convert endpoint for direct currency conversion and a /fluctuation endpoint for measuring rate volatility over a window. The API is distributed via RapidAPI and authenticated with X-RapidAPI-Key and X-RapidAPI-Host headers. It is suitable for finance dashboards, e-commerce price localisation, and lightweight FX conversion in agent workflows where a free tier is acceptable.

## For AI agents

Fetch current, historical, and time-series foreign-exchange and crypto rates, and convert amounts between currencies. Authenticated via RapidAPI with X-RapidAPI-Key and X-RapidAPI-Host headers.

## Scope

Does not handle payment execution, settlement, or trade routing - use for foreign-exchange and crypto rate lookups and conversion only.

## Capabilities

- Retrieve the latest exchange rates against a base currency from /latest
- Pull historical rates for a specific date with /historical
- Convert an amount between two currencies in a single call to /convert
- List supported currency symbols, including major cryptocurrencies, via /symbols
- Build a time-series chart of rates between two dates with /timeseries
- Measure rate fluctuation between two dates using /fluctuation

## Use cases

### E-Commerce Price Localisation

Online stores show prices in the visitor's currency by converting a base price at request time. The Hirak Exchange Rates /convert endpoint takes a from, to, and amount and returns the converted value, so an agent can localise a product page without maintaining a daily rates job. Latency is acceptable for catalogue rendering.

Example prompt: For a basket of 49.99 USD, call GET /convert with from=USD, to=EUR, amount=49.99 and return the converted total.

### Treasury and Finance Dashboard

Finance teams build a small dashboard showing the current value of foreign cash balances. /latest and /timeseries together cover a current snapshot and a 30-day chart, so an agent can produce both a tile and a sparkline from a single API source without paying for an enterprise FX feed.

Example prompt: Fetch /latest with base=USD and /timeseries from 30 days ago to today for symbols=EUR,GBP,JPY and return both for a dashboard render.

### Crypto Conversion Helper

Apps that mention crypto values need a fast conversion from BTC or ETH into a fiat currency. The Hirak Exchange Rates API includes major cryptocurrencies in its symbols list, so /convert and /latest can return rates for crypto pairs alongside fiat without integrating a separate exchange API.

Example prompt: Convert 0.05 BTC to USD by calling GET /convert with from=BTC, to=USD, amount=0.05 and return the resulting value.

### AI Agent FX Quote Tool

An AI agent embedded in a chat product answers 'what is X in Y' questions for users. Through Jentic, the agent searches for the convert operation, loads the schema, and executes against Hirak with the user's RapidAPI key from the vault. The narrow surface keeps tool selection unambiguous.

Example prompt: When the user says 'how much is 250 GBP in USD', search Jentic for 'convert currency', load /convert, and execute with from=GBP, to=USD, amount=250.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/latest` | Get the latest exchange rates |
| GET | `/historical` | Get historical exchange rates for a date |
| GET | `/convert` | Convert an amount between two currencies |
| GET | `/symbols` | List supported currency symbols |
| GET | `/timeseries` | Get a multi-day rate time series |
| GET | `/fluctuation` | Get rate fluctuation between two dates |

## Key resources

- **Rates** — Latest and historical exchange rates for fiat and crypto pairs.
- **Conversion** — Direct amount conversion between two currencies.
- **Symbols** — List of supported currency and crypto symbols.
- **Time Series and Fluctuation** — Multi-day rate series and volatility metrics.

## Why Jentic

- **Setup:** Wiring the Hirak Exchange Rates API by hand means sending both an X-RapidAPI-Key and an X-RapidAPI-Host header on every request and deciding between the RapidAPI host and the direct rates.hirak.site host. Through Jentic you install once, import the Hirak Exchange Rates API from the API Directory, store the RapidAPI key once, and your agent calls it.
- **Permission scoping:** The Hirak Exchange Rates API is read-only and selects currencies and dates through query parameters rather than scopable path ids, so scoping stays at the operation level: limit the agent to the operations it needs, such as converting a currency or fetching latest rates. You choose that set, so a broader call like a timeseries or fluctuation lookup is only available if you include it.
- **Credential handling:** Your X-RapidAPI-Key and X-RapidAPI-Host values are stored once, encrypted, by your own Jentic One instance and injected as headers at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'convert currency', and Jentic returns the GET /convert operation with its query schema so the agent picks /convert, /latest, or /timeseries without reading the reference docs.

## Related APIs

- **APILayer API** — Multi-API marketplace including currency exchange APIs with stricter SLAs.
- **Abstract API** — Bundle of utility APIs including FX rates with per-key auth and predictable pricing.
- **Stripe API** — Payment processing platform that needs FX rates for multi-currency settlement reporting.

## FAQ

### Why is there no official OpenAPI spec for Hirak Exchange Rates API?

Hirak does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Hirak Exchange Rates 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 Hirak Exchange Rates API use?

Hirak Exchange Rates is distributed through RapidAPI, so calls require both the X-RapidAPI-Key and X-RapidAPI-Host headers. Through Jentic, both values are stored in your Jentic One instance and injected at execution time so the raw key never enters the agent context.

### Can I convert an amount between currencies in one call?

Yes. GET /convert accepts a from currency, to currency, and amount, and returns the converted value directly. This avoids a separate /latest fetch and a client-side multiplication step.

### What are the rate limits for the Hirak Exchange Rates API?

RapidAPI plan tiers govern throughput on this API; the spec itself does not declare rate limits. Check your RapidAPI subscription for monthly request quotas and add backoff for batch /timeseries jobs.

### How do I localise prices through Jentic?

Run pip install jentic, then await client.search('convert currency'), load the GET /convert schema, and execute it with from, to, and amount parameters per page render. Cache responses for low-volatility pairs to limit RapidAPI usage.

### Are cryptocurrencies supported alongside fiat?

Yes. The /symbols endpoint includes major cryptocurrencies as supported symbols, and /latest, /historical, /convert, and /timeseries accept those symbols as base or target currencies.

### Can I limit what my agent is allowed to do with the Hirak Exchange Rates API?

Yes. Because Jentic One is self-hosted, your own rules decide which of the six read-only GET operations the agent may call, so you can allow just /convert and /latest and leave /historical, /symbols, /timeseries, and /fluctuation out of reach. This API selects currencies and dates through query parameters rather than scopable path IDs, so control stays at the operation level: a broader timeseries or fluctuation lookup is available only if you include it. Your RapidAPI key and host are stored by your own instance and injected at execution time, so the agent can act on the operations you permit without ever seeing the raw credentials.