Checklist for pointing the demo at your own FX feed

Field notes

Start with authentication. Store API keys in Cloudflare secrets, regenerate the typed bindings, and confirm the loader never logs sensitive tokens.

Map your payload into the demo schema (`rate`, `ts`, `base`, `quote`). The UI does not care where the data originated as long as the shape stays consistent.

Revisit the narrative copy after integration. Update references to “demo data” with accurate descriptions of your provider and include any required attribution.

Key takeaways

Copy these into your own playbooks or PRDs—the bullet points summarize the decisions the article supports.

• Treat credentials as infrastructure, not code—use Wrangler secrets.
• Normalize external payloads to the existing `ExchangeRateRecord` type.
• Refresh the disclosures page when you switch from demo to live data.