Exchange Rate API is now part of AllRatesToday — your API key keeps working 🤝

[cahthuranag]

TL;DR: Exchange Rate API and AllRatesToday are now one service. Nothing breaks for existing users — keys, endpoints, dashboards, and plans all keep working unchanged.

What did NOT change

• Your era_live_ API key keeps working against https://exchange-rateapi.com/api/... indefinitely.
• Your dashboard remains at exchange-rateapi.com/dashboard.
• Your plan, limits and billing are untouched.
• Same data: mid-market rates from Reuters/Refinitiv, 160+ currencies, updated every 60 seconds.

What changed

• The exchange-rateapi.com website (docs, guides, blog) now lives at allratestoday.com.
• New features ship on AllRatesToday first: official SDKs for JavaScript, Python, PHP and Rust, an MCP server for AI assistants, and historical time-series endpoints.

Want the newer API surface?

Sign up free at allratestoday.com/register — 300 requests/month, real-time rates, no credit card. Details: allratestoday.com/free-currency-api

Questions? Ask below 👇

[richardchen874-sys]

The Exchange Rate API is now part of AllRatesToday — your API key keeps working 🤝 is the first metric layer I would make trustworthy, because cost optimization only works after attribution is credible.

A useful shape would be one usage event per model call, with provider/model, feature name, token fields, retry count, latency, and billing bucket all attached. Then cost can be traced back to product behavior instead of guessed from invoices.

I am testing a multi-model OpenAI-compatible API layer around official Chinese models, so the routing and usage-accounting parts of this are directly relevant to me. In this case, is the main pain attribution by user/workspace, or just understanding which agent steps are consuming the most tokens?