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

# Currencyscoop CurrencyBeacon API

Jentic publishes the only available OpenAPI specification for CurrencyBeacon API, keeping it validated and agent-ready. CurrencyBeacon (formerly CurrencyScoop) exposes a REST interface for real-time and historical exchange rates covering more than 168 fiat currencies and over 2,000 cryptocurrencies. Rates are aggregated from commercial banks and exchange providers, with endpoints for live quotes, historical lookups, currency conversion, and time-series ranges. The API authenticates either by API key passed as a query parameter or by bearer token.

## For AI agents

Look up live and historical foreign-exchange rates, convert amounts between currencies, and retrieve time-series data for over 168 fiat currencies and 2,000 cryptocurrencies.

## Scope

Does not handle payment execution, currency hedging, or cross-border transfers - use for FX rate lookup and conversion only.

## Capabilities

- Retrieve the latest mid-market exchange rates against a base currency for fiat and crypto pairs
- Pull historical exchange rates for any specific date back through CurrencyBeacon's archive
- Convert a specified amount from one currency to another using current or historical rates
- Fetch time-series exchange rate data across a date range for charting or backtesting
- Enumerate the full list of supported fiat and cryptocurrency codes with their metadata

## Use cases

### Multi-Currency Checkout Pricing

Display localised prices in a customer's home currency at checkout by fetching live rates against a base currency. The /latest endpoint returns mid-market rates for over 168 currencies in a single call, so storefronts can refresh quotes once per session and convert SKU prices client-side. Suitable for low-volume conversion display where settlement still happens in a single base currency.

Example prompt: Call GET /latest with base=USD and symbols=EUR,GBP,JPY,INR and use the returned rates to render localised prices for a product priced at 49.99 USD

### Historical FX Reporting

Reconcile historical invoices, expenses, or accounting entries by retrieving the exchange rate that applied on a specific transaction date. The /historical endpoint accepts a date parameter and returns rates for all supported currencies, useful for finance teams generating multi-currency reports or auditors verifying booked FX values.

Example prompt: Call GET /historical with date=2024-06-15 and base=USD to retrieve the EUR/USD rate that applied on that day for an invoice reconciliation

### Crypto Portfolio Valuation

Value a portfolio that mixes fiat and cryptocurrency holdings by pulling current rates against a single accounting currency. CurrencyBeacon covers more than 2,000 cryptocurrencies alongside fiat, so a single /latest call can return BTC, ETH, and stablecoin rates plus the fiat side of the book.

Example prompt: Call GET /latest with base=USD and symbols=BTC,ETH,USDC,EUR,GBP and compute total portfolio value from holdings supplied by the user

### Time-Series FX Charting

Build line charts of exchange rate movement over a date range without scraping or storing historical data locally. The /timeseries endpoint returns a date-keyed object of rates between a start and end date, suitable for treasury dashboards or hedging analysis where teams need to see trend behaviour at a glance.

Example prompt: Call GET /timeseries with start_date=2025-01-01, end_date=2025-01-31, base=USD, symbols=EUR and return a daily rate series for plotting

### AI Agent FX Lookup via Jentic

An AI agent answering a question like 'how much is 500 euros in dollars?' uses Jentic to discover and execute the right CurrencyBeacon operation. The agent searches for 'convert currency', loads the /convert schema, supplies from, to, and amount, and returns the converted value without the developer wiring up CurrencyBeacon directly.

Example prompt: Use Jentic to search 'convert currency' and execute /convert with from=EUR, to=USD, amount=500 to answer a user question

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/latest` | Get latest exchange rates against a base currency |
| GET | `/historical` | Get exchange rates for a specific date |
| GET | `/convert` | Convert an amount between two currencies |
| GET | `/timeseries` | Get exchange rates across a date range |
| GET | `/currencies` | List supported fiat and cryptocurrency codes |

## Key resources

- **Exchange Rates** — Latest, historical, and time-series mid-market rates across fiat and crypto
- **Conversion** — Direct amount conversion between any two supported currencies
- **Currencies** — Catalogue of supported fiat currency and cryptocurrency codes

## Why Jentic

- **Setup:** Wiring this CurrencyBeacon API by hand means placing your API key in the query or a bearer token in the header, targeting the api.currencybeacon.com/v1 host, and handling retries around rate lookups yourself. Through Jentic you install once, import the API from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** This surface is read-only, with currencies, dates, and amounts passed as query parameters rather than an id in the URL path, so limit the agent to the operations it needs, such as latest rates or conversion. You choose which of those read operations are in scope.
- **Credential handling:** Your CurrencyBeacon API key or bearer token 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 'convert currency' or 'get a historical exchange rate', and Jentic returns the matching CurrencyBeacon operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **CurrencyAPI** — Similar live and historical FX coverage with a different free-tier ceiling
- **ExchangeRate-API** — Free fiat-only exchange rate API without crypto coverage
- **CurrencyFreaks API** — Live, historical, and convert endpoints across 180+ currencies

## FAQ

### Why is there no official OpenAPI spec for CurrencyBeacon API?

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

The API supports two methods: an API key supplied as the api_key query parameter, or a bearer token in the Authorization header. Through Jentic the credential is stored in the encrypted vault and injected at call time, so the raw key never enters the agent's prompt.

### Can I retrieve historical exchange rates with the CurrencyBeacon API?

Yes. Call GET /historical with a date parameter (YYYY-MM-DD) and an optional base and symbols list to retrieve the rates that applied on that date across all supported currencies.

### What are the rate limits for the CurrencyBeacon API?

Rate limits depend on the CurrencyBeacon plan tier and are enforced by the vendor; the spec does not encode exact numbers. Free plans typically permit a few thousand calls per month, while paid plans raise the ceiling. Check your CurrencyBeacon dashboard for the current quota.

### How do I convert an amount between two currencies through Jentic?

Run pip install jentic, then search for 'convert currency', load the /convert operation, and execute it with from, to, and amount parameters. Jentic returns the converted value and the rate used.

### Is the CurrencyBeacon API free?

CurrencyBeacon offers a free tier suitable for low-volume use and paid plans for higher request volumes, real-time updates, and full historical access. Pricing is set on the vendor's website.

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

Yes. Because you run Jentic One yourself, your own rules decide which CurrencyBeacon operations and credentials the agent may use. This surface is read-only and passes currencies, dates, and amounts as query parameters rather than in the URL path, so you can scope the agent to just the operations it needs, for example allowing GET /latest and GET /convert while excluding GET /historical or GET /timeseries. You choose which of those read operations stay in scope for a given agent.