get_target_market — the manufacturer's target market statement, filed once, read by every distributor's agent.

TM · the Target Market door

4 markets whose rules accept manufacturer evidence — live from the Book manifest at render, sweep market date 2026-10-30 · statements are stored at each node under tm/; no count of them is published on any page

get_target_market serves the target market statement a product's manufacturer has filed for its International Securities Identification Number (ISIN): who the product is for and who it is not for, in each market's own category words; how it may be distributed; what the product is; which documents and assessments stand behind it. The manufacturer's agent files it with file_target_market, signed and versioned; it is stored at the node of the product's home market, signed again under that node's key, and receipted. A distributor's agent reads it in one call, and get_orderability reads it in the same call that clears the product — so the conditions a regime places on a distributor that the manufacturer's statement discharges are shown discharged, with the statement's version and signature on the outcome.

1 The statement

1.1

Unit: one ISIN, one manufacturer (by Legal Entity Identifier), one version → one signed statement. A change is a new version with a supersedes link; every version stays published.

1.2

Target market: for each market the statement names, the positive target market — client categories, knowledge and experience, ability to bear loss, risk tolerance, objectives and needs — and the negative target market, each in the regime's own words, as the manufacturer states them.

1.3

Distribution: the distribution strategy the manufacturer sets — execution-only, with appropriateness, advised, portfolio management — as the regime names them.

1.4

Product: the manufacturer's product scope statement, mapped to the term the market's rule uses through the same scope bridge get_orderability uses.

1.5

Documents and assessments: the key information document, prospectus or factsheet by URL, date and hash at filing; the assessments the manufacturer states it performed, named and dated.

1.6

Source: the European MiFID Template (EMT) file the statement was derived from, by version and hash, where there is one; otherwise a direct filing.

1.7

Two signatures: the manufacturer's, under its filer identity or its own published key; the home node's, under its record key. Both verify offline.

1.8

Nothing judged: the door stores and serves the manufacturer's representation. It does not assess whether the statement is adequate; that duty stays with the firm.

2 Two calls

2.1

One read:

{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_target_market","arguments":{"subject":"DE0007164600"}}}

at https://mcp.gettargetmarket.ai/mcp .

2.2

One filing:

{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"file_target_market","arguments":{"subject":"<ISIN>","manufacturer":"<LEI>","statement":{…}}}}

with the filer identity in the authorization header.

2.3

The vocabulary is the open standard at aio-10060.org (the statement object, the signature rule and the discharge rule); the clearance signals are at acm-68000.org; the chapter is the market's Book of Markets page at sm-eco-10060.org/market/<market>/.

3 Access

Any MCP client that speaks Streamable HTTP:

{
  "mcpServers": {
    "gettargetmarket": {
      "type": "http",
      "url": "https://mcp.gettargetmarket.ai/mcp"
    }
  }
}

Claude Code:

claude mcp add --transport http gettargetmarket https://mcp.gettargetmarket.ai/mcp

3.1

Door: https://mcp.gettargetmarket.ai/mcp — the same router as https://mcp.getissuer.ai/mcp : same index, no second store. Reads need no authentication and no account; a filing needs a filer identity bound to the manufacturer's Legal Entity Identifier. Every call is routed to the node of the product's home market; the node signs; the router forwards.

3.2

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

3.3

Tools: file_target_market · get_target_market · list_target_market_versions · verify_target_market, with get_orderability · resolve_issuer · get_record · list_nodes on the same door.

3.4

Regional doors: mcp.<market>-cm-kg.ai/mcp and <market>.eu-cm-kg.ai/mcp — each serves the statements of its own market only.

3.5

Registry entry: registry.modelcontextprotocol.io · io.github.allooloo/gettargetmarket. Documentation: gettargetmarket.ai/docs; filing a statement: gettargetmarket.ai/file.

3.6

Paying for a read: every read is free unless the agent asks for the offer (header x402-pay: 1); the door then answers HTTP 402 with a signed offer and the same call carries the payment and the receipt — agentic-x402.ai.

4 Filing

4.1

Who may file: the manufacturer of the product, identified by its Legal Entity Identifier, holding a filer identity issued at this door after it has shown control of the issuer domain on the product's record — a DNS record or a mail to a role address at that domain. One identity per manufacturer; the value is shown once and never held in clear by Allooloo.

4.2

What may be filed: a statement for an ISIN the manufacturer's Legal Entity Identifier issues. A filing against any other subject is refused. A filing never overwrites; it supersedes.

4.3

From an EMT file: a manufacturer that already produces the European MiFID Template files it as the statement's source; the door carries the file's version and hash and the fields as mapped.

4.4

Request a filer identity: gettargetmarket.ai/file .

5 Provenance

5.1

Every statement is signed by the manufacturer under its filer identity or its own published key, and by the home node under its record key (EdDSA); verify against the key ids named in the statement.

5.2

Every filing and every read is receipted at https://mcp.rco-records.ai/mcp with the door as writer and the filer or reader as caller; the receipt's answer_hash binds it to the exact signed statement; verify_receipt is public and works offline against rco-records.ai/.well-known/jwks.json.

5.3

Every version ever filed stays published, unchanged, for as long as a receipt cites it. An outcome that cited version 3 resolves to version 3.

5.4

The documents a statement names are re-fetched nightly; a document that no longer resolves or whose hash has changed is marked drifted on the statement, never removed, and the manufacturer is the one to file again.

5.5

Whether a regime accepts the manufacturer's statement as the evidence a distributor may rely on is a sourced field of the Book of Markets, read from the regulator's own text; where the regime is silent, the condition stays with the firm even when a statement is on file.

6 How get_orderability uses it

serving

An orderability outcome for a product with a statement on file shows, for each condition the regime places on the distributor: discharged by manufacturer statement v<N> (filed <date>, key <kid>) where the market's chapter says the regime accepts manufacturer evidence for that condition; present, firm-held where the chapter is silent; firm-held where no statement exists. The clearance signal is unchanged by the statement — a statement never clears or blocks a product. The outcome names the statement version it read and the filing receipt, so the trace runs receipt → outcome → statement → manufacturer signature → source file.

Sample outcome — the test subject TEST:DE000TMKT025, asked at the Germany node for the client category “Professionelle Kunden”, read at render, receipted at the receipt door (statement v2, filing receipt rco:cr6sufspj577sq3e5ahk):

7 What it is not

7.1

Not a judgment on the product, the manufacturer or the statement. It is the manufacturer's representation, signed, dated and served.

7.2

Not the distributor's assessment. The regime's duties on the distributor — appropriateness, suitability, its own target market — stay with the distributor.

7.3

Not a registry of record for the regulator. It is evidence an agent can cite and a firm can keep.

7.4

Not a count. No page of this door states how many statements, manufacturers or markets it holds; the figures above are read at render.

8 Receipts

Every filing and every read has a permanent address on rco-records.ai that resolves to exactly what the door stored or served — the statement version, both signatures, the serving time and the key ids. A second read never changes the first receipt. The receipt id is on every door answer (receipt_id), readable at https://mcp.rco-records.ai/mcp and at cite-fact.ai.

9 The estate

source: list_nodes at https://mcp.getissuer.ai/mcp, /book/manifest.json and tm/ at each node, read at render.

Machine kit

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

Twins (same body, no 301): gettargetmarket.org, gettargetmarket.io. Forwards here (301, path kept): get-targetmarket.com.

Contact Us