canonical: https://jentic.com/apis/amdoren.com/amdoren

# Amdoren Currency API

Jentic publishes the only available OpenAPI specification for Amdoren Currency API, keeping it validated and agent-ready. The Amdoren Currency API is a free currency conversion service supporting more than 150 fiat currencies. Its single GET endpoint returns the converted amount between a source and destination currency at the current exchange rate, authenticated by an api_key query parameter against www.amdoren.com/api. Typical consumers are budgeting apps, travel tools, e-commerce checkouts, and AI agents that need a low-friction conversion lookup without the overhead of a multi-endpoint FX provider.

## For AI agents

Lets agents convert an amount from one currency to another across 150+ supported currencies via a single GET /currency.php call with an api_key query parameter.

## Scope

Does not handle cryptocurrencies, historical FX time series, or money transfers - use for current-rate fiat conversions across 150+ currencies only.

## Capabilities

- Convert an amount between any two of 150+ supported fiat currencies in one call
- Retrieve the current exchange rate between two currencies as part of a conversion request
- Render localised price displays by converting a base price into the user's preferred currency
- Compute landed-cost estimates in a buyer's home currency at checkout
- Drive expense categorisation by converting foreign-currency receipts to a reporting currency

## Use cases

### Localised E-Commerce Pricing

International storefronts can show prices in the buyer's home currency by calling /currency.php with the catalogue currency, the buyer's currency, and the price. The single-endpoint surface keeps the integration cheap - most teams add it during checkout localisation work in an afternoon. Useful for low-volume merchants who do not need the broader feature set of Stripe FX or Wise.

Example prompt: Call GET /currency.php with from='USD', to='EUR', amount=49.99 and return the converted EUR amount as a string with two decimal places

### Travel and Budgeting Apps

Personal-finance and travel apps can offer a 'how much is this in my currency' feature without standing up a heavyweight FX integration. The single Amdoren endpoint covers the conversion math and returns enough detail (rate, converted amount) for the UI. The free tier suits low-volume hobby and indie apps.

Example prompt: Call GET /currency.php with from='GBP', to='THB', amount=20 and return the rate and converted amount for a travel-budget screen

### Expense Reporting Currency Normalisation

Finance teams importing foreign-currency receipts can normalise each line into a reporting currency by calling /currency.php once per receipt. Because the endpoint is a single GET, it slots cleanly into a row-by-row spreadsheet enrichment job with negligible operational complexity. Use a paid FX provider when historical rates are required.

Example prompt: For each row in an expense file, call GET /currency.php with from=row.currency, to='USD', amount=row.amount and append the converted USD value

### AI Agent Currency Math

Agents that handle bookings, quotes, or shopping baskets can pull current FX values through Jentic without storing raw api_key values. The agent searches Jentic for a conversion intent, loads the operation schema, and executes against a vault-held key. Useful for travel planners and shopping copilots that span currencies inside a single conversation.

Example prompt: Search Jentic for 'convert currency', execute the operation backed by GET /currency.php with from='EUR', to='USD', amount=250, and return the result rounded to two decimals

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /currency.php | Convert an amount between two currencies |

## Key resources

- **Currency** — Convert an amount between two currencies and return the rate and converted value

## Why Jentic

- **Setup:** Wiring the Amdoren Currency API by hand means appending the api_key to the query string on every call and parsing its single currency.php endpoint yourself. Through Jentic you install once, import Amdoren from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** Amdoren exposes a single currency-conversion endpoint that takes the currency codes as query parameters, so scope the agent to that one operation. You choose the operations it may call, so nothing beyond the conversion lookup runs unless you add it.
- **Credential handling:** Your Amdoren api_key is stored once, encrypted, by your own Jentic One instance and injected at execution time, so it stays out of the query string the agent sees. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'convert an amount between currencies' or 'get an exchange rate', and Jentic returns the matching Amdoren operation with its input schema so the agent calls the right endpoint without parsing the reference docs.

## Related APIs

- **ExchangeRate-API** — Free and paid FX rate API with historical and time-series endpoints alongside conversion
- **CurrencyAPI** — Modern FX API with historical, time-series, and currency metadata endpoints
- **CurrencyBeacon** — FX API with conversion, historical, and time-series endpoints across 150+ currencies
- **Abstract API** — IP-geolocation and currency endpoints to detect a user's home currency before conversion

## FAQ

### Why is there no official OpenAPI spec for Amdoren Currency API?

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

Amdoren uses an API key passed as the api_key query parameter on the /currency.php request. There is no header-based scheme or OAuth flow. Through Jentic, the api_key is stored encrypted in the vault and injected at execution time so the agent never sees the raw key.

### Can I convert any pair of currencies with the Amdoren Currency API?

Yes for the 150+ fiat currencies Amdoren supports. The single GET /currency.php endpoint accepts ISO 4217 codes for both the source (from) and destination (to) currency plus a numeric amount, and returns the converted value at the current rate. Cryptocurrencies are not in scope.

### What are the rate limits for the Amdoren Currency API?

Amdoren's free tier allows a few hundred calls per day per api_key, with paid tiers raising the cap. The spec does not enumerate the exact ceiling. Throttle bulk jobs to one request per second and back off on HTTP 429 to stay safe across tiers.

### How do I convert currency through Jentic?

Search Jentic for 'convert currency' or 'get exchange rate'. Jentic returns the operation backed by GET /currency.php, you load the schema (from, to, amount), and execute. Jentic injects the api_key from the vault. Run it through Jentic One, the self-hosted execution layer.

### Does the Amdoren Currency API include historical rates?

No. The single endpoint returns only the current rate for the requested pair. For historical FX data pair this with a provider that exposes time-series endpoints (Open Exchange Rates, exchangerate-api, currencybeacon).

### Can I limit what my agent is allowed to do with the Amdoren Currency API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, and the Amdoren Currency API exposes a single currency-conversion operation (GET /currency.php) that takes the source and destination currency codes plus an amount as query parameters. You scope the agent to just that conversion lookup, so nothing beyond it runs unless you add it. Your Amdoren api_key is held by your own instance and injected at execution time, so the agent never handles the raw key.