Stop Agent
Authorizations
Clerk session JWT for the web app (active organization required), or an organization-scoped SEAOTTER access key (so_…) from POST /api/v1/api-keys for programmatic / docs try-it / MCP use. The same so_… value is both Authorization: Bearer so_… and SEAOTTER_API_KEY.
Path Parameters
Response
Successful Response
Agent UUID
pending | provisioning | running | paused | stopped | error | deleting
pending, provisioning, running, paused, stopped, error, deleting Kubernetes namespace (agent-{id})
hobby, startup, business, enterprise, starter, pro Documented subset of agent.config returned on AgentOut (extra keys allowed).
- AgentConfigPublic
- Config
Cloud partner id
Data-plane region
Role-aware env metadata. Members: empty. Admins/API keys: key → gsm | configured (never plaintext or full gsm: resource ids).
"https://my-hermes-abcd1234.agents.seaotter.dev"
True while the Hermes dashboard may be briefly unavailable after a pod restart (secrets, Restart, credential rotate). Poll GET /agents/{id}/dashboard-reachability until clear.
True while a credential rotation is still converging onto the live Hermes gateway. Prefer waiting / retrying talk rather than assuming the revealed key is already accepted.

