Skip to main content
GET
Read workspace readiness

Authorizations

Authorization
string
header
required

Your Reason API key from Settings › API keys. New keys use reason_; legacy ara_ keys remain accepted. Keys are capability-scoped: run, mcp:read, mcp:write, secrets:read, secrets:write, sessions:read, sessions:debug, knowledge:read, memory:read, memory:write, skills:read, skills:write, repos:read, repos:write, reviews:read, reviews:write, deployment:read, analytics:read, org:read, org:write, attachments:read, attachments:write, guardrails:read, guardrails:write, network:read, network:write, automations:read, automations:write, agent_auth:read. network:read and network:write are opt-in, excluded from default keys. network:read reads the saved workspace network policy; network:write replaces custom allowed hosts and requires a current organization owner/admin. Legacy project PATCH requests containing network_allowed_hosts also require network:write plus their existing run scope and project management permission; saved project hosts do not affect current session egress. Only owners/admins can mint or manage keys with network:write; keys cannot grant themselves more authority. See /docs/network-policies for replacement semantics and runtime applicability. mcp:write manages MCP server configuration only; it does not authorize remote MCP-tool execution. sessions:read reads sessions, including the assistant, reasoning and tool activity in their events. sessions:debug is privileged: only for organization owners/admins, it expands session events to the full diagnostic projection (diagnostic event kinds, status text and raw event metadata).

Response

Readiness snapshot with per-check limits and actions.

checked_at
string
required
resource_mode
enum<string>
required
Available options:
legacy-personal,
consolidated
access
object
required
funding
object
required

Read-only API/Loop funding preflight, not a model, provider-capacity, seat, spend-limit or compute reservation.

github
object
required

Recorded workspace installations and this caller's own connection only. Target repository permissions must be verified separately; no connection is refreshed or repaired.

devices
object
required

Only this caller's personal Devices, not teammates' inventory or cloud-computer capacity. Optional for cloud work.