Skip to main content
Docket exposes work through an MCP server and a prerelease REST contract. Both run as the person who authorizes the client. The authorization scope narrows that person’s access. It never expands it.

Make your first request

Discover the REST resource, register a native client, and list the organizations you can read.

Connect an AI agent

Connect an MCP client to Docket’s Streamable HTTP endpoint.

REST contract

Read the current public REST boundary and its version headers.
The public API is prerelease. Docket publishes one current compatibility contract, 0.1.0. It does not publish an SDK or send outbound webhooks.

​
Choose an interface

The current REST bearer canary is deliberately narrow: GET /v1/orgs and HEAD /v1/orgs accept an OAuth token with work:read. Other business REST operations remain first-party session routes until their published operation contracts expand this boundary.

​
The work model

An Organization is Docket’s tenant boundary. Teams carry workflow states. Tasks can belong to projects, programs, or initiatives, and a task’s parentTaskId creates a task hierarchy. Personal Athena data belongs under /v1/me/athena, not an organization work route. Use names only where a documented MCP tool accepts them. REST identifiers and fields come from the live OpenAPI reference.

​
Build against the contract

Send Docket-Version: 0.1.0 when a client needs to assert the current contract. Every public REST response identifies the contract and its deployed revision. Read API versions before pinning client behavior, and read Errors before writing retries.