FXMacroData Commercial Redistribution gives product builders a clear path to show macro and FX data inside customer-facing apps, dashboards, portals, publisher pages, widgets, reports, and AI market tools. It is built for teams that want to add trusted market context to their own product experience without negotiating an enterprise contract before they have meaningful traffic.
- Fintech apps that want macro cards, event calendars, or FX context inside customer accounts.
- Broker, research, and publisher products that need data-backed market modules.
- AI market tools that generate summaries, previews, or briefings from structured macro data.
- Early-stage products using stacks such as Supabase and Vercel that need a legitimate customer-facing display license.
What Commercial Redistribution is
Commercial Redistribution is a display license for approved downstream products. It lets your app show FXMacroData-powered output to end users while keeping the commercial rights, attribution, and usage measurement clear from day one.
The plan is intentionally different from an individual API subscription. Individual use is for private research, scripts, notebooks, backtests, alerts, and internal workflows. Commercial Redistribution is for the moment your users, customers, readers, or subscribers can see the data inside your product.
| Use case | Right plan | Why |
|---|---|---|
| Customer dashboard, portal, publisher page, report, widget, or AI market summary | Commercial Redistribution | People outside your team can see FXMacroData-powered output. |
| Private scripts, notebooks, research, backtests, or internal-only alerts | Individual or Enterprise, depending on team size | The data is not displayed to external users. |
| Raw data feed, public API, data marketplace, bulk export, or white-label pass-through | Enterprise | Those rights go beyond the self-serve display license. |
Supabase and Vercel example
Imagine a founder building a market intelligence app on Supabase and Vercel. Supabase handles user accounts and product state. Vercel hosts the application. The product team wants to add a macro dashboard where customers can see the latest US CPI context, upcoming releases from the release calendar, and a short note about how those events could matter for EUR/USD.
That is a natural Commercial Redistribution use case. The app is not reselling a raw data feed. It is showing a licensed, human-facing product experience: a CPI card, an event calendar, a chart, and a written explanation inside the customer's workflow.
A customer logs in and opens a macro dashboard.
The product requests FXMacroData from a server-side boundary.
Supabase stores app state and display-ready product views.
The user sees attributed macro cards, charts, and commentary.
The practical boundary is simple: the customer sees useful market output, not the underlying FXMacroData feed. Supabase can support the product experience, but it should not become a customer-accessible raw data warehouse. Vercel can host the app, but the browser should not contain reusable FXMacroData credentials.
What customers see
A good redistribution experience should feel like part of your product. Customers should see clear, useful context, such as:
- A macro event card showing the latest inflation reading and release time.
- A dashboard tile for upcoming central-bank or economic releases.
- A pair-focused note explaining why a macro event matters for a currency pair.
- A chart or widget that helps users understand recent macro direction.
- A visible "Data powered by FXMacroData" attribution near the data module.
The product should not look like a data dump. The value is in turning reliable macro data into a useful customer-facing experience, whether that is a dashboard, broker portal, research page, AI summary, or publisher widget.
How pricing and metering work
Commercial Redistribution is priced for early product launches. It starts at $25 per 1,000 measured monthly non-bot website users, with a $25 monthly minimum after the 14-day trial. The meter is based on measured users who can see FXMacroData-powered output, not raw page views.
| Measured monthly users | Billable blocks | Monthly charge after trial |
|---|---|---|
| 0 to 1,000 | 1 block | $25 minimum |
| 1,001 to 2,000 | 2 blocks | $50 |
| 3,422 | 4 blocks | $100 |
| 10,000 | 10 blocks | $250 |
This makes it possible to launch a real customer-facing product without pretending an individual API key includes redistribution rights. As usage grows, the same metering makes it clear when the product is ready for Enterprise terms, custom limits, additional domains, procurement, SLA discussions, or broader redistribution rights.
What is allowed and what needs Enterprise
The Commercial Redistribution boundary is designed to be easy to explain: customer-facing display is allowed when it is approved, attributed, metered, and served from a secure product architecture. Raw redistribution is not included.
| Allowed on Commercial Redistribution | Needs another path |
|---|---|
| Customer-facing cards, charts, calendars, reports, widgets, and AI summaries. | Raw public APIs, database access, or feed-like pass-through. |
| Approved product display on the registered domain. | Multiple unrelated domains, client portals, white-label delivery, or broker-scale distribution without approval. |
| Visible attribution and pixel metering on pages that show FXMacroData-powered output. | Hidden attribution, blocked metering, marketplace resale, or customer-facing bulk downloads. |
| Reasonable product caching for performance and reliability. | Permanent data warehouses, historical archives for resale, or downloadable datasets. |
If the product requires raw exports, client-specific redistribution, white-label access, data marketplace listing, warehouse sharing, procurement review, or formal support commitments, move the conversation to Enterprise before building that path.
Why it matters for product teams
Many early fintech products start with a small feature: a market calendar, a macro dashboard, a client note, or an AI-generated market summary. The commercial risk appears when that feature becomes visible to users. Without a redistribution license, a personal API subscription can quietly become the data layer for a customer-facing product.
Commercial Redistribution solves that gap. It gives builders a legitimate way to launch, show attribution, measure exposure, and scale from a small audience to a larger commercial agreement when the product proves demand.
Common questions
When do I need FXMacroData Commercial Redistribution?
Use Commercial Redistribution when users, customers, subscribers, readers, or app visitors can see FXMacroData-powered output inside your product. If the data stays private to you or your internal team, use the appropriate internal-use plan instead.
Can a Supabase and Vercel app show FXMacroData data?
Yes. A Supabase and Vercel app can show FXMacroData-powered output when the product is approved for customer-facing display, uses visible attribution, installs the redistribution pixel, keeps data access server-side, and avoids raw feed or download behavior.
Can I let customers download the underlying data?
No, not on the self-serve Commercial Redistribution path. Customer-facing raw downloads, bulk files, database access, public APIs, and feed-like delivery require Enterprise terms.
How does the pixel affect billing?
The redistribution pixel helps measure monthly unique non-bot website users who can see FXMacroData-powered output. That keeps pricing tied to actual product exposure rather than manual reporting or page-view estimates.
Get started
Start with one approved product surface. For example, add a macro event card, a release-calendar panel, or a pair-specific dashboard module to your app. Keep attribution visible, make the approved domain clear, and treat FXMacroData as the licensed data source behind the customer experience.
Review the Commercial Redistribution plan, the Commercial Redistribution Terms, and the redistribution pixel setup guide. For larger rollouts, multiple domains, white-label delivery, raw feeds, exports, procurement, or SLA requirements, use the Enterprise path.
