---
title: "One regime's status"
method: GET
path: "/v2/workspaces/{id}/regimes/{regime}"
tags: ["Regimes"]
---

# One regime's status

`GET /v2/workspaces/{id}/regimes/{regime}`

## Request

- Base URL: `https://api.infolang.ai`
- URL: `https://api.infolang.ai/v2/workspaces/{id}/regimes/{regime}`
- Auth: one of:
  - HTTP bearer
  - HTTP bearer
  - HTTP bearer

The single-id read a picker captions its options with. `status: null` means nothing has DEFINED this regime — a regime named only by a scope link that arrived first is LATENT, not absent (A5), which is why that case is a 200 and not a 404. `disclosure_policy` is the policy PARSED out of the regime's name; `null` next to a name you believe says `[disclosure:required]` means the guarantee is not in force.

Requires the `coord:read` scope. Accepts all three lanes: a session JWT (bounded by the caller's role on this workspace) or an `il_*` machine credential whose own scope set, workspace set and validity window cover it — both ceilings apply and neither can raise the other, so a credential carrying `coord:read` is still refused where the role does not permit it.

A credential with no scope record resolves to `LEGACY_DEFAULT`, which does NOT include `coord:read` — mint a key with it explicitly (`POST /v2/workspaces/{id}/keys`).

## Path parameters

- `id` string, required
- `regime` string, required

## Response `200`

The regime's phase, lineage and parsed disclosure policy

- object
  - `regime` string, required
  - `status` 'scheduled' | 'active' | 'ended' | 'void', nullable
  - `name` string, nullable
  - `window` object, nullable
    - `from` string, nullable
    - `to` string, nullable
  - `contested` boolean
  - `lost_adjudication` boolean
  - `parents` string[]
  - `children` string[]
  - `fold_size` number
  - `disclosure_policy` string, nullable, required

## Other responses

- `401`: Missing/invalid credential, or `credential_expired` — the credential is outside its `[not_before, expires_at)` window and must be replaced
- `403`: `insufficient_scope` — the credential's own scope set, or the caller's role on this workspace, does not cover the scope this route requires (the missing scope is named in the message). Or `forbidden` — the credential is not scoped to this workspace, or holds no grant on it
- `501`: The regime verbs are not compiled into this deployment (`kernel-verbs` is off upstream)

---

[API](https://skmtc.dev/infolang/apis/infolang-api.md) · [All operations](https://skmtc.dev/infolang/apis/infolang-api/llms.txt) · [OpenAPI document](https://skmtc.dev/infolang/apis/infolang-api/revisions/d04bf6de72c8?raw)