Kortex
snapshot · 2026-07-18
Kortex · agents & MCP · the platform as tools, with the bill on every result

Built to be read by agents

Kortex serves AI agents as first-class clients: an MCP server over the full platform (not just the graph), the cost of every call returned on every result, receipts an agent can cite and replay, machine-readable grounding documents, and a developed error contract. Deterministic underneath; the agent gets the same governed, source-traceable answers a human analyst gets.

Connect

MCP (streamable HTTP):  POST https://kortex.orkora.com/v2/mcp     X-API-Key on every request
Discovery manifest:     GET  https://kortex.orkora.com/.well-known/kortex.json
Agent map:              GET  https://kortex.orkora.com/llms.txt
Errors:                 GET  https://kortex.orkora.com/v2/errors   ·   OpenAPI: /openapi.json

14 tools

toolwhat it doesfloor
kortex_cost_previewestimate any call before running it; free0
kortex_schemagraph schema: labels, edge types, live totals1,000
kortex_search_generatorsgenerator search by fuel, zone, operator, MW2,000
kortex_get_nodeany node as a faceted view with per-domain provenance2,000
kortex_traverseN-hop traversal from a node; billed per edge delivered5,000
kortex_cypherread-only Cypher; billed on delivered output at field weights20,000
kortex_tablesevery servable dataset: catalogue + governed row fetch with filters50,000
kortex_seriestime-series catalogue + fetch (prices, rates, carbon, flows)2,000
kortex_country18-indicator country profile; absence disclosed, never interpolated2,000
kortex_asset_profilesectioned asset risk profile, evidence class per section2,000
kortex_entityLEI-keyed corporate profile + ownership control map (attribute-once totals)2,000
kortex_insightpre-built cross-domain screens (stranded assets, queue blockage…)5,000
kortex_siting_screenthe flagship in one call: ranked zones + rejections + receipt5,000
kortex_receiptreplay a frozen answer by receipt id: cite receipts, not screenshots1,000

The cost contract

Every tool result is JSON with a cost block: what was billed, the category floor, the delivered-output value and the basis. Settlement is max(floor, delivered-output value) at the same field weights as REST, on every channel, so no path through the platform is a cheaper pipe for the same data. Provenance metadata is never billed. A hard 402 gate re-checks the actual cost before the payload is delivered; a blocked response bills nothing, and tool errors bill nothing.

{"data": {…}, "cost": {"billed_credits": 51000, "floor_credits": 50000,
  "delivered_value_credits": 51000, "basis": "max(category floor, delivered-output value)"},
 "receipt_id": "…"}   // when the payload carries a retrievable provenance receipt

A server-side billing-integrity watchdog audits value density on every response (payload size vs credits billed) and flags any route serving materially more than it charges; flagged routes are reviewed and repriced at source.

Grounding resources (MCP resources/read)

uricontents
kortex://pricinglive cost weights and the settlement rule
kortex://errorsstable error codes with meaning and resolving action
kortex://schemanode labels, edge types, live totals
kortex://sourcesregistered sources with licence and rights status
kortex://rightsrights modes, fail-closed semantics, evidence-class principles
kortex://correctionsthe corrections register: every governance-driven change to a served number, before/after and reason (also RSS at /v2/corrections.rss, deltas via ?since=)

These exist so an agent grounds itself in Kortex's actual governance instead of guessing: what things cost, what errors mean, what the rights position is, where every number comes from.

Answers an agent can defend

Envelope-bearing results carry a receipt: the frozen canonical answer, graph snapshot id, software build and resolved sources, retrievable forever at GET /v2/receipts/{id} or via the kortex_receipt tool. An agent that cites a Kortex receipt is citing an artifact its principal can independently replay. Absence is disclosed (present=false), contradicted data is quarantined and documented, and there is no LLM in the stack: the same call returns the same answer.

Rights: licensing & rights modes · evidence: coverage · methodology · validation · data: the five surfaces · contracts: OpenAPI. Keys: kortex@orkora.com, API access by agreement.