Goal: build a small browser-based macro dashboard with ChatGPT Sites and a public FXMacroData endpoint, then use it as a starting point for research tools, data explainers, and internal prototypes.
Explore the FXMacroData macro dashboard example. It presents the public USD inflation release history as a release monitor.
Good research tools make a macro release easier to inspect, not harder to trust. A useful dashboard should show the latest value, recent history, the official source, and the time context around the release. ChatGPT Sites is a fast way to turn that product idea into a working interface; FXMacroData's builder hub supplies the macro data layer.
Who this example is for
| Reader | Useful first build | Why it helps |
|---|---|---|
| Research team | Release monitor | Keep the latest print, its history, and source context in one view. |
| Product builder | Macro dashboard prototype | Test a data-led interface before committing to a larger application. |
| Content team | Data explainer | Turn a current macro series into a visual companion to an article or briefing. |
What the example app does
The example uses the public US inflation release history to render four things that matter in a macro workflow:
- the latest year-on-year reading;
- the previous reading and the change between releases;
- a compact trend view of the latest observations; and
- the publisher and known-at context that makes the number auditable.
FXMacroData public endpoint → ChatGPT Sites interface → release monitor → research discussion or product prototype.
The point is not to turn a single figure into a trading instruction. It is to make the released record easy to inspect before a researcher, analyst, or product workflow takes the next step.
Step 1: Start with a public data surface
The public USD inflation endpoint is a useful starting point because it returns a concise release history without requiring an API key. Open the endpoint directly to inspect the shape before designing the interface:
https://api.fxmacrodata.com/v1/announcements/usd/inflation?limit=8The response includes a release series in data, along with publisher and data-quality context. For a release monitor, the important fields are the observation date, value, and announcement_datetime: the time the market could have known the observation.
Step 2: Describe the dashboard before you build it
A short build brief keeps the first version focused. Ask ChatGPT Sites for a single-page dashboard with an FXMacroData identity, a dark navigation treatment, a live USD inflation card, a release-history chart, and a visible source label. State that no API key should appear in the page or its client-side code.
That brief is deliberately narrow. It helps you test whether the release monitor is readable before adding calendars, pair context, or premium data access.
Step 3: Fetch the release history
Run this request in the site's server-side or build step rather than in browser code: the FXMacroData API is designed for server-side use and does not send CORS headers to browser origins. The fetch can stay small when the endpoint is public. This example sorts the returned observations from oldest to newest so a chart reads naturally from left to right.
const response = await fetch(
"https://api.fxmacrodata.com/v1/announcements/usd/inflation?limit=8"
);
if (!response.ok) throw new Error("Data is unavailable");
const payload = await response.json();
const releases = [...payload.data].reverse();
const latest = releases.at(-1);
const previous = releases.at(-2);For protected coverage, customer-specific views, or higher-volume product traffic, keep the API key in a server-side data layer rather than in browser code. The public demo is intentionally limited to a no-key USD surface.
Step 4: Design around the release record
Use the data shape to decide what belongs on screen. The dashboard example uses a simple hierarchy:
- Latest release: make the newest value immediately visible.
- Change: compare it with the preceding release without implying a forecast or trade recommendation.
- History: show enough releases to make the latest print meaningful.
- Provenance: retain the publisher and timing context beside the chart.
That structure works for other macro series too. A policy-rate panel can link to the relevant Federal Reserve release context, while an event monitor can use the release calendar to show what is scheduled next.
Step 5: Use the prototype as a product decision tool
Once the page is useful, it becomes a concrete reference for the next product decision. You might keep it as an internal research surface, expand it into a customer dashboard with the appropriate data rights, or use it to decide which FXMacroData endpoint belongs in a larger application.
| Next need | Best next FXMacroData surface |
|---|---|
| Upcoming macro events | Release Calendar |
| Pair-specific market context | FX pair dashboard |
| Structured integration reference | API reference |
| Tool-connected research workflow | MCP server guide |
What to measure before expanding the app
Test whether a reader can answer four questions without leaving the page: what changed, when it became known, who published it, and which series they are looking at. If those answers are not clear, improve the information hierarchy before adding more charts.
Then test the real workflow. Ask a researcher to use the monitor before a release discussion, or ask a product teammate to explain the latest reading from the screen alone. Those checks reveal whether the dashboard is clarifying the record or merely decorating it.
Summary
ChatGPT Sites can turn a data-product idea into a reviewable macro interface quickly. Start with a public FXMacroData release endpoint, keep the record and its provenance visible, and use the result to decide what belongs in the next version of the product. Explore the working FXMacroData dashboard example, then continue with the Builder Hub when you are ready to extend it.
