For Agents
Fetch live and historical FX rates for 170+ currencies, convert an amount between two currencies, and check your plan usage. Returns JSON keyed by ISO currency code.
Use for: I need to get today's exchange rate for EUR against USD, Convert 250 USD to GBP at the current rate, Retrieve historical exchange rates for 2023-01-15, List all supported currency codes
Not supported: Does not handle payments, money transfers, or stock market data. Use for currency exchange rate data only.
The Open Exchange Rates API returns real-time and historical foreign exchange rates for more than 170 currencies, published against a USD base. It serves spot rates from the latest feed, dated historical rates, time-series ranges between two dates, and a direct value conversion between any two currency codes. A currencies listing supplies the full set of supported codes and names, and a usage endpoint reports the calls remaining on your plan.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Open Exchange Rates 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.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fopenexchangerates.org%2Fopenexchangerates" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fopenexchangerates.org%2Fopenexchangerates" | 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 Open Exchange Rates API.
Retrieve the latest exchange rates for 170+ currencies against a USD or custom base
Look up historical exchange rates for any past date
Pull a time series of daily rates between a start and end date
Convert a specific amount from one currency code to another
List every supported currency code and read remaining calls on your plan
Patterns agents use Open Exchange Rates API for, with concrete tasks.
★ AI Agent Currency Conversion
An AI agent handling invoices or quotes can convert amounts between currencies on demand through Jentic. The agent supplies the amount and the source and target currency codes, then receives the converted value computed from current rates, without the developer wiring the App ID or parsing the rates feed by hand.
Call GET /convert/{value}/{from}/{to} to convert 100 USD to EUR and return the converted amount
Multi-Currency Pricing
Online stores and SaaS billing systems localize prices by reading the latest rates and applying them to a base currency. The latest-rates feed returns every supported currency against a chosen base, so a pricing service can refresh its conversion table on a schedule and display local prices to each customer.
Call GET /latest.json with base set to EUR and read the USD and GBP rates for a pricing table
Historical Rate Analysis
Finance and reporting tools reconcile past transactions at the rate that applied on the transaction date. The historical endpoint returns rates for a specific day, and the time-series endpoint returns a range, so an agent can rebuild the exact conversion used on any date or chart how a currency moved over a period.
Call GET /historical/2024-03-01.json with symbols set to EUR,GBP to read the rates for that date
6 endpoints — the open exchange rates api returns real-time and historical foreign exchange rates for more than 170 currencies, published against a usd base.
METHOD
PATH
DESCRIPTION
/latest.json
Latest exchange rates for all or specified currencies
/historical/{date}.json
Historical exchange rates for a specific date
/time-series.json
Exchange rates across a date range
/convert/{value}/{from}/{to}
Convert a value between two currencies
/currencies.json
List supported currency codes and names
/usage.json
Plan usage statistics for your App ID
/latest.json
Latest exchange rates for all or specified currencies
/historical/{date}.json
Historical exchange rates for a specific date
/time-series.json
Exchange rates across a date range
/convert/{value}/{from}/{to}
Convert a value between two currencies
/currencies.json
List supported currency codes and names
/usage.json
Plan usage statistics for your App ID
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Open Exchange Rates API by hand means passing your App ID as a query parameter on every call, choosing a base currency, and parsing the rates feed yourself. Through Jentic you install once, import Open Exchange Rates from the API Directory, store the App ID once, and your agent calls it.
Permission scoping
This API is read-only, so a rule can bound your agent to the specific rate lookups it needs, such as the latest-rates and conversion operations, and exclude the rest. You choose the operation set, so the agent can read rates but cannot reach anything you did not grant.
Credential isolation
Your App ID 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.
Intent-based discovery
Agents search Jentic by intent such as 'convert USD to EUR' or 'get historical exchange rates', and Jentic returns the matching Open Exchange Rates operation with its input schema so the agent calls the right endpoint without reading the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Open Exchange Rates API through Jentic.
What authentication does the Open Exchange Rates API use?
The Open Exchange Rates API authenticates with an App ID passed as the `app_id` query parameter on every request, per its OpenAPI spec. Through Jentic the App ID is stored encrypted by your own Jentic One instance and injected when a call runs, so it never appears in the agent's prompt or logs.
Can I convert between two currencies with the Open Exchange Rates API?
Yes. The conversion operation takes an amount and a source and target currency code in the URL path and returns the converted value computed from current rates. You can also read the latest or historical rates and apply them yourself for bulk conversions.
What are the rate limits for the Open Exchange Rates API?
The OpenAPI spec does not specify rate limits; your request allowance depends on your subscription plan. The usage operation reports the calls remaining on your plan, and current limits are listed in the vendor documentation at https://docs.openexchangerates.org/.
How do I fetch exchange rates with the Open Exchange Rates API through Jentic?
Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, import Open Exchange Rates from the API Directory, and store your App ID once. Your agent then searches for an intent such as 'get the latest exchange rates', and Jentic returns the matching operation with its input schema. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Is there an Open Exchange Rates MCP server?
You do not need an MCP server to give your agent the Open Exchange Rates API. Jentic connects it directly from the API Directory: import the API, store your App ID once, and your agent calls the rate and conversion operations on demand. That keeps your agent's context free of an extra server's tool definitions.
Can I limit what my agent is allowed to do with the Open Exchange Rates API?
Yes. Every operation in this API is a read, so you can allow just the ones the agent needs, such as reading the latest rates and converting a value, while leaving out the currencies listing or the plan-usage endpoint. Because you run Jentic One yourself, the agent holds no access beyond the read operations you grant, and every call it makes is logged.
GET STARTED