DOCS
REST API
The /v1 contract is published as OpenAPI and generated from the capability registry.
Product teams exposing business knowledge through APIs, MCP, A2A and connected systems
Produce consistent machine contracts and controlled workflows from one canonical capability registry.
Scope, role, entitlement and write authority are enforced by the server, never asserted by the client.
Contract
The machine-readable contract lives at /v1/openapi.json. It is generated, so the documented surface and the callable surface cannot drift apart.
Versioning
Paths are prefixed with /v1. A breaking change ships as a new version rather than a silent change to an existing route.
Idempotency
Write endpoints accept an idempotency-key header. Replaying the same key with the same payload returns the original result instead of duplicating work.
Errors
Failures use a problem document with a stable code, a title, a detail and a correlation id. Stack traces are never returned.