Documentation — the orderability door

get_orderability is the orderability outcome: for one listed security, one client category and one market, what that market's own rules say — may this product be ordered for this category of client, under the rule revision in force today. The answer is built from the Book of Markets, the sourced chapter of every market's product-governance, design-and-distribution or know-your-product duty; it is signed by the node of the issuer's own country and receipted before it is served. An agent at a manufacturer, a distributor or a dealer asks it before an order proceeds; the firm keeps the receipt and shows afterwards what rule it relied on.

1 Access

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

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

1.1: Door: https://mcp.getorderability.ai/mcp — the same router as https://mcp.getissuer.ai/mcp : same index, no second store; read-only, no authentication, no account.
1.2: Agent Card (A2A): https://agent.getorderability.ai/.well-known/agent-card.json .

2 One call

{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_orderability","arguments":{"subject":"XETRA:SAP","client_category":"Professionelle Kunden"}}}

signal	state	when
ACM-200	CLEARED	the category is one the market's securities rule names; the subject is on the register and not halted; a rule revision exists; the instrument class is within the rule's product scope. The conditions ride on the outcome; the firm holds the evidence
ACM-403	EXCLUDED	the regime itself states an exclusion for this category and this class of instrument — a product-intervention measure, a retail ban — cited to the measure
ACM-404	NOT NAMED	the category is not one the market's rule names; the outcome lists the categories it does
ACM-451	READ THE FILING	a regulatory filing for the issuer is dated in the last three days; a person reads it before the agent acts
no signal	NOT DETERMINABLE	the evidence does not reach a conclusion; the outcome carries evidence_gaps with the pages checked, and stops

3 The outcome

3.1: Unit: one subject, one client category, one market, one rule revision → one signed outcome in the AIO-10060 §7.1 shape, keyed <market>-cm-kg/<venue>/<code>, resolved by ticker, ISIN or LEI.
3.2: Scope: the product by its record version and instrument class; the client category in the market's own classification (Paragraph (o) · Professionelle Kunden · elective professional client · Privatkundinnen und -kunden); the market; the immutable rule revision applied.
3.3: Signal: one ACM-68000 (Agent Clearance Manifest) clearance signal, or none where the evidence does not reach a conclusion.
3.4: Basis: every distribution condition the regime imposes, with the party it binds and the evidence that discharges it where the regime names one, marked firm-held where it names none; the scope object the subject's class falls within, cited to the provision; each line naming the chapter field it rests on.
3.5: Gaps: the items the regime requires and the firm holds — target-market statement, product scope statement, product documentation, required assessments — each cited to the Book, each listed as firm-held. Where a category is not one the rule names, the outcome lists the categories the chapter does name, in the regime's words, so the question can be asked again correctly.
3.6: Review: the triggers after which the outcome must be produced again — a new rule revision, a new chapter section version, a change on the record.
3.7: Nothing inferred: a value the reader marked inferred, or prose it could not structure, is visible in the Book and never used; a regulator's page the reader could not reach is recorded as not found with the pages checked.

4 Provenance

4.1: Every outcome is signed by the producing node under its record key (EdDSA); verify against the node's /.well-known/jwks.json named in the answer. The outcome stamps the AIO-10060 text version and the gate version it was produced under.
4.2: Every read is receipted at https://mcp.rco-records.ai/mcp with the node as writer; the receipt's answer_hash binds it to the exact signed outcome; verify_receipt is public and works offline against rco-records.ai/.well-known/jwks.json. The receipt id is on every answer (receipt_id).
4.3: Every basis line names the chapter field it rests on; every chapter field carries its source URL, the date the page bears, the time it was read and the pages checked. The section version the outcome read stays published, unchanged, for as long as the receipt exists.
4.4: Public rule text only: the regulator's own pages and statutes; nothing licensed from a third party; nothing inferred. A source that refuses automated reading is recorded as not found, not worked around.
4.5: Re-read weekly by the Book's readers — a search reader, a reading model and a review model that rejects what the page does not say — and on targeted passes when a provision changes. No staff on the line.

getorderability.ai