Skip to content
BrokerMeta.ai

Integrations

Four ways to connect. One source underneath.

However you publish broker information, the underlying facts come from the same structured, versioned record.

Read the docsJoin early access

Surfaces

Pick the one that fits your stack.

REST API

01

The primary surface. Query brokers, entities and offerings directly from your application, CMS or data warehouse.

  • 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 so you only transfer what changed

WordPress

02

Replace manually entered broker facts with connected fields, without rebuilding your templates.

  • 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 the factual fields are connected
  • Works alongside your existing review and rating fields

AI & MCP

03

Give agents a structured source of broker facts instead of asking them to research the open web.

  • An MCP server exposing the same entities the API serves
  • Agents retrieve current values rather than recalling stale ones
  • Useful inside content workflows, CMS agents and internal tools
  • Responses are grounded in supplied data, with the source attached

Embeds

04

Drop-in components for the blocks every broker page repeats, without building each one from scratch.

  • Comparison tables and product cards
  • Regulation and risk-warning blocks
  • Pricing and fee sections
  • Styled to inherit your typography and colours

In practice

The same offering, three ways.

A REST call, a WordPress shortcode and an MCP tool call all resolve to the same versioned record.

GETREST
/brokers/example-broker/offerings
  ?country=AE&client_type=retail
WordPress
[brokermeta
  broker="example-broker"
  field="average_spread"
  country="AE"]
MCP tool call
get_broker_offering({
  broker: "example-broker",
  country: "AE"
})

Endpoint paths, parameter names and shortcode attributes are indicative while the API is in early access.

Tell us where your broker data lives.

WordPress, a headless CMS, a spreadsheet or an internal database — we will map the shortest path to a connected integration.

Join early accessTalk to us