Skip to main content
v1 is operator-dogfooded scope. The public quickstart flow below describes the intended developer experience but assumes you have an existing tenant + API key. Self-serve tenant provisioning is a post-v1 conversation.

​
1. Get an API key

Tenant + key creation today is operator-driven via the worktruck-cli binary. Once you have a key, it looks like: 
wt_<32-char-base64>
API keys are tenant-scoped and member-scoped. They carry the same access level the linked member has.

​
2. Hit the API

The API root is https://api.worktruck.app. Authentication is a bearer header: 
curl https://api.worktruck.app/api/v1/people \
  -H "Authorization: Bearer wt_..."
A successful response stamps X-Worktruck-Backend: go on every reply — confirms you reached the Go service rather than a stale Rust pod.

​
3. Write your first row

curl https://api.worktruck.app/api/v1/people \
  -X POST \
  -H "Authorization: Bearer wt_..." \
  -H "Content-Type: application/json" \
  -d '{
    "kind": "person",
    "display_name": "Alice MacGregor",
    "given_name": "Alice",
    "family_name": "MacGregor"
  }'
The response carries the new Person’s id, plus the audit fields (created_at, updated_at, etc.).

​
4. The other surfaces

The same operations are also available via:
  • MCP at https://mcp.worktruck.app/mcp — JSON-RPC 2.0 over HTTP. Use this when wiring up an Anthropic-side agent through the Managed Agents path.
  • CLI via go install github.com/worktruckapp/worktruck-go/cmd/worktruck-cli@latest. Profile-based; first run prompts for the key.

​
Where to next

  • Concepts — the entity model and how everything relates.
  • API Reference — full endpoint catalog (coming soon).