dogabot exposes a scoped REST API at https://api.dogabot.com/api/v1 for Pro and Institutional accounts.
Authenticate with an API key (dbk_live_…), not a Clerk browser session.
This site is the reference: every path here is on the API-key allowlist. Create a key in the app, then use curl, CI, or desk tools. MCP install stays on GitHub and Learn.
export DOGABOT_API_KEY=dbk_live_...
curl -H "Authorization: Bearer $DOGABOT_API_KEY" https://api.dogabot.com/api/v1/me
| Plan | Keys | Access | Rate limit |
|---|---|---|---|
| Pro | Up to 3 active | Read scopes. Terminal place/cancel needs write:terminal and feat:terminal. |
60 requests / minute / key |
| Institutional | Up to 10 active | Read plus write when ops enables feat:api:write on the account. |
300 requests / minute / key |
Each key can restrict callers to public IPs or CIDRs. Empty allowlist means any IP.
Restrictions apply to REST and MCP. Do not use 127.0.0.1.
API keys cannot mint other keys, read or write exchange secrets, call ops-only or checkout routes,
act as another user, or force-close automations. Those stay on the signed-in webapp.
MCP is served at https://mcp.dogabot.com/mcp, not as a REST path on api.dogabot.com.