Skip to content

Broker data infrastructure

Broker information changes constantly. Most affiliate websites struggle to stay up to date.

BrokerMeta keeps product information accurate and consistent across affiliate sites, comparison platforms and AI through our API.

The broker data API built with brokers.

BrokerSource
spread
0.7
licence
ABC123
risk_warning
74.2%
minimum_deposit
$0
jurisdiction
AE
BrokerMetav3 · 09:14 UTC

normalize → validate → version

Publisher

Average EUR/USD spread 0.7 pips · Licence ABC123 · Minimum deposit $0

Comparison tableReview pageAI answer

Illustrative example data. Not a real broker.

The problem

Broker data changes. Affiliate pages are out of date.

  • Spreads change
  • Risk warnings update
  • Instrument counts move

Licences, fees, leverage and account conditions differ by jurisdiction.

Yet thousands of publisher pages still rely on manually researched data.

Broker source

Current
EUR/USD spread
0.7
Risk warning
74.2%
Instruments
1,350
Updated
Today

Affiliate page

Out of date
EUR/USD spread
Differs from the broker source: 0.9
Risk warning
Differs from the broker source: 76.1%
Instruments
Differs from the broker source: 1,200
Updated
Differs from the broker source: 7 months ago

Illustrative example data. Not a real broker or a real quoted value.

BrokerMeta replaces that process with a structured source of truth.

How it works

Update once. Distribute everywhere.

  1. 01

    Brokers provide the source

    Approved public product data is supplied from our broker partners.

  2. 02

    BrokerMeta normalizes it

    Different broker structures are mapped into one consistent schema.

  3. 03

    Publishers connect once

    Use the data through:

    • REST API
    • WordPress integrations
    • Embeds
    • MCP and AI-agent workflows
  4. 04

    Data stays current

    When the source changes, connected publisher experiences can update with it.

Data is organized by

  1. Broker

    Example Broker

  2. Legal Entity

    Example Broker (UAE) Ltd

  3. Licence

    ABC123

  4. Jurisdiction

    United Arab Emirates

  5. Offering

    Retail — standard account

Every value BrokerMeta stores hangs off this hierarchy, so a fact is always attached to the entity, licence and jurisdiction it actually applies to.

Schema

One schema for broker metadata.

BrokerMeta can structure the information publishers repeatedly research and maintain.

Regulation

08
  • Legal entities
  • Regulators
  • Licences
  • Jurisdictions
4 more fields
  • Restricted countries
  • Investor protection
  • Risk warnings
  • Retail loss percentages

Trading

08
  • Asset classes
  • Instruments
  • Spreads
  • Commissions
4 more fields
  • Leverage
  • Margin requirements
  • Account types
  • Trading platforms

Accounts

07
  • Minimum deposits
  • Base currencies
  • Islamic accounts
  • Account-opening requirements
3 more fields
  • Inactivity fees
  • Custody fees
  • Currency conversion fees

Payments

08
  • Deposit methods
  • Withdrawal methods
  • Deposit fees
  • Withdrawal fees
4 more fields
  • Processing times
  • Cards
  • Bank transfers
  • E-wallets

Product experience

08
  • Mobile apps
  • Platform features
  • Authentication
  • Charting
4 more fields
  • Alerts
  • Research
  • Education
  • Support availability

Full field reference

Every category, field and data type in one place, with the jurisdiction rules that apply to each.

Explore the schema

Field names shown are representative of the schema. Coverage varies by broker and jurisdiction.

Jurisdiction

Built around jurisdiction.

A broker is not one global product.

The legal entity serving a customer can change by country.

So can:

  • regulation
  • available instruments
  • leverage
  • fees
  • account types
  • payment methods
  • risk disclosures

BrokerMeta models those differences directly.

Instead of asking

“What does this broker offer?”

you can ask

“What does this broker offer a retail client in the UAE?”

Choose a jurisdiction and client type

Example Broker

GET /brokers/example-broker/offerings?country=GB&client_type=retail

legal_entity
Example Broker (UK) Ltd
licence
GB-114872
max_leverage
1:30
instruments
1,350
payment_methods
Card, Bank transfer
risk_disclosure
Required

GET /brokers/example-broker/offerings?country=AE&client_type=retail

legal_entity
Example Broker (UAE) Ltd
licence
ABC123
max_leverage
1:200
instruments
980
payment_methods
Card, Bank transfer, E-wallet
risk_disclosure
Required

GET /brokers/example-broker/offerings?country=GB&client_type=professional

legal_entity
Example Broker (UK) Ltd
licence
GB-114872
max_leverage
1:500
instruments
1,420
payment_methods
Card, Bank transfer
risk_disclosure
Reduced protections apply

Illustrative example data for a fictional broker. Values are shown to demonstrate how offerings differ by jurisdiction and client type.

Integrations

Built for publishers.

API

Query normalized broker data directly from your application, CMS or internal database.

GETRequest
/brokers/example-broker/offerings
  ?country=AE&client_type=retail
  • REST
  • JSON
  • Versioned
  • Jurisdiction-aware
Explore API

Response · 200 OK

{
  "broker": "example-broker",
  "legal_entity": "Example Broker (UAE) Ltd",
  "licence": "ABC123",
  "client_type": "retail",
  "country": "AE",
  "offering": {
    "average_spread": 0.7,
    "minimum_deposit": 0,
    "max_leverage": "1:200",
    "instruments": 980
  },
  "updated_at": "2026-08-31T09:14:00Z"
}

Illustrative response shape for a fictional broker.

WordPress

Replace manually entered broker facts with connected fields.

Add the integration once and keep the underlying data current without repeatedly researching the same information.

AI & MCP

Give AI agents access to structured broker facts instead of asking them to research the open web.

Use BrokerMeta inside content workflows, CMS agents and internal publishing tools.

Embeds

Use broker data in comparison tables, review pages, pricing sections, regulation blocks and product cards.

Without building every component from scratch.

  • Comparison tables
  • Review pages
  • Pricing sections
  • Regulation blocks
  • Product cards

Language

More than raw values.

BrokerMeta can also turn structured broker facts into source-grounded language.

API value

average_spread: 0.7

Structured value from the broker source.

Generated description

The average EUR/USD spread for this account is currently 0.7 pips.

Language generated from the value on the left, not from the open web.

Generated descriptions stay tied to the underlying data.

When the fact changes, the description can change with it.

Version history

Know what changed.

BrokerMeta keeps a history of important product-data changes.

For every update, publishers can see:

This creates an auditable record instead of silently replacing old information.

EUR/USD average spread

Updated
Previous value
0.8 pips
Current value
0.7 pips
Effective date
31 August 2026
Source
Broker-supplied data

Version history

  1. v30.7 pips31 Aug 2026(current version)
  2. v20.8 pips14 May 2026
  3. v10.9 pips02 Jan 2026

Illustrative example data. Not a real broker or a real quoted value.

Trust model

Source-backed by design.

  • Broker supplied

    Canonical product facts come from participating brokers wherever possible.

  • Read only

    BrokerMeta does not require write access to broker systems.

  • Public metadata

    The platform focuses on information brokers already publish publicly.

  • Versioned

    Changes can be timestamped and retained historically.

  • Broker neutral

    One standardized data layer can support multiple competing brokers.

Editorial independence

Keep facts separate from opinions.

BrokerMeta provides the factual infrastructure.

Publishers keep control of their editorial layer.

BrokerMeta facts

Structured

BrokerMeta can supply

Spread
0.7 pips
Licence
ABC123
Minimum deposit
$0
Available in UAE
Yes

Publisher opinion

Editorial

The publisher still decides

Rating
4.6 / 5
Best for
Active traders
Recommendation
Editor's choice

Illustrative example data. Not a real broker or a real quoted value.

Broker data stays authoritative without compromising publisher independence.

Propagation

One change. Everywhere.

Imagine a broker updates its quarterly risk warning.

  1. Step 01

    Broker

    The source value changes.

    risk_warning: 74.2% → 76.4%

  2. Step 02

    BrokerMeta

    The new value is normalized, timestamped and versioned.

    normalized · v4 · 2026-08-31T09:14:00Z

  3. Step 03

    Publisher API

    The current value becomes available immediately.

    GET /brokers/example-broker

  4. Step 04

    Connected content

    Risk-warning blocks, tables and related descriptions can refresh automatically.

    3 templates · 1 comparison table · 1 review page

One update no longer needs to become hundreds of manual edits.

Illustrative sequence. Update behaviour depends on how a publisher connects.

Ecosystem

Infrastructure for the broker affiliate ecosystem.

For brokers
BrokerMeta creates a structured way to distribute accurate product information.
For publishers
It removes one of the most repetitive parts of maintaining broker content.
For AI systems
It creates a cleaner source of current, structured facts.
  1. Broker
  2. BrokerMeta
  3. Publishers
  4. Search & AI

BrokerMeta supplies structured product data to the publishers and tools that use it. It does not control search rankings or the output of any AI system.

Stop maintaining broker metadata manually.

Connect to one structured source for current broker product data.