Risk-free rate differentials sit at the center of carry, hedging costs, and relative-value FX trades, but they are not one globally uniform series. In one currency you may be looking at a true overnight benchmark such as SOFR or EURSTR. In another, the most useful short-end signal may be an interbank fix, a bill-rate proxy, or a rate that still sits close to the local policy framework. FXMacroData keeps the access pattern simple while making it easier to understand those structural differences before they distort a cross-currency comparison.
The key idea
FXMacroData standardizes the field name risk_free_rate so your workflow is consistent across currencies,
but the underlying short-end rate structure still matters. The cleanest FX analysis starts by comparing like with like.
Why this matters in FX
Traders often compress rate differentials into one headline view: the higher-yielding currency should outperform, the lower-yielding currency should lag. That framing is directionally useful, but it can break down fast if the underlying rates are drawn from different parts of the curve or different policy frameworks.
If you compare an overnight benchmark in one country with a term interbank proxy in another, you are no longer measuring the same economic object. You are blending monetary implementation, funding structure, and local market conventions into one number. That is why FXMacroData pairs standardized endpoint design with currency-specific docs such as USD risk_free_rate, EUR risk_free_rate, and SGD risk_free_rate.
The practical payoff is simple: you can move quickly across currencies without flattening away the differences that matter for carry screens, funding comparisons, and event-driven FX dashboards.
A good comparison framework
- Benchmark vs benchmark: SOFR, EURSTR, SONIA, SARON, SORA, and NOWA belong in the cleanest cross-market set.
- Proxy vs proxy: bank-bill and interbank series can still be extremely useful, but they should be compared with care.
- Policy vs funding: policy_rate and
risk_free_rateanswer different questions, even when both feed the carry story.
The four structures you will see most often
| Structure | What it captures | Best use | Typical examples |
|---|---|---|---|
| Overnight benchmark | Observed overnight funding conditions with minimal policy smoothing. | Clean carry comparisons and short-end relative-value work. | USD SOFR, EUR EURSTR, GBP SONIA, CHF SARON, SGD SORA, NOK NOWA |
| Short-end proxy | Term or interbank rates that stand in for the local funding picture when a clean overnight benchmark is less useful or less established. | Practical country coverage in screens, models, and relative ranking. | AUD interbank cash proxy, NZD 90-day bank bills, MXN TIIE 28-day, HKD 1M HIBOR, CAD short-end cash proxy |
| Operational daily rate | A daily operating rate that sits close to the way the local central bank implements policy. | Monitoring local liquidity conditions and policy transmission. | BRL CDI Over, CNY 7-day reverse repo, SEK Swedish overnight benchmark |
| Policy-linked hybrid | A short-end series where regime design and policy framework matter almost as much as the label itself. | Situations where interpretation should stay tied to the local monetary regime. | JPY and some linked-system or framework-sensitive currencies |
How to think about the major currency groups
The easiest way to use the endpoint is to group currencies by the structure they represent, not just by the shared field name. That lets you decide which pairs belong in the same screen, which spreads are genuinely comparable, and where a little extra interpretation is worth the effort.
1. The clean benchmark set
This is the strongest starting point for cross-currency carry work. These rates sit close to observable overnight funding conditions, so the comparison is much closer to apples-to-apples.
- USD: SOFR gives you a short-end funding benchmark that stays distinct from the Fed's decision-driven policy_rate.
- EUR: EURSTR is the right comparison object for euro overnight conditions rather than a simple restatement of ECB policy settings.
- GBP and CHF: SONIA and SARON keep sterling and Swiss franc analysis in the benchmark family as well.
- SGD and NOK: SORA and NOWA make both currencies useful additions when you want a broader benchmark-style carry basket.
2. The proxy set
Some currencies are better represented by a liquid short-end proxy than by a clean overnight benchmark. These series are still highly useful, especially for ranking relative funding conditions, but they deserve a little more context.
- AUD and CAD: both are best treated as cash-market proxy cases rather than simple copies of the policy target.
- NZD: the 90-day bank bill structure remains useful for carry work, but it is not the same object as SOFR or EURSTR.
- MXN: TIIE 28-day is central to Mexican funding conditions and still matters greatly for FX, even though it lives in a term bucket.
- HKD: 1-month HIBOR is practical and relevant, but interpretation should stay anchored to the linked exchange-rate system.
3. Operational daily rates
A few currencies sit closer to daily policy implementation than to a clean market benchmark. These are still valuable series, but the interpretation is often more about liquidity management and transmission than about a pure market clearing rate.
- BRL: CDI Over remains a core rate for Brazilian funding and local market pricing.
- CNY: the 7-day reverse repo rate carries clear monetary-operations information alongside its funding signal.
- SEK: Sweden fits the daily-rate family better than the sparse policy-event family, which changes how it should be monitored in dashboards.
4. Hybrid cases where regime detail matters
Some currencies need a little more care because the monetary regime shapes the interpretation as much as the rate label itself.
- JPY: Japan is a reminder that a rate can look simple on paper while still requiring policy-context awareness in practice.
- HKD: Hong Kong combines a practical funding proxy with a regime that is inseparable from the USD peg and HKMA framework.
How FXMacroData helps you use the distinction
The value of the platform is not just that you can request a rate. It is that you can move from idea to implementation without losing the economic context behind the series.
The uniform endpoint pattern keeps code clean:
https://fxmacrodata.com/api/v1/announcements/{currency}/risk_free_rate?api_key=YOUR_API_KEYThe currency-specific docs then tell you what sits behind that path, so your dashboard logic, alerts, and model inputs stay disciplined rather than generic. That is especially useful when you pair funding metrics with event-driven indicators such as inflation, non_farm_payrolls, or policy_rate.
risk_free_rate or policy_rate on purpose. They are related, but they are not interchangeable.
A practical workflow
If you want the daily funding side of carry, start with currencies that belong to the same structural family. For example:
curl "https://fxmacrodata.com/api/v1/announcements/usd/risk_free_rate?api_key=YOUR_API_KEY"
curl "https://fxmacrodata.com/api/v1/announcements/eur/risk_free_rate?api_key=YOUR_API_KEY"
curl "https://fxmacrodata.com/api/v1/announcements/sgd/risk_free_rate?api_key=YOUR_API_KEY"If you want a policy-decision framework instead, switch to the policy series rather than mixing the two ideas together:
curl "https://fxmacrodata.com/api/v1/announcements/usd/policy_rate?api_key=YOUR_API_KEY"
curl "https://fxmacrodata.com/api/v1/announcements/eur/policy_rate?api_key=YOUR_API_KEY"
curl "https://fxmacrodata.com/api/v1/announcements/dkk/policy_rate?api_key=YOUR_API_KEY"That split is what keeps event logic clean. Daily funding rates belong in carry models, short-end monitors, and relative-value dashboards. Policy rates belong in decision calendars, surprise analysis, and central-bank tracking.
Where to start in FXMacroData
Use the article as a framework, then move straight into the docs for the currencies you trade most.
- Check the USD rate structure if you are using dollar funding as the anchor.
- Compare EUR when you are building G10 carry or relative-rate dashboards.
- Review NZD when you need a reminder that not every short-end signal is a clean overnight benchmark.
Bottom line
FXMacroData makes multi-currency short-end analysis easier because it gives you one clean way to access funding-rate data without pretending every currency behaves the same way. That is the right balance for serious FX work: operational simplicity without analytical shortcuts.
If you keep benchmark currencies with benchmark currencies, treat proxies as proxies, and separate policy decisions from daily funding rates, your carry screens and dashboard signals become much more reliable.
Start with the currency-specific data docs at /api-data-docs/, then build your comparison set around structure first and ticker second.
