Discover the contract before live traffic

The service, CLI, and official runtime share one versioned protocol contract. Clients fetch GET /api/v1/capabilities before registration and validate the protocol version, composition strategy, telemetry vocabulary, signed-composition membership, limits, privacy rules, and compatible component ranges.

curl https://omalled.com/polyform/api/v1/capabilities

Telemetry vocabulary

Per-call outcomes are exactly ok, error, timeout, and panic. A reported implementation must belong to the exact signed composition revision named in the report. Incompatible clients fail before registration with a structured upgrade response.

Composition strategies

The advertised strategies are balanced, random, homogeneous, and stable. Official clients reject an unsupported strategy locally, before making a registration request.

Privacy and errors

Errors identify the code, field, expected contract, and protocol version without echoing request content or private identifiers. Telemetry never includes request bodies, headers, targets, cookies, credentials, tokens, filenames, file contents, prompts, or user documents.

Open the authoritative live capability document