Organizations
GET /v0/organizations returns the calling key’s workspace with counts and limits. A workspace owns its projects, keys and resources; it is distinct from a human console user.
Registration modes
Autonomous registration starts unverified, with no outgoing recipients enabled and no paid-resource access. The response contains its initial capabilities and limits. Its stable registration secret permits safe replay of the same creation request.
Human-email signup permits outgoing email only to the supplied human address until that workspace is verified.
POST /v0/agent/verify consumes the delivered OTP and removes that recipient gate. Verification does not replace the plan’s limits, billing readiness, permissions or spending controls.
A verified human can use Claim an agent workspace and submit the registration key privately. The console holds its new owner credential server-side. The original agent key remains restricted until the owner explicitly grants additional access through appropriate keys and workspace controls.
See agent registration, API keys, billing and budgets.
Workspace moves
POST /v0/organizations/move is unavailable for durable production workspaces and returns 409 organization_move_unsupported. A target workspace ID alone never grants ownership; the legacy in-memory demonstration path requires valid full source and destination credentials. Use the claim flow for an autonomous workspace instead of attempting to migrate data or bypass registration limits.