Blog

The FX book

A shop that needs 99 dollars in yen does not buy a second vendor. Sugra Finance already has 151 official daily rates and convert on the same key as the quote.

ShareXLinkedInFacebookTelegramRedditEmailCopy linkMarkdown
The FX book: a single dark wooden shelf in amber light, coins in one row. Title reads The FX book, 151 official rates, already in the key.

You have a shop. A jacket is 99 dollars. A customer in Tbilisi, Tokyo or Tashkent wants that number in their currency before they pay.

This is a display problem. The market has trained you to solve it by buying a currency API: a second vendor, a second key, a second bill, for the privilege of printing a number next to a price.

If you already hold a Sugra key, you do not buy that product. The official daily book is a module of Sugra Finance, on the same key as the quote, in the seven-direction family. Convert reads that same book.

What a dedicated FX API costs

These four exist to sell you the book and nothing else:

What a dedicated FX API costs: Fixer, CurrencyLayer, Open Exchange Rates and ExchangeRate-API, free and paid plans as published on 2026-09-06

Prices as published on 2026-09-06. Reference only: specialised FX products. Sugra is not in the table because the book is not a SKU.

Sugra Free is 50 requests a day and already includes this book, plus the rest of the catalog. Sugra Pro is 59 dollars for 50,000 requests a day. Their 59 dollars buys the currency feed alone.

They update more often on paid plans. Ours is a daily official fix. For a storefront that needs to show yen, that is the right clock. For a payment you actually send, it is the wrong clock. The payload says so: basis is central-bank reference, not tradable.

One call, then convert

GET /api/v1/forex/rates?base=USD
curl -H "x-api-key: YOUR_API_KEY" \
  "https://sugra.ai/api/v1/forex\
/rates?base=USD"

Live on 2026-09-06: 151 ISO codes, one panel, as_of 2026-09-04. USD is 1.0. EUR is 0.8604. JPY is 156.2468. Georgian lari is 2.6159. Uzbek som is 11,795.62. The calendar was Saturday; the book is Friday. That is what a daily official print looks like. It is dated, not late.

The euro snapshot at /forex/latest is a different endpoint: EUR base, 29 codes. Leave it. This article is the shelf.

GET /api/v1/forex/convert
    ?from=USD&to=EUR&amount=99
curl -H "x-api-key: YOUR_API_KEY" \
  "https://sugra.ai/api/v1/forex\
/convert?from=USD&to=EUR\
&amount=99"
{
  "from_currency": "USD",
  "to_currency": "EUR",
  "amount": 99.0,
  "result": 85.18,
  "rate": 0.8604,
  "date": "2026-09-04",
  "basis": "central-bank reference, not tradable"
}

99 dollars is 85.18 euro on that fix, 15,468 yen, 258.97 lari, 1,167,766 som.

99 USD converted on the official book: 85.18 EUR, 15,468 JPY, 258.97 GEL, 1,167,766 UZS, as of 2026-09-04

Data: Sugra API - one request, nothing else: GET /api/v1/forex/convert?from=USD&to=EUR&amount=99.

The runnable copy is recipe 17 in the public cookbook: forex_shop_convert.py. Same envelope as CPI, as a 13F, as a weather point. Recipe 10 in that folder is the BIS long-run series versus the dollar, a different job.

Who this is for

A storefront that needs a price in the shopper’s currency.

A finance team that needs a second column on an invoice.

An agent that has to answer “what is 99 dollars in yen” from a named official print, not from a remembered number.

It is not for sending the payment. The bank that moves the money has its own rate, and that rate is a trade. This book is how you orient before you get there.

What is next

A faster official book, for a checkout that cannot wait for the daily fix. And a comparison of official cross-rates across central banks: the same pair printed two ways. Neither is in this endpoint today. Stay tuned.


Not a trade. Values pulled 2026-09-06 from sugra.ai. Book date 2026-09-04.

Previous: Sugra Finance. Family: seven directions, one key.

Integrate with one key across every product direction.

Get API keyDocsFamily