Skip to main content
The Studio CLI (studio / @chatatp/studio CLI) talks to the Dashboard API under /dapi/. These routes use a user session from studio auth login, not a Developer API key.
/dapi/ is the builder/dashboard surface. Integrations that send messages as an end user should use the Developer API (/v1/) instead.

Base URL

Same host as the Developer API:

Auth

After studio auth login, the CLI stores a token and sends:
Auth endpoints themselves accept email/password or OAuth and return that token.

Path catalog

Copied from src/chatatp_studio/cli/endpoints.py and src/cli/endpoints.ts. Trailing slashes are required.

Auth and users

Teams

Platforms

Knowledge bases

Memory

Scheduling

Assistant / Copilot

Agents, MCP, HTTP API tools, LLM

Several /dapi/ collection/detail paths are inferred from REST convention in the SDK endpoint registry (agents, MCP, HTTP API tools, LLM). Confirm verbs against the backend before publishing playground pages for those routes.