Docs/Sources/Exchange Rate Grounding Data

Exchange Rate Grounding Data

Get exchange rate between two currencies

OperationalCredits 2 per callp50 233msFinance

Overview

A currency rate API in one call: pass two currency codes as parameters to receive the current conversion multiplier and an ISO 8601 timestamp showing when the rate refreshed. The response covers over 170 currencies in real time. Paid plans also return the inverse rate for reverse conversions without a second call.

Live Test Exchange Rate Grounding Data Source →

The tool

Once your client is connected to the VerveContext server, this appears in its tool list as ExchangeRateGroundingData. It is read-only and open-world — it fetches and never mutates anything on your side — so most clients call it without asking you to confirm.

Tool call
{
  "name": "ExchangeRateGroundingData",
  "arguments": {
    "currency1": "USD",
    "currency2": "EUR"
  }
}

You do not name the tool yourself; the model picks it. Asking about USD in the terms this source covers is enough for it to reach for ExchangeRateGroundingData on its own — naming it explicitly also works, and is the way to force the call.

Connecting

One server URL covers every source in the catalog, including this one. Authorization is OAuth: the client opens a browser once, and there is no key to paste into a config file.

{
  "mcpServers": {
    "vervecontext": {
      "url": "https://api.vervecontext.com/v1/mcp"
    }
  }
}

Per-client setup — Claude, Cursor, VS Code, ChatGPT — is on the MCP setup page.

Arguments

These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made. Premium arguments are accepted on every plan but only take effect on plans that include them.

ArgumentTypeDescription
currency1RequiredstringThe first currency you want to get the exchange rate for
currency2RequiredstringThe second currency you want to get the exchange rate for

What the model gets back

The result carries a structuredContent object matching the tool's declared outputSchema, so a client reads fields without parsing prose. status is "ok" and error is null on success; a null field means the value was not available for that input, not that the call failed.

Result
{
  "status": "ok",
  "error": null,
  "data": {
    "currency1": "USD",
    "currency2": "EUR",
    "exchangeRate": "0.866664",
    "inverseRate": "1.153850",
    "lastUpdated": "2026-09-16T02:00:27.378Z"
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

FieldTypeExampleDescription
currency1stringUSDThe first currency code requested for exchange rate
currency2stringEURThe second currency code requested for exchange rate
exchangeRatestring0.866664The current exchange rate from currency1 to currency2
inverseRatePremiumstring1.153850The inverse exchange rate from currency2 to currency1
lastUpdatedstring2026-09-16T02:00:27.378ZISO 8601 timestamp of when the exchange rates were last refreshed

Why ground on it

A model can produce something that looks like this answer from its training data, and be confidently out of date or simply wrong. This source returns the current value in a shape you can check, which is the difference between an answer you can cite and one you have to hedge.

Point an evaluation at exchangeRate: it is the field most worth pinning a claim to, and it is either present and current or absent — never plausibly invented.

Failure modes

Errors come back as tool errors carrying a sentence the model can act on, not a bare status code. Error handling covers the full list.

StatusWhat it means
400 / 422The arguments did not validate. The message names the offending one.
401The OAuth session is invalid or expired — reconnect the server.
403Blocked by a key restriction or an IP allow-list. Never a bad identity.
404This source is not part of VerveContext. Check the catalog.
429Out of credits, or a brief rate limit. The message tells them apart.

A call costs 2 credits each time the tool actually runs; a model that reasons about the tool without calling it costs nothing.

Use cases

Multi-Currency Checkout
Convert product catalog totals into a buyer's local currency at payment time so shoppers review exact prices before charging their cards.
Cross-Border Invoicing
When billing foreign clients, SaaS platforms convert base subscription fees into regional currencies to generate accurate invoices.
Travel Booking Conversion
Travel booking engines convert hotel and flight rates into the traveler's home currency so customers can compare international costs.
Remittance Payout Preview
To eliminate foreign exchange surprises, fintech apps display the converted payout amount before a user confirms an international wire.

Other ways to use Exchange Rate Grounding Data

Set up Exchange Rate Grounding Data on VerveContext, or reach the same source a different way. Your VerveContext account and credits work on all of them — one key, one balance.

Call it as a REST APIOne HTTPS endpoint and an x-api-key header, with SDKs for Node, Python and .NET.APIVerve →Reference →
Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.VerveKit →Reference →
Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheets →Reference →

More in Finance:

Was this page helpful?