Regulation
08- Legal entities
- Regulators
- Licences
- Jurisdictions
4 more fieldsShow fewer
- Restricted countries
- Investor protection
- Risk warnings
- Retail loss percentages
Broker data infrastructure
BrokerMeta keeps product information accurate and consistent across affiliate sites, comparison platforms and AI through our API.
The broker data API built with brokers.
normalize → validate → version
Average EUR/USD spread 0.7 pips · Licence ABC123 · Minimum deposit $0
Illustrative example data. Not a real broker.
The problem
Licences, fees, leverage and account conditions differ by jurisdiction.
Yet thousands of publisher pages still rely on manually researched data.
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
Approved public product data is supplied from our broker partners.
Different broker structures are mapped into one consistent schema.
Use the data through:
When the source changes, connected publisher experiences can update with it.
Data is organized by
Broker
Example Broker
Legal Entity
Example Broker (UAE) Ltd
Licence
ABC123
Jurisdiction
United Arab Emirates
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
BrokerMeta can structure the information publishers repeatedly research and maintain.
Every category, field and data type in one place, with the jurisdiction rules that apply to each.
Field names shown are representative of the schema. Coverage varies by broker and jurisdiction.
Jurisdiction
A broker is not one global product.
The legal entity serving a customer can change by country.
So can:
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?”
GET /brokers/example-broker/offerings?country=GB&client_type=retail
GET /brokers/example-broker/offerings?country=AE&client_type=retail
GET /brokers/example-broker/offerings?country=GB&client_type=professional
Illustrative example data for a fictional broker. Values are shown to demonstrate how offerings differ by jurisdiction and client type.
Integrations
Query normalized broker data directly from your application, CMS or internal database.
/brokers/example-broker/offerings
?country=AE&client_type=retailResponse · 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.
Replace manually entered broker facts with connected fields.
Add the integration once and keep the underlying data current without repeatedly researching the same information.
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.
Use broker data in comparison tables, review pages, pricing sections, regulation blocks and product cards.
Without building every component from scratch.
Language
BrokerMeta can also turn structured broker facts into source-grounded language.
average_spread: 0.7
Structured value from the broker source.
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
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.
Version history
Illustrative example data. Not a real broker or a real quoted value.
Trust model
Canonical product facts come from participating brokers wherever possible.
BrokerMeta does not require write access to broker systems.
The platform focuses on information brokers already publish publicly.
Changes can be timestamped and retained historically.
One standardized data layer can support multiple competing brokers.
Editorial independence
BrokerMeta provides the factual infrastructure.
Publishers keep control of their editorial layer.
BrokerMeta can supply
The publisher still decides
Illustrative example data. Not a real broker or a real quoted value.
Broker data stays authoritative without compromising publisher independence.
Propagation
Imagine a broker updates its quarterly risk warning.
The source value changes.
risk_warning: 74.2% → 76.4%
The new value is normalized, timestamped and versioned.
normalized · v4 · 2026-08-31T09:14:00Z
The current value becomes available immediately.
GET /brokers/example-broker
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
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.
Connect to one structured source for current broker product data.