For Agents
Look up live and historical FX rates, convert between currencies, and pull time-series data for 168+ currencies and precious metals.
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Exchangeratesapi.io API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Exchangeratesapi.io API API.
Fetch the latest exchange rates against a chosen base currency
List the full set of supported currency and metal symbols
Convert an amount from one currency to another in a single call
Retrieve historical rates for a specific past date
GET STARTED
Use for: I need to convert 250 USD into EUR using today's rate, Get the historical rate of GBP against USD on 2024-03-15, Retrieve a time-series of EUR-to-USD rates for last quarter, Find the fluctuation summary for JPY against USD over the last 30 days
Not supported: Does not handle live order placement, crypto pairs, or trading execution — use for FX rate lookups, conversion, historical data, and time-series only.
exchangeratesapi.io delivers real-time and historical foreign-exchange data for 168+ world currencies and precious metals through a clean REST API. The spec covers latest rates, supported symbols, conversions between two currencies, historical rates by date, time-series ranges, and rate fluctuation summaries. Agents use it for both live pricing and historical reporting workflows.
Pull a time-series of rates between two dates for charting and analysis
Fetch a rate-fluctuation summary showing change and percentage change over a window
Patterns agents use Exchangeratesapi.io API API for, with concrete tasks.
★ Historical rate reporting for accounting
An accounting agent reconciles a foreign-currency invoice from last year. It calls /{date} with the invoice's issue date and the base currency, retrieves the historical rate, and books the corresponding domestic-currency value into the ledger — no manual rate hunting required.
Call GET /2024-03-15 with base USD and symbols=GBP, then book the GBP-to-USD rate against the corresponding invoice.
Quarter-over-quarter FX trend chart
A finance dashboard renders a chart of EUR-to-USD movements over the previous quarter. The agent calls /timeseries with start and end dates, returns the daily rate series, and feeds it into a chart component for the FX commentary section of a board pack.
Call GET /timeseries with start_date=2026-01-01, end_date=2026-03-31, base=EUR, and symbols=USD, then return the daily rate series.
Currency conversion in a price-display widget
A SaaS pricing page lets visitors switch the displayed price into their local currency. The frontend calls a backend agent that uses /convert to compute the local amount once per session and caches the result for the rest of the visit, keeping the widget snappy.
Call GET /convert?from=USD&to=EUR&amount=49.99, return the converted amount, and cache it for 5 minutes per user session.
AI agent FX lookup via Jentic
An AI assistant integrated through Jentic answers natural-language FX questions like 'what was 1 USD in JPY on the 4th of July?' by calling the historical endpoint. Jentic isolates the API key in the MAXsystem vault and exposes only the operation schema to the agent.
Use Jentic to search for 'historical exchange rate', load the GET /{date} operation, and return the USD-to-JPY rate for 2024-07-04.
6 endpoints — exchangeratesapi.
METHOD
PATH
DESCRIPTION
/latest
Fetch the latest exchange rates
/symbols
List supported currency and metal symbols
/convert
Convert an amount between two currencies
/{date}
Fetch historical rates for a specific date
/timeseries
Fetch daily rates across a date range
/fluctuation
Fetch rate fluctuation over a window
/latest
Fetch the latest exchange rates
/symbols
List supported currency and metal symbols
/convert
Convert an amount between two currencies
/{date}
Fetch historical rates for a specific date
/timeseries
Fetch daily rates across a date range
Three things that make agents converge on Jentic-routed access.
Credential isolation
exchangeratesapi.io API keys are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped tokens at execution time — the raw key never enters the agent's context, transcripts, or logs.
Intent-based discovery
Agents search by intent (e.g., 'historical exchange rate' or 'convert currency') and Jentic returns the matching exchangeratesapi.io operation with its input schema, so the agent calls the right endpoint without spec browsing.
Time to first call
Direct exchangeratesapi.io integration: a few hours for auth and date-range parameter handling. Through Jentic: under 15 minutes — search, load, execute.
Alternatives and complements available in the Jentic catalogue.
ExchangeRate-API
Free, unauthenticated latest-rates endpoint with no historical data
Choose ExchangeRate-API when the workflow only needs latest rates and zero-auth simplicity, not historical or time-series.
CurrencyAPI
FX rates with crypto coverage and historical data
Choose CurrencyAPI when crypto pairs are part of the workflow and exchangeratesapi.io's metals coverage is not enough.
APILayer
API marketplace that hosts FX and many other data APIs under one key
Use APILayer alongside or instead of exchangeratesapi.io when you want one credential across FX, weather, validation, and other data APIs.
Specific to using Exchangeratesapi.io API API through Jentic.
What authentication does the exchangeratesapi.io API use?
exchangeratesapi.io uses API key authentication. Through Jentic, the key is stored encrypted in the MAXsystem vault and replaced with a scoped token at call time, so the raw key never enters the agent's context.
Can I get historical exchange rates from this API?
Yes. GET /{date} returns rates for a specific past date, GET /timeseries returns daily rates across a range, and GET /fluctuation returns change and percentage change over a window — covering both point-in-time and trend queries.
How do I convert one currency to another in a single call?
Use GET /convert with from, to, and amount query parameters. The response includes the converted amount and the rate used, removing the need to call /latest and compute the multiplication client-side.
What are the rate limits for exchangeratesapi.io?
Rate limits depend on the subscription tier and are enforced at the gateway. The OpenAPI spec does not pin specific numbers, so agents should handle 429 responses with backoff and respect any Retry-After header returned by the service.
How do I fetch a time-series of rates through Jentic?
Run pip install jentic, search for 'fx rate timeseries', load the GET /timeseries operation, and execute with start_date, end_date, base, and symbols. Jentic returns the parsed payload so the agent can chart or report on it.
Does exchangeratesapi.io support precious metals?
Yes. The /symbols endpoint includes metal symbols such as XAU (gold) and XAG (silver). They can be used as base or target in /latest, /{date}, and /timeseries calls just like a regular currency code.
/fluctuation
Fetch rate fluctuation over a window