get_orderability — whether a capital product may be ordered for a client category, for AI agents.

AIO · AI Orderability

12 markets with client categories on file · 16 with product scope on file — live from the Book manifest at render, sweep market date 2026-10-30

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 The outcome

1.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.

1.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.

1.3

Signal: one ACM-68000 (Agent Clearance Manifest) clearance signal, or none where the evidence does not reach a conclusion.

1.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.

1.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.

1.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.

1.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.

2 The signal

get_orderability turns the chapter, the rule revision and the record into one answer for a product and a client category in the product's home market — the ACM-68000 signal, with the outcome's signature, the node, the chapter section version and the receipt id on the same answer.

2.1

One call:

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

at https://mcp.getorderability.ai/mcp .

2.2

ACM-000, ACM-300 and ACM-500 are reserved by ACM-68000 and never served. An identifier that is not a listed security, a bare ticker that names more than one issuer, and a home node that did not answer are reported as errors with their reason, not as signals; nothing is served from another country.

2.3

The vocabulary is the open standard at acm-68000.org; the outcome's shape is aio-10060.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": {
    "getorderability": {
      "type": "http",
      "url": "https://mcp.getorderability.ai/mcp"
    }
  }
}

Claude Code:

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

3.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. get_orderability is routed to the node of the subject's listing; the node signs; the router forwards.

3.2

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

3.3

Tools: get_orderability, with resolve_issuer · get_record · get_signal · list_aliases · list_events_since · list_nodes on the same door.

3.4

Regional doors: mcp.<market>-cm-kg.ai/mcp and <market>.eu-cm-kg.ai/mcp for the European nodes — each answers its own market only; the roster entry of each (list_nodes, fields regional_door and agent_card) is the address of record.

3.5

Registry entry: registry.modelcontextprotocol.io · io.github.allooloo/getorderability. Documentation: getorderability.ai/docs; enterprise connector setup: allooloo.io/setup.

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 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.

5 Ask about any product

5.1

The subject names the market: an exchange prefix (TSX:, LSE:, XETRA:), a suffix (.TO, .L, .DE), an ISIN country code, or an LEI resolved through the apex index.

5.2

The client category is in the market's own words. Every market page opens with 'Ask get_orderability with:' and the categories its chapter names; a category the rule does not name returns ACM-404 and the list.

5.3

Default scope: the market the name belongs to. A name listed on two nodes returns two outcomes, each from its own door under its own chapter; nothing is joined across borders inside a door.

5.4

No node answers for another: if a door is unavailable the answer says so (no-fallback rule).

5.5

Every answer is an outcome with sources, never a summary. The desk for a person: ask.allooloo.io.

6 The Book of Markets

The outcome is built from the Book of Markets: one chapter per market, five sections — the record fields, the rule register, the orderability objects, the venues by Market Identifier Code, the disclosure classes — every value in one field shape with its source, date and pages checked. The chapter is served signed from the issuer's node at /book/manifest.json and rendered at sm-eco-10060.org/market/<market>/. The Book is the market-and-duty link of the stack; get_orderability is the door onto the question it answers.

7 What it is not

7.1

Not advice, not an individual suitability assessment, not permission, not a venue and not an order. It says what the sourced rules of a market say about a product and a category of client.

7.2

Not the firm's evidence. Where a regime requires a target-market statement, an assessment or product documentation and does not publish the document that satisfies it, the outcome records the requirement and marks the evidence firm-held. The condition rides on the outcome; the firm holds the proof.

7.3

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

8 The duty doors

8.1

agent-kyp.ai — Know Your Product (KYP), Canada · categories under National Instrument 31-103

8.2

agent-prod.ai — the Product Intervention and Product Governance Sourcebook (PROD) and the Consumer Duty, UK · categories under COBS 3

8.3

agent-mifid.ai — the product governance rules of the second Markets in Financial Instruments Directive (MiFID II), Germany · France · Netherlands · categories under Annex II as transposed

8.4

agent-finsa.ai — the Financial Services Act (FinSA), Switzerland · categories under Art. 4

8.5

agent-ddo.ai — the Design and Distribution Obligations (DDO), Australia

8.6

agent-regbi.ai — Regulation Best Interest (Reg BI), United States

8.7

Each door points an agent at the outcome under that duty, from the node of that market, in that regime's own category words; the duty decision stays with the firm.

9 Receipts

Every outcome's receipt is a permanent address on rco-records.ai that resolves to exactly what the door served — the outcome, the node, the chapter section version, the serving time, the signing key and the source page of each basis line. A second call never changes the first receipt. The receipt of a cleared read is the RCO receipt id on every door answer (receipt_id), readable at https://mcp.rco-records.ai/mcp and at cite-fact.ai.

10 The estate

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

10.1

The router holds an index only and forwards each call to the node of the listing; the outcome is produced, signed and receipted in its own country; no fallback across borders.

10.2

Every count on this page is read at render; nothing is typed.

11 Machine kit

11.1

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

11.2

Twins (same body, no 301): getorderability.com, getorderability.org, getorderability.io. Forwards here (301, path kept): get-orderability.ai, get-orderability.com, get-orderability.org, get-orderability.io.

Contact Us