Sustema

ENTITY developer reference

Connect an MCP client

Candidate documentation for reading and synthetic examples. Account creation, live API access, SDKs, collections and MCP are not available here. A released service profile and matching integration instructions are required before use.

Availability and support boundary

An MCP connection is not available from these pages. Supported client versions, the actual endpoint, OAuth setup and end-to-end behaviour remain to be qualified. No installation command, service URL or client compatibility claim is supplied here.

The defined protocol baseline is MCP 2025-11-25 over Streamable HTTP with JSON responses, without an SSE event stream. This names the contract baseline; it does not claim to be the latest protocol or establish support for a particular client.

Before connecting

Use the released ENTITY endpoint and documented OAuth flow for the chosen client. Confirm its supported protocol and runtime versions, intended workspace, delegated data authority and usage ceiling. Complete initialization and compare the immutable binding with the release’s public bundle.

Discovery exposes a stable catalogue; it does not grant entitlement to invoke every tool. Current authority must still hold when invoking a tool and receiving its result. A tool profile argument cannot select an incompatible generation.

Review the effects of each tool

MCP carries the same bounded data capabilities, evidence, rights and accounting as the API. Operations can consume delegated credits or change an owned classification order or report. Discovery and tool annotations are not authority to buy funding, accept account terms or enlarge a spending mandate.

Private account, staff, operator and funding-purchase APIs are outside the public tool surface. Do not use a shared operator credential. Treat company and supplier text as data, never as instructions to an agent.

Read errors at the correct boundary

Malformed protocol requests and known-tool input validation have distinct handling. Known-tool validation uses the governing API Problem as a tool error. Domain denials retain restricted disclosure; a client must not infer hidden resources from refusal details.

Preserve the complete API envelope, limitations and usage. HTTP and MCP must agree on business outcome and accounting. Unknown retry delay remains unknown; a client must not invent one or interpret recovery guidance as permission for a fresh charged operation.

Reconnect without repeating work

If acknowledgement is lost, reconcile the original operation using its key, creation time and compatible contract. A later authentication failure does not establish whether the earlier attempt committed.

Reinitialising an expired session, sending notifications/cancelled, or deleting a session does not cancel or refund admitted business work. Cancelling delivery and cancelling a supported owned classification order are separate operations. Revocation during delivery can leave original effects uncertain even when delivery stops.

Next: release compatibility, application credentials and operation reference.