Skip to content
GitmoapAPIBeta
Agentsai-org
GET/groups/{group_id}/ai-org/ritual-runs

The organization's ritual runs, newest first — each with its state, its thread, what it cost

list_ai_ritual_runs
  • ai_org:read
    A token needs the ai_org:read scope: Read an AI organization, its agents, sessions and usageGranted by read_api, write_api.Every operation this scope unlocks
  • Single-resource

    x-gitmoap-isolation: {"kind":"single_or_self_scoped"}

  • Paginated
    Pass the next_token a page returns to get the next one.

For anyone who can see the organization (ai_org.view). A run's recorded outcome is shown only to whoever reads its squad — the board, for a run of the whole organization — and is absent for everyone else. ritual narrows the list to one ritual; keyset-paginated.

Parameters

Path
  • group_idGroupId (string · uuid)The organization's top-level group
Query
  • ritual_keyRitualKey (string)optionalOnly one ritual's runs
  • limitinteger · int64optionalMaximum number of runs, 1-100 (default 50)
  • next_tokenstringoptionalPagination token

Responses

200The runsapplication/json
  • itemsarray of AiRitualRunThe runs.
    • The AiRitualRun schema
    • cost_microsinteger · int64What it spent, in millionths of a dollar with the fee included.
    • kindRitualKindstand_upplanningrefinementreviewretrospectivearchitecture_reviewreleasereplenishmentdigestWhat the ritual does.
    • namestringThe ritual's name when the run was scheduled.
    • ritual_keyRitualKey (string)The ritual's key in the revision.
    • run_idAiRitualRunId (string · uuid)The run.
    • scheduled_forstring · date-timeWhen it was due.
    • started_byAiRitualStartscheduledmanualreleaseWhat started it.
    • stateAiRitualRunStatescheduledrunningcompletedskippedfailedWhere it stands.
    • budget_microsinteger · int64 or nulloptionalThe most it may spend.
    • ended_atstring · date-time or nulloptionalWhen it ended.
    • errorstring or nulloptionalWhy it failed.
    • gate_idAiGateId (string · uuid) or nulloptionalThe gate its outcome waits on, when a person approves it.
    • outcomeobject or nulloptionalWhat it produced, as its facilitator recorded it.
    • phaseAiRitualPhaseparticipantsfacilitatingawaiting_approvalapplyingor nulloptionalWhere a running run is.
    • skip_reasonstring or nulloptionalWhy it was skipped.
    • squad_keySquadKey (string) or nulloptionalThe squad it ran for; absent for the whole organization.
    • started_atstring · date-time or nulloptionalWhen it started.
    • threadstring or nulloptionalIts thread, by address.
  • next_tokenstring or nulloptionalThe next page, when there is one.
200 exampleSynthesized example
{
"items": [
{
"cost_micros": 78,
"kind": "stand_up",
"name": "payments-api",
"ritual_key": "ritual-key-1b15",
"run_id": "25b52782-8527-49fd-995b-301855e498ec",
"scheduled_for": "2026-10-08T19:38:56Z",
"started_by": "scheduled",
"state": "scheduled"
},
{
"cost_micros": 20,
"kind": "stand_up",
"name": "payments-api",
"ritual_key": "ritual-key-4aa7",
"run_id": "d91a2777-530a-4bfe-99d7-bd7901487e1d",
"scheduled_for": "2026-10-09T06:26:22Z",
"started_by": "scheduled",
"state": "scheduled"
}
],
"next_token": "next-token-70a5"
}
400Bad request — a path parameter is not a well-formed value of its typeapplication/json
Error codes
  • BAD_REQUESTThe request is malformed: a parameter or a body field is not a well-formed value of its type
  • errorErrorBody
    • The ErrorBody schema
    • codestringThe coarse category, tied to the status: NOT_FOUND, CONFLICT, INSUFFICIENT_SCOPE. Every error has one; the API reference's error catalogue lists them all.
    • messagestringWhat went wrong, for a person. Written to be read, not parsed: match on reason or code.
    • fieldstring or nulloptionalOn a 400 that refused one field's value, the field, as its JSON path: email, items[0].name. Put the message under that input. Absent on every other error.
    • reasonstring or nulloptionalThe specific code, when the error has one: LAST_ORGANIZATION_OWNER, BRANCH_PROTECTED. The message starts with it too. Match on this when it is present, and on code otherwise.
    • required_scopestring or nulloptionalThe scope the access token was missing, on INSUFFICIENT_SCOPE.
    • violationsanyoptionalPresent on the structured-validation errors (PROVIDER_VALIDATION_FAILED per-node, PIPELINE_VALIDATION_FAILED DAG): a JSON array of the offending elements, so a caller can fix every one in a single round-trip. Absent (omitted) on every other error.
400 exampleSynthesized example
{
"error": {
"code": "code-0063",
"message": "Inline scalar newtypes but keep their brand"
}
}
401Unauthenticated — no credential, or an invalid oneapplication/json
Error codes
  • UNAUTHORIZEDNo credential was sent, or the one sent is invalid, expired or revoked
  • errorErrorBody
    • The ErrorBody schema
    • codestringThe coarse category, tied to the status: NOT_FOUND, CONFLICT, INSUFFICIENT_SCOPE. Every error has one; the API reference's error catalogue lists them all.
    • messagestringWhat went wrong, for a person. Written to be read, not parsed: match on reason or code.
    • fieldstring or nulloptionalOn a 400 that refused one field's value, the field, as its JSON path: email, items[0].name. Put the message under that input. Absent on every other error.
    • reasonstring or nulloptionalThe specific code, when the error has one: LAST_ORGANIZATION_OWNER, BRANCH_PROTECTED. The message starts with it too. Match on this when it is present, and on code otherwise.
    • required_scopestring or nulloptionalThe scope the access token was missing, on INSUFFICIENT_SCOPE.
    • violationsanyoptionalPresent on the structured-validation errors (PROVIDER_VALIDATION_FAILED per-node, PIPELINE_VALIDATION_FAILED DAG): a JSON array of the offending elements, so a caller can fix every one in a single round-trip. Absent (omitted) on every other error.
401 exampleSynthesized example
{
"error": {
"code": "code-ddaf",
"message": "Pin a page's payload to the build that rendered it"
}
}
403Forbidden — the caller's access level or token scope is insufficientapplication/json
Error codes
  • FORBIDDENYou are signed in but may not do this here; reason names the permission or the rule that refused it
  • INSUFFICIENT_SCOPEThe access token lacks the scope this operation needs; required_scope names it
  • PERMISSION_REQUIREDYou need a permission you do not hold here; the message names it
  • errorErrorBody
    • The ErrorBody schema
    • codestringThe coarse category, tied to the status: NOT_FOUND, CONFLICT, INSUFFICIENT_SCOPE. Every error has one; the API reference's error catalogue lists them all.
    • messagestringWhat went wrong, for a person. Written to be read, not parsed: match on reason or code.
    • fieldstring or nulloptionalOn a 400 that refused one field's value, the field, as its JSON path: email, items[0].name. Put the message under that input. Absent on every other error.
    • reasonstring or nulloptionalThe specific code, when the error has one: LAST_ORGANIZATION_OWNER, BRANCH_PROTECTED. The message starts with it too. Match on this when it is present, and on code otherwise.
    • required_scopestring or nulloptionalThe scope the access token was missing, on INSUFFICIENT_SCOPE.
    • violationsanyoptionalPresent on the structured-validation errors (PROVIDER_VALIDATION_FAILED per-node, PIPELINE_VALIDATION_FAILED DAG): a JSON array of the offending elements, so a caller can fix every one in a single round-trip. Absent (omitted) on every other error.
403 exampleSynthesized example
{
"error": {
"code": "code-d1c8",
"message": "Pin a page's payload to the build that rendered it"
}
}
404application/json
Error codes
  • NOT_FOUNDThe resource does not exist — or exists and you cannot see it: a private resource you have no access to answers exactly as an absent one does
  • errorErrorBody
    • The ErrorBody schema
    • codestringThe coarse category, tied to the status: NOT_FOUND, CONFLICT, INSUFFICIENT_SCOPE. Every error has one; the API reference's error catalogue lists them all.
    • messagestringWhat went wrong, for a person. Written to be read, not parsed: match on reason or code.
    • fieldstring or nulloptionalOn a 400 that refused one field's value, the field, as its JSON path: email, items[0].name. Put the message under that input. Absent on every other error.
    • reasonstring or nulloptionalThe specific code, when the error has one: LAST_ORGANIZATION_OWNER, BRANCH_PROTECTED. The message starts with it too. Match on this when it is present, and on code otherwise.
    • required_scopestring or nulloptionalThe scope the access token was missing, on INSUFFICIENT_SCOPE.
    • violationsanyoptionalPresent on the structured-validation errors (PROVIDER_VALIDATION_FAILED per-node, PIPELINE_VALIDATION_FAILED DAG): a JSON array of the offending elements, so a caller can fix every one in a single round-trip. Absent (omitted) on every other error.
404 exampleSynthesized example
{
"error": {
"code": "code-ea28",
"message": "Inline scalar newtypes but keep their brand"
}
}

CLI

gitmoap ai-org list-ai-ritual-runs

  • --group-ididThe organization's top-level group (id or group path)
  • --limitnumberoptionalMaximum number of runs, 1-100 (default 50)
  • --next-tokenstringoptionalPagination token
  • --ritual-keyidoptionalOnly one ritual's runs