AI and agents
Connect an external agent to Whagons or understand the built-in Whagons assistant.
Whagons supports two related but distinct agent experiences.
| Experience | Who runs it? | How it gets access | What it uses |
|---|---|---|---|
| External agent | A third-party agent, automation, or agent platform | A user approves a discoverable auth.md claim | Short-lived whg_agent_… token and the public v1 API |
| Whagons assistant | Whagons inside the signed-in product | The current Whagons user session | Curated product actions, navigation, exports, and data tools |
Do not treat the built-in assistant's curated action catalog as a public REST API. External agents use the documented /api/v1/* endpoints.
auth.md access
Discover and implement Whagons user-claimed agent authentication.
User claim flow
Understand the consent screen, code, tenant selection, and common errors.
Call the API
Use a delegated agent token with the same v1 API as an integration key.
Assistant capabilities
See the complete in-product capability map and curated action families.
Which path should I use?
Use a Settings-issued API key when a known server-to-server integration needs durable access and an administrator can manage key rotation.
Use agent access when an autonomous tool starts the connection and a human Whagons user should explicitly approve that agent for one tenant.
Use the built-in assistant when the user is already working in Whagons and wants natural-language help with visible work, setup, analysis, files, or navigation.
Current status
The v1 task API and Settings-issued keys are the primary public integration surface. The auth.md agent flow is available as a beta while its discovery, credential renewal, and management experience continue to be refined.
Start with auth.md agent access, or go directly to the API key quickstart.