CurrencyFreaks API

Name: CurrencyFreaks API
Brand: CurrencyFreaks API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentData TransformationapiKey10 EndpointsREST

For Agents

Pull real-time and historical FX rates, convert currency, read fluctuation, and resolve currency by IP via CurrencyFreaks. Useful for AI agents that price internationally or analyse FX volatility.

Install Jentic One Beta

Connect the CurrencyFreaks API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the CurrencyFreaks 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# 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 instance

Jentic 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.

Capabilities

What an agent can do with CurrencyFreaks API.

List supported currencies and their symbols via /supported-currencies and /currency-symbols

Pull latest exchange rates for a base currency via /rates/latest

Look up historical rates for a date via /rates/historical

GET STARTED

Start building with CurrencyFreaks API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for CurrencyFreaks API, keeping it validated and agent-ready. CurrencyFreaks provides real-time and historical exchange-rate data for fiat currencies, metals, and cryptocurrencies, updated every minute. The API exposes ten endpoints covering supported currency listings, currency symbols, latest and historical rates, latest and historical conversion, time-series, fluctuation, IP-based currency detection, and historical data limits. Authentication uses the apikey query parameter, and responses are JSON with rates expressed against a chosen base currency.

Use Cases

Patterns agents use CurrencyFreaks API for, with concrete tasks.

★ Localised Pricing by IP

An agent serving an international audience can call /iptocurrency to detect a visitor's likely local currency, then call /rates/latest with the store's base to fetch the conversion factor. The combination produces locally priced product pages without asking the user to pick a currency manually, while still giving them the option to override.

Call GET /iptocurrency with the visitor IP, then GET /rates/latest with base=USD and the detected target currency to render local pricing.

FX Fluctuation Monitoring

A treasury or trading agent can monitor currency volatility using /fluctuation to retrieve change and percent-change between two dates across selected currencies. Combine with /timeseries for richer charts so finance teams can size hedging decisions.

Call GET /fluctuation with start_date, end_date, base, and symbols and alert when percent change exceeds a configured threshold.

Historical Audit Conversion

A finance agent can express past transactions in a reporting currency by calling /convert/historical with the transaction date. CurrencyFreaks caps historical depth by plan, so /historical-data-limits exposes the available range and lets the agent fail safely on out-of-range dates.

For each transaction, call GET /convert/historical with from, to, amount, and the transaction date, falling back to /convert/latest if the date is outside the plan's historical limit.

AI Agent Integration via Jentic

An AI assistant that handles FX can use Jentic to discover CurrencyFreaks rather than hard-coding the apikey query parameter. The agent searches for an intent like 'convert currency at the latest rate', loads the schema, and runs the call against credentials Jentic stores.

Use Jentic search for 'convert currency at the latest rate' and execute the matching GET /convert/latest operation.

Key Endpoints

10 endpoints — jentic publishes the only available openapi specification for currencyfreaks api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/rates/latest

Get latest exchange rates

GET

/rates/historical

Get historical exchange rates

GET

/convert/latest

Convert at latest rate

GET

/convert/historical

Convert at historical rate

GET

/timeseries

Get a time-series of rates

GET

/fluctuation

Get currency fluctuation data

GET

/iptocurrency

Detect currency from IP

GET

/supported-currencies

List supported currencies

GET

/rates/latest

Get latest exchange rates

GET

/rates/historical

Get historical exchange rates

GET

/convert/latest

Convert at latest rate

GET

/convert/historical

Convert at historical rate

GET

/timeseries

Get a time-series of rates

GET

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your CurrencyFreaks API 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.

Intent-based discovery

Agents search Jentic by intent such as 'convert currency at the latest rate' or 'detect currency from IP', and Jentic returns the matching CurrencyFreaks operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using CurrencyFreaks API through Jentic.

Why is there no official OpenAPI spec for CurrencyFreaks API?

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

CurrencyFreaks uses an API key passed as the apikey query parameter. Through Jentic the key is stored encrypted in your Jentic One instance and added to each request URL at execution time, so it never appears in agent prompts or logs.

Can I convert currency at a historical rate with CurrencyFreaks?

Yes. Call GET /convert/historical with from, to, amount, and date to get the converted value at the spot rate of that date. Use /historical-data-limits to confirm the date is within your plan's allowed history.

What are the rate limits for the CurrencyFreaks API?

Rate limits and historical depth depend on the plan tied to your apikey. The /historical-data-limits endpoint exposes the maximum back-date your plan can resolve, which is helpful for failing fast on out-of-range queries.

How do I detect a visitor's currency by IP through Jentic?

Run pip install jentic, search Jentic for 'detect currency from IP', load the schema for GET /iptocurrency, and execute it with the visitor IP. Jentic handles the apikey from your Jentic One instance and returns the resolved currency for use in localised pricing.

Does CurrencyFreaks support cryptocurrencies?

Yes. CurrencyFreaks covers fiat currencies, metals, and cryptocurrencies. Call GET /supported-currencies and GET /currency-symbols to retrieve the full list of fiat and crypto codes available on your plan.

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

Yes. Because you run Jentic One self-hosted, your own rules decide which CurrencyFreaks operations and credentials the agent may use. This surface is read-only, so you can scope the agent to just the endpoints it needs, such as GET /rates/latest, GET /convert/historical, or GET /iptocurrency, and leave the rest out of reach. The API key stays in your Jentic One instance and is injected only for the operations you have allowed.