DEVELOPERS

Developer surfaces

OpenAPI, MCP and A2A contracts are generated from the same canonical capability registry.

BUILT FOR

Product teams exposing business knowledge through APIs, MCP, A2A and connected systems

BUSINESS OUTCOME

Produce consistent machine contracts and controlled workflows from one canonical capability registry.

DECISION CONFIDENCE

Scope, role, entitlement and write authority are enforced by the server, never asserted by the client.

OpenAPI

The versioned contract lives at /v1/openapi.json so clients can generate against the supported HTTP surface.

The machine endpoint remains /mcp while MCP Launch handles client setup, scopes and verification.

The agent discovery record is published at /.well-known/agent.json and declares currently available capabilities.