Aumatex developer platform

Exchange rates,
fetched 48 times a day.
Served as often as you like.

auma.dev serves fiat, crypto and metal rates for 340+ currencies from an open dataset. A scheduled job pulls it every 30 minutes and stores a snapshot; your requests are answered from the edge and never reach the upstream. JSON over HTTPS, no keys, CORS on, documented in OpenAPI.

Read the docsopenapi.jsonllms.txt
request
curl https://auma.dev/v1/fx/latest?base=EUR&symbols=USD,GBP,CHF,BTC
response · live
{
  "base": "EUR",
  "date": "2026-11-02",
  "fetchedAt": "2026-11-02T20:00:18.959Z",
  "nextRefreshAt": "2026-11-02T20:30:18.959Z",
  "count": 4,
  "rates": {
    "USD": 1.11839108,
    "GBP": 0.83456265,
    "CHF": 0.92064628,
    "BTC": 0.000014293598
  }
}

Endpoints

/fx

Fiat, crypto and metal rates for 340+ currencies from the open fawazahmed0/currency-api dataset (CC0). auma.dev pulls it on a schedule — every 30 minutes, 48 times a day at most — and serves a snapshot; client requests never reach the upstream. Every response says when the snapshot was taken and when the next refresh is due.

/platform

Service metadata.

48 upstream contacts a day, not one more

The spacing and the daily cap are enforced in the store, whoever triggers a refresh; the schedule is just the trigger. /v1/fx/status shows every contact.

Cached, then forgotten

Every response carries Cache-Control and an ETag aligned with the next refresh, so the CDN answers repeats and clients get 304s. No accounts, no cookies, no analytics on the API.

One contract

The docs, openapi.json and llms.txt are generated from the same definition, so they cannot drift.

Coming next

More endpoints are on the way. Each one will land here with the same rules — no keys, cached at the edge, one contract — and will be announced in openapi.json before anywhere else.

Next endpointsoon
Next endpointsoon
Next endpointsoon