Currencytick API
★ Only Publicly Available OpenAPI DocumentFinanceBankingapiKey4 EndpointsREST
For Agents
Fetch live and historical foreign-exchange rates and list supported currency codes through a compact four-endpoint API.
Use for: I want to get the live rate for USD to EUR, Retrieve the historical EUR/GBP rate from 2024-03-15, List all currency codes Currencytick supports, Check whether the Currencytick API is currently available
Not supported: Does not handle currency conversion of amounts, payments, or hedging - use for live and historical FX rate lookup only.
Jentic publishes the only available OpenAPI specification for Currencytick API, keeping it validated and agent-ready. Currencytick is a foreign-exchange data service that delivers live and historical currency rates over a small, focused REST surface. The API exposes a healthcheck, a live rates endpoint, a historical rate lookup, and a supported-currencies listing, with authentication by API key passed as the apikey query parameter.
Install Jentic One Beta
Connect the Currencytick API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Currencytick 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.
1
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%2Fcurrencytick.com%2Fcurrencytick" | sh2
Step 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%2Fcurrencytick.com%2Fcurrencytick" | 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.
Capabilities
What an agent can do with Currencytick API.
Pull live mid-market exchange rates for a base currency against one or many target currencies
Retrieve historical exchange rates for a specified past date
Enumerate the full list of supported currency codes for validation and dropdowns
Verify API availability with the healthcheck endpoint before running a batch job
Use Cases
Patterns agents use Currencytick API for, with concrete tasks.
★ Lightweight FX Quote Display
Show a live exchange rate beside a price, balance, or invoice line item without integrating a heavy financial-data platform. Currencytick's /live endpoint returns rates in a single call against a base currency, suitable for product pages, dashboards, or notification systems where teams need a current rate but do not need streaming or sub-second updates.
Call GET /live with base=USD and target=EUR to display the current EUR price next to a 99 USD product
Historical Rate Lookup for Reconciliation
Look up the exchange rate that applied on a past date for accounting, expense reports, or invoice reconciliation. The /historical endpoint takes a date and base currency and returns the rates that were active, removing the need to maintain an in-house archive of FX history.
Call GET /historical with date=2024-12-31 and base=USD to retrieve the year-end EUR/USD rate for accounting close
Supported Currency Validation
Validate user-entered currency codes before submitting a conversion or quote request, by fetching the canonical list of supported currencies from /supported_currencies. Useful for multi-currency forms, finance back-office tools, and onboarding flows where teams need to gate user input.
Call GET /supported_currencies and check whether 'PLN' is present before allowing the user to submit a conversion request
AI Agent Currency Lookup via Jentic
An AI agent answering a natural language FX query uses Jentic to find the right Currencytick operation and execute it without bespoke integration work. The agent searches for 'live exchange rate', loads the /live schema, supplies base and target, and returns the rate to the user.
Use Jentic to search 'live exchange rate' and execute /live with base=USD and target=JPY to answer a user's rate query
Key Endpoints
4 endpoints — jentic publishes the only available openapi specification for currencytick api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/live
Get live exchange rates for a base currency
GET
/historical
Get historical exchange rates for a date
GET
/supported_currencies
List supported currency codes
GET
/healthcheck
Verify API availability
GET
/live
Get live exchange rates for a base currency
GET
/historical
Get historical exchange rates for a date
GET
/supported_currencies
List supported currency codes
GET
/healthcheck
Verify API availability
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Currencytick API by hand means appending the apikey query parameter to every request, targeting the api.currencytick.com host, and handling retries around rate lookups yourself. Through Jentic you install once, import the Currencytick API from the API Directory, store the API key once, and your agent calls it.
Permission scoping
This surface is read-only, with currencies and dates passed as query parameters rather than an id in the URL path, so limit the agent to the operations it needs, such as live or historical rate lookups. You choose which of those read operations are in scope.
Credential isolation
Your Currencytick 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 'live exchange rate' or 'historical currency rate', and Jentic returns the matching Currencytick operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Currencytick API through Jentic.
Why is there no official OpenAPI spec for Currencytick API?
Currencytick does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Currencytick 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 Currencytick API use?
The API uses an API key supplied as the apikey query parameter on every request. Through Jentic the key is held in the encrypted vault and injected at execution time, so the raw secret is never visible to the agent.
Can I get historical rates with the Currencytick API?
Yes. Call GET /historical with the desired past date and base currency to retrieve the rates that applied on that day for the supported target currencies.
What are the rate limits for the Currencytick API?
Rate limits depend on the Currencytick plan tier and are not encoded in the spec. Check your Currencytick account dashboard for the exact quota that applies to your key.
How do I look up a live exchange rate through Jentic?
Install the SDK with pip install jentic, search for 'live exchange rate', load the /live operation, and execute it with base and target query parameters. Jentic returns the rate without you handling the apikey directly.
How do I validate a currency code is supported?
Call GET /supported_currencies, which returns the full list of currency codes Currencytick can quote. Check membership in that list before issuing a /live or /historical request.
Can I limit what my agent is allowed to do with the Currencytick API?
Yes. Because you self-host Jentic One, your own rules decide which Currencytick operations the agent may call, and you can grant only the read endpoints it needs, such as GET /live for current rates or GET /historical for past-date rates, while leaving out /supported_currencies or /healthcheck. The whole surface is read-only, with base currency, target, and date passed as query parameters, so scoping to specific operations bounds exactly what the agent can look up. Your API key is stored by your own instance and injected at execution, so the agent calls only the operations you allow without ever seeing the secret.
GET STARTED