Skip to main content
GET
Get agent

Authorizations

Authorization
string
header
required

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

agent_id
string<uuid>
required

Response

Successful Response

id
string<uuid>
required

Agent UUID

name
string
required
status
enum<string>
required

pending | provisioning | running | paused | stopped | error | deleting

Available options:
pending,
provisioning,
running,
paused,
stopped,
error,
deleting
namespace
string
required

Kubernetes namespace (agent-{id})

resource_plan
enum<string>
required
Available options:
hobby,
startup,
business,
enterprise,
starter,
pro
config
AgentConfigPublic · object
required

Documented subset of agent.config returned on AgentOut (extra keys allowed).

created_at
string<date-time>
required
updated_at
string<date-time>
required
cloud
string
default:gcp

Cloud partner id

region
string
default:us-central1

Data-plane region

env_vars
Env Vars · object

Role-aware env metadata. Members: empty. Admins/API keys: key → gsm | configured (never plaintext or full gsm: resource ids).

error_message
string | null
dashboard_url
string | null
Example:

"https://my-hermes-abcd1234.agents.seaotter.dev"

api_url
string | null
dashboard_handoff_url
string | null
dashboard_username
string | null
hostname
string | null
dashboard_warming
boolean
default:false

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.

credential_rotation_pending
boolean
default:false

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.