# Whagons for Agents

Whagons is a tenant-scoped operations platform centered on workspaces and tasks.

## Start here

- Human and developer docs: https://docs.whagons.com/docs
- Full public docs index: https://docs.whagons.com/llms.txt
- Full public documentation corpus: https://docs.whagons.com/llms-full.txt
- OpenAPI 3.1: https://docs.whagons.com/openapi/whagons-v1.json
- Agent integration guide: https://docs.whagons.com/docs/agents

## Authentication

Whagons supports two external credentials:

1. Settings-issued API keys beginning with whg_live_. A tenant admin creates these in Settings > Integrations and gives the secret to the integration.
2. User-claimed agent tokens beginning with whg_agent_. Discover this flow at https://gon.whagons.com/auth.md and https://gon.whagons.com/.well-known/oauth-protected-resource.

Never ask a user to paste a credential into a public conversation or log it.

## REST API

- Current API base: https://cvx-share.whagons.com/api/v1
- Read scope: ext:read
- Task write scope: ext:tasks:write
- Most requests require tenantId.
- Resolve current workspace, user, category, status, priority, team, template, tag, and spot IDs before writing.
- Credentials act on behalf of a Whagons user and inherit that user's current permissions and visibility.

Supported v1 work includes reference-data reads; visible task reads; task creation, updates, and soft deletion; comments; assignments; tags; logs; approvals; and acknowledgments.

## Safety

- Stay within the credential's tenant and scopes.
- Do not assume a name or ID is shared between tenants.
- Do not retry a consequential write blindly after an ambiguous failure.
- Treat 401 as a credential, expiry, scope, or tenant mismatch.
- Do not claim an operation succeeded until the API confirms it.
- Use the API and agent changelogs before depending on beta behavior.