Every disclosure, dated, typed, sourced. Twelve markets.

Disclosure is the trail itself, offered as a product: per-node feed of what every issuer filed as it lands; jurisdiction exports of records and twelve-month trail; the provenance log — where each field came from, when it was read, what changed between drops; and the query log, kept in-region, of what a firm's agents asked and were answered. Public-record only; nothing a data licence could pull back.

London first: brokers, wealth managers and platforms under the FCA product governance rules (PROD) take the UK node's trail as the feed, RNS, the FCA National Storage Mechanism and Companies House as its sources, nothing licensed on the wire. Toronto next: the same feed from the Canada node for the KYP file. Then the other nine markets.

Scope

1.1

Unit: the disclosure event — date, type, title as published, category, reference, URL of the regulator's or exchange's copy.

1.2

Window: trailing twelve months per issuer, refreshed by the weekly sweep of each node.

1.3

Events at render: 2386821 across 11 live nodes (list_nodes).

The four shapes

2.1

Feed: per node, what every issuer filed as it lands — list_events_since with a date, paged.

2.2

Export: per jurisdiction, the records and the twelve-month trail as JSON, cut at a drop date.

2.3

Provenance log: per field, where it came from, when it was read, what changed between drops (the pond drops are the log; the surfaces snapshot is its page-level twin).

2.4

Query log: kept in the region of the calling firm — what its agents asked and were answered; never leaves that region; not yet in service (stated).

Counts per node

source: list_nodes at https://mcp.capitalmarketsknowledgegraph.ai/mcp, read at render

The residency rule

3.1

Every event list is stored and served in the jurisdiction of the issuer; the apex forwards and holds no body.

3.2

No fallback: a node that does not answer is reported unavailable; nothing is served from another region.

3.3

Exports are cut in-region and delivered from that region's door.

Access

4.1

Apex door (MCP, streamable-http, no auth): https://mcp.capitalmarketsknowledgegraph.ai/mcp — routes by identifier to the node that holds the name

4.2

Apex Agent Card (A2A): https://agent.capitalmarketsknowledgegraph.ai/.well-known/agent-card.json

4.3

Tools: resolve_issuer · get_record · list_aliases · list_events_since · list_nodes

4.4

Regional doors: mcp.<node>-cm-kg.ai/mcp, answers scoped to the node; descriptors at /mcp.json and /openapi.json

4.5

Registry entry: registry.modelcontextprotocol.io · io.github.allooloo/cm-kg

4.6

Feeds and exports sit behind the Registries layer (agent identity and licence); the public doors serve the record and the trail read-only to any caller.

Provenance

5.1

Every field carries its source URL, the reader (registry, exchange list, filing tag or named engine) and a state (sourced · filled · confirmed); none is served without source and read date.

5.2

Public-record only: no prices, quotes or licensed market data; blank stays blank; nothing inferred.

5.3

Records are versioned and never deleted; the record as_of and the field read dates are separate fields.

5.4

"Confirmed" is the word; signing is reserved for CMR (cm-record.org) and is not yet in service.

Estate

6.1

Eleven doors in eleven Azure regions, records stored and served in the issuer's jurisdiction; the apex holds an index only and forwards; no fallback across borders.

6.2

Hong Kong: a beacon at Width 0, local partner wanted, no door.

source: list_nodes at https://mcp.capitalmarketsknowledgegraph.ai/mcp, read at render

Machine kit

7.1

/llms.txt · /facts.json · /.well-known/agent-card.json · /.well-known/security.txt · /sitemap.xml · /robots.txt

7.2

Headers on every response: Content-Security-Policy (strict), Strict-Transport-Security, X-Content-Type-Options, Referrer-Policy, X-Frame-Options, X-CMR-Node, X-CMR-As-Of, X-CMR-Version, X-CMR-Source, X-CMR-Operator, X-Surface-Version.

Contact Us

The agents that built this read their own mail: allooloo@hey.com