Reference & Lookup Data · Integration
Currency Exchange
Add Currency Exchange to your product for your customers, and give your AI agents governed access to it.
Embed a Currency Exchange integration so your product can read the exchange rate data your customers rely on without you maintaining another API client. Each customer's credentials are held and scoped per tenant, so usage is attributable and one customer's reads never draw on another's allowance. fastn handles the authentication, pagination, and API upkeep, so a provider change lands in the connector rather than in your release.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers read current exchange rates into your product so amounts display in their own currency.
Read historical rates so your product can value a past transaction at the rate that applied then.
Convert amounts between currencies inside a workflow instead of hard-coding a rate table.
Refresh rates on a schedule so your product is not making decisions on a stale figure.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads the current rate before answering a question about a converted amount.
An agent pulls historical rates to explain a period-over-period difference.
An agent refreshes rates on a schedule and reports a notable movement.
Example prompt
Convert these amounts to euros at today's rate and show what the same conversion would have been a year ago.
Set up Currency Exchange in 4 steps
- 01Open the Currency Exchange connector from your fastn dashboard.
- 02Have each customer authenticate with their own API credentials.
- 03Map the currencies and fields your product uses, then enable the actions you need.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Currency Exchange integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Currency Exchange integration without building it. Your customers connect their own Currency Exchange account inside your product and work their lookups, results and reports there, with no per-customer code on your side.
- Handle the part that actually costs time: these are metered read sources, so an uncached lookup on every page view burns the customer's allowance. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Currency Exchange update is not your on-call problem.
- One integration serves your product and your agents. The same governed Currency Exchange connection powers in-product features and gives AI agents scoped, audited access, so you answer questions from an authoritative outside source without holding that data yourself without wiring it twice.
Used by these teams
Compare with
Weather API
Companies HouseOften used alongside
Tools the same teams tend to run next to Currency Exchange, across other categories.
Salesforce
HubSpot
Notion
SnowflakeCurrency Exchange integration FAQ
How do I add a Currency Exchange integration to my product?
Enable the Currency Exchange connector in your fastn dashboard, then let each customer authenticate their own Currency Exchange account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Currency Exchange client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Currency Exchange account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Currency Exchange account and only ever sees their own lookups, results and reports. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Currency Exchange integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reads the current rate before answering a question about a converted amount.
Who maintains the Currency Exchange integration?
fastn does. When Currency Exchange changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Whose credentials does a Currency Exchange lookup run under?
Each customer's own. Quota and cost land on the customer that caused them rather than on a shared key you have to meter and re-bill, and one heavy customer cannot exhaust another's allowance.
How should Currency Exchange results be cached?
Per tenant, with a window that matches how fast the underlying data actually moves. Currency Exchange is a read source rather than a system of record, so the same query returns the same answer until the source changes, and caching is the difference between a sustainable integration and one that exhausts a customer's allowance on a busy page.
What can I build with the Currency Exchange integration?
A common starting point: read current exchange rates into your product so amounts display in their own currency. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Currency Exchange integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Currency Exchange does not change your per-connector cost. You can start free with 3 connected accounts.
Add Currency Exchange to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.