Platform status

Docket’s public API is prerelease. The current public REST compatibility contract is 0.1.0, and Docket supports one current contract rather than a retained set of versions.

Surface	Current status
REST resource	`https://api.clearthedocket.com/v1` with version and revision response headers.
REST OAuth bearer access	`GET` and `HEAD /v1/orgs` with `work:read` only.
MCP	Streamable HTTP at `https://api.clearthedocket.com/mcp`.
OAuth	Authorization code and refresh-token grants with PKCE `S256`.
SDK	No published SDK.
Outbound webhooks	None.

What may change

Docket can expand the REST OAuth operation manifest in a later release. Until then, no task, project, time, or other business REST operation should be assumed to accept a bearer token. Read the live OpenAPI reference for schemas, and use MCP where an agent needs work actions now. Clients should send Docket-Version: 0.1.0 when they need a deliberate assertion and should handle unsupported_api_version. Every public REST response also carries Docket-Revision, the full deployed source revision.

Reliability boundaries

Docket does not send outbound webhooks, publish an SDK, or promise older version routing. MCP resource notifications are best-effort and not replayed. A client must re-read a resource after a notification and must reauthorize after an authority failure. Report a mismatch between these pages and the live API with the response’s Docket-Version, Docket-Revision, request method, and path. Never include an access token.

​What may change

​Reliability boundaries

What may change

Reliability boundaries