# BrokerMeta integrations

> REST API, WordPress, MCP for AI agents, and embeds — all resolving to the same record

Source: https://brokermeta.ai/integrations

---

Four surfaces over one source. A REST call, a WordPress shortcode and an MCP tool call all resolve
to the same versioned record.

## REST API

Filter by country, client type, asset class and account type; request only the fields a template
needs; every response carries a version and an effective date; conditional requests transfer only
what changed.

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

## WordPress

Shortcodes and blocks for single values, tables and regulation panels. Values resolve at render
time, so pages do not go stale between edits. Editors keep writing copy; only factual fields are
connected.

```
[brokermeta broker="example-broker" field="average_spread" country="AE" client_type="retail"]
```

## AI and MCP

An MCP server exposing the same entities the API serves, so agents retrieve current values instead
of recalling stale ones or researching the open web. Responses are grounded in supplied data with
the source attached. Useful inside content workflows, CMS agents and internal publishing tools.

```
get_broker_offering({ broker: "example-broker", country: "AE", client_type: "retail" })
```

## Embeds

Drop-in components for comparison tables, product cards, regulation and risk-warning blocks, and
pricing and fee sections, styled to inherit the host site's typography and colours.

---

## About this file

Markdown version of https://brokermeta.ai/integrations, provided under the [llms.txt](https://llmstxt.org)
proposal. The index of every such file is at https://brokermeta.ai/llms.txt.

Every broker value in BrokerMeta material is an illustrative example for a fictional
"Example Broker". No real broker is described, and nothing here is financial advice.

Questions: hello@brokermeta.ai