canonical: https://jentic.com/apis/api.fxratesapi.com/fxratesapi # FxRatesAPI Jentic publishes the only available OpenAPI specification for FxRatesAPI, keeping it validated and agent-ready. FxRatesAPI delivers foreign exchange rate data covering 170+ currencies, including fiat, cryptocurrencies, and precious metals. The 5-endpoint REST API supports latest rates, historical rates by date, currency conversion between any two units, time-series across a date range, and a directory of supported currencies - the standard surface developers expect from an FX data provider, with crypto and metals included. ## For AI agents Fetch latest and historical foreign exchange rates, convert amounts between 170+ currencies including crypto and precious metals, and pull time-series rate data. ## Scope Does not handle FX trade execution, money transfer, or settlement - use for exchange rate data and currency conversion lookups only. ## Capabilities - Get the latest exchange rates for any base currency against 170+ targets - Pull historical exchange rates for a specific date - Convert an amount between any two supported currencies including crypto - Retrieve a time-series of rates between two dates for trend analysis - List the catalogue of supported currencies and their metadata ## Use cases ### Multi-Currency Pricing in Apps Show prices in a user's local currency in an e-commerce or SaaS app by fetching the latest rates against the merchant's base currency once per hour and applying the rate at display time. The /latest endpoint supports a base parameter and returns a full rates object, so the app caches one response per base currency rather than calling per conversion. Example prompt: GET /latest?base=USD to fetch the rates table, then compute display prices for EUR, GBP, and JPY shoppers from the cached response ### Reporting and Reconciliation in Local Books Reconcile cross-border transactions in local books by pulling the historical rate on the transaction date. The /historical endpoint accepts a date and base currency and returns the same rates table the system would have seen that day. Useful for monthly close, audit trails, and re-statement of foreign-currency invoices. Example prompt: GET /historical?date=2025-01-15&base=USD to retrieve the EUR rate on that date and value the original-currency invoice in the local books ### Crypto and Metals Tracking Track crypto and precious metal prices alongside fiat rates from a single API. The supported currency list includes BTC, ETH, XAU (gold), XAG (silver), and other commodities, queried through the same /latest, /historical, and /timeseries endpoints. Reduces the number of integrations a small fintech or treasury team needs to maintain. Example prompt: GET /timeseries?start_date=2025-05-01&end_date=2025-05-31&base=USD¤cies=BTC,XAU to chart crypto and gold against USD for May ### AI Agent Currency Conversion via Jentic An AI agent answering finance questions or building reports can call FxRatesAPI through Jentic to fetch live or historical rates without holding an API key itself. Jentic stores the api_key, exposes the five operations as discoverable tools, and returns the rate or converted amount the agent needs. Example prompt: Search Jentic for 'convert currency', load the GET /convert schema, and execute with from=GBP, to=JPY, amount=250 to return the converted value ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/latest` | Latest exchange rates for a base currency | | GET | `/historical` | Exchange rates on a specific date | | GET | `/convert` | Convert an amount between two currencies | | GET | `/timeseries` | Daily rates between two dates | | GET | `/currencies` | List supported currencies | ## Key resources - **Rates** — Latest, historical, and time-series exchange rates across 170+ currencies - **Conversion** — Convert an amount from one currency to another - **Currencies** — Directory of supported fiat, crypto, and metal currencies ## Why Jentic - **Setup:** Wiring FxRatesAPI by hand means passing its api_key as a query parameter on every call and coding your own reads of the latest, historical, and convert endpoints. Through Jentic you install once, import FxRatesAPI from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** FxRatesAPI parameters such as currency and date travel in the query string rather than as ids in the URL path, and every operation here is read-only, so limit the agent to the read operations it needs, such as latest or convert. Every operation you grant is your explicit choice. - **Credential handling:** Your FxRatesAPI key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'get the latest exchange rate' or 'convert between two currencies', and Jentic returns the matching FxRatesAPI operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **ExchangeRate-API** — Free-tier-friendly fiat exchange rate provider focused on simplicity - **CurrencyAPI** — FX rates provider with similar coverage of fiat, crypto, and metals - **Alpha Vantage** — Equities, options, and broader markets data that complements FX rate feeds ## FAQ ### Why is there no official OpenAPI spec for FxRatesAPI? FxRatesAPI does not publish a public OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call FxRatesAPI 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 FxRatesAPI use? FxRatesAPI uses an API key passed as the api_key query parameter. Through Jentic, the key is stored in the encrypted vault and appended to each request at execution time so it never appears in URLs the agent constructs. ### Does this API cover cryptocurrencies and precious metals? Yes. The /currencies endpoint enumerates the supported list, which includes BTC, ETH, XAU (gold), XAG (silver), and other commodities alongside fiat currencies. The same /latest, /historical, /convert, and /timeseries endpoints accept those tickers as base or target. ### How do I get the rate on a specific historical date? Call GET /historical?date=YYYY-MM-DD&base=XXX. The response is the same shape as /latest but returns the rates as of that date - useful for reconciling transactions in your local currency at the rate that applied on the transaction day. ### How do I convert an amount through Jentic? Run pip install jentic, then search 'convert currency'. Jentic returns the GET /convert operation with parameters from, to, and amount. Execute with the values you need; Jentic handles the api_key and returns the converted amount and the rate used. ### How fresh are the latest rates? FxRatesAPI updates fiat rates roughly every 60 seconds during market hours and crypto rates more frequently as the underlying exchanges report. Check the timestamp field on the /latest response to see the exact freshness for the rate you received. ### Can I limit what my agent is allowed to do with the FxRatesAPI? Yes. Because your Jentic One instance is self-hosted, you decide which of the five FxRatesAPI operations your agent may call, and every one you grant is your explicit choice. All FxRatesAPI endpoints are read-only and take parameters like currency and date in the query string, so you can grant just the reads the agent needs, such as /latest or /convert, and withhold /historical, /timeseries, or /currencies. Your rules govern which operations and credentials the agent uses, so it can never call an endpoint you did not allow.