[{"data":1,"prerenderedAt":83},["ShallowReactive",2],{"$f23rpqo1ucbrba":3},{"href":4,"title":5,"description":6,"kind":7,"mark":7,"planned":8,"contributors":9,"provenance":7,"express":8,"bridge":8,"html":10,"headings":11},"\u002Fdocs\u002Fapi\u002Fendpoints","Endpoints","Every route an API token can call, by resource, with the scope it needs; and the few that only the portal can.",null,false,[],"\u003Ch2 id=\"reading-this-page\">Reading this page\u003C\u002Fh2>\n\u003Cp>A route's scope is its resource, the first part of its path after \u003Ccode>\u002Fv1\u003C\u002Fcode>, and its level: \u003Ccode>read\u003C\u002Fcode> for a \u003Ccode>GET\u003C\u002Fcode>, \u003Ccode>write\u003C\u002Fcode>\nfor anything else. So a route nested under a task is a task route: starting a run, \u003Ccode>POST \u002Fv1\u002Ftasks\u002F{id}\u002Fruns\u003C\u002Fcode>, needs\n\u003Ccode>tasks:write\u003C\u002Fcode>, not \u003Ccode>runs:write\u003C\u002Fcode>. See \u003Ca href=\"\u002Fdocs\u002Fapi\u002Fauthentication\">Authentication\u003C\u002Fa> for tokens and scopes, and\n\u003Ca href=\"\u002Fdocs\u002Fapi\u002Fconventions\">Conventions\u003C\u002Fa> for errors, pagination and retries.\u003C\u002Fp>\n\u003Cp>Every \u003Ccode>{id}\u003C\u002Fcode> is an id, never a slug. Apart from the catalogue, every route below answers only for your own\nenterprise: an id from another enterprise is a \u003Ccode>404\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Ch2 id=\"tasks\">Tasks\u003C\u002Fh2>\n\u003Cp>A task's definition, its versions and schedule, and the runs, memory and recommendations that belong to it. See\n\u003Ca href=\"\u002Fdocs\u002Fwork\u002Ftasks\">Tasks\u003C\u002Fa>, and \u003Ca href=\"\u002Fdocs\u002Fapi\u002Ftasks\">Tasks over the API\u003C\u002Fa> for the task as JSON.\u003C\u002Fp>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Call\u003C\u002Fth>\n\u003Cth>Scope\u003C\u002Fth>\n\u003Cth>What it does\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Ftasks\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>tasks:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Tasks, a page at a time, with search and filters.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Ftasks\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>tasks:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Create a task, with its first version. A task belongs to a role, not a team: a non-null \u003Ccode>teamId\u003C\u002Fcode> is refused \u003Ccode>400 task_team_removed\u003C\u002Fcode>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Ftasks\u002F{id}\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>tasks:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>The task, its current version and skill, its version list, the teams that have it (\u003Ccode>teams\u003C\u002Fcode>: every team a holder of its role sits on or leads), its webhook, its definition warnings, and your enterprise's own input values (\u003Ccode>inputValues\u003C\u002Fcode>, with \u003Ccode>ignoredInputValues\u003C\u002Fcode> naming any the current version does not take).\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>DELETE \u002Fv1\u002Ftasks\u002F{id}\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>tasks:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Delete the task and every version of it. Its runs are kept. A \u003Ccode>409\u003C\u002Fcode> while it has a run under way.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Ftasks\u002F{id}\u002Fcopy\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>tasks:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Copy it as a new task of your own: send \u003Ccode>name\u003C\u002Fcode> and \u003Ccode>slug\u003C\u002Fcode>, and optionally \u003Ccode>assigneeRole\u003C\u002Fcode>, which is the original's unless you send one.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Ftasks\u002F{id}\u002Fversions\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>tasks:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Every version, newest first.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Ftasks\u002F{id}\u002Fversions\u002F{versionId}\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>tasks:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>One version as it was, with its skill, how many runs used it, and whether it is current.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Ftasks\u002F{id}\u002Fversions\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>tasks:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Publish a new version. Send \u003Ccode>baseVersionId\u003C\u002Fcode>. Add \u003Ccode>&quot;visibility&quot;: &quot;public&quot;\u003C\u002Fcode> (with \u003Ccode>catalog:write\u003C\u002Fcode>) to put that version in the catalogue, listed on the task's role once you have published that role, or \u003Ccode>&quot;private&quot;\u003C\u002Fcode> to withdraw it and record it as left out. Once the task is in the catalogue, every version you save after goes there too, with no \u003Ccode>visibility\u003C\u002Fcode>; \u003Ccode>catalogPublication\u003C\u002Fcode> in the answer says whether it did. See \u003Ca href=\"\u002Fdocs\u002Fapi\u002Ftasks#publishing-to-the-catalogue\">Publishing to the catalogue\u003C\u002Fa>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Ftasks\u002F{id}\u002Fworkflow\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>tasks:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>The current version and its skill, on their own.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>PUT \u002Fv1\u002Ftasks\u002F{id}\u002Fschedule\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>tasks:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Set its schedule. See \u003Ca href=\"\u002Fdocs\u002Fwork\u002Fschedules\">Schedules and webhooks\u003C\u002Fa>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>DELETE \u002Fv1\u002Ftasks\u002F{id}\u002Fschedule\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>tasks:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Remove its schedule.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>PUT \u002Fv1\u002Ftasks\u002F{id}\u002Finput-values\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>tasks:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Replace your enterprise's own input values: \u003Ccode>{ &quot;values&quot;: { &quot;key&quot;: value } }\u003C\u002Fcode>. Every run takes them under what its start gives and over the version's defaults. Works on a clone you cannot edit; refused on a built-in task (\u003Ccode>os_task_immutable\u003C\u002Fcode>), and for a key the version does not declare (\u003Ccode>input_undeclared\u003C\u002Fcode>) or a value of the wrong type (\u003Ccode>input_invalid\u003C\u002Fcode>). See \u003Ca href=\"\u002Fdocs\u002Fwork\u002Ftasks#your-own-input-values\">Your own input values\u003C\u002Fa>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>DELETE \u002Fv1\u002Ftasks\u002F{id}\u002Finput-values\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>tasks:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Clear your enterprise's own input values.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Ftasks\u002F{id}\u002Fruns\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>tasks:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Start a run, with the body as its input.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Ftasks\u002F{id}\u002Fmemory\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>tasks:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>The notes trained on this task, and its training grants.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Ftasks\u002F{id}\u002Fmemory\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>tasks:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Train a note on this task: \u003Ccode>{ &quot;text&quot;: &quot;…&quot; }\u003C\u002Fcode>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Ftasks\u002F{id}\u002Fmemory\u002Fask\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>tasks:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Ask memory as this task would. See \u003Ca href=\"\u002Fdocs\u002Fcontrol\u002Fmemory\">Memory\u003C\u002Fa>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Ftasks\u002F{id}\u002Fmemory\u002Ftrain\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>tasks:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Train a note, or a correction, at a layer this task may write. A person may train the task's team (the first team a holder of its role sits on; \u003Ccode>memory_task_on_no_team\u003C\u002Fcode> when there is none), or the enterprise, here.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Ftasks\u002F{id}\u002Frecommendations\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>tasks:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Self-improvement recommendations for this task.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Cp>A task is given to a role, never to one member. A body that creates, changes, copies or clones a task and still\nnames a member in \u003Ccode>assigneeMemberId\u003C\u002Fcode> is refused with a \u003Ccode>400\u003C\u002Fcode> (\u003Ccode>assignee_member_removed\u003C\u002Fcode>).\u003C\u002Fp>\n\u003Ch2 id=\"runs\">Runs\u003C\u002Fh2>\n\u003Cp>One run of one task: its status, events, log and cost. See \u003Ca href=\"\u002Fdocs\u002Fwork\u002Fruns\">Runs\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Call\u003C\u002Fth>\n\u003Cth>Scope\u003C\u002Fth>\n\u003Cth>What it does\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fruns\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>runs:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Runs, a page at a time, filtered by task, version or status.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fruns\u002F{id}\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>runs:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>One run, its events and gates, its task, what came before and after it, and its cost. \u003Ccode>modelStandsInFor\u003C\u002Fcode> names the model its task asked for when the run used another in its place. \u003Ccode>afterEventId\u003C\u002Fcode> sends only the events since that one.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fruns\u002F{id}\u002Flog\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>runs:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Its full log, once stored. A \u003Ccode>404\u003C\u002Fcode> (\u003Ccode>log_not_found\u003C\u002Fcode>) until then.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fruns\u002F{id}\u002Fos-tool\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>runs:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>A short read: its status, task, input and last eight events, the newest later run on the same work (\u003Ccode>latestRun\u003C\u002Fcode>) and its hand-offs (\u003Ccode>handOff\u003C\u002Fcode>).\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Fruns\u002F{id}\u002Fcancel\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>runs:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Cancel it.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Fruns\u002F{id}\u002Fretry\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>runs:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Retry it as a new run, on the task's current version.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Fruns\u002F{id}\u002Fclear\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>runs:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Take a failed run, or a pipeline that stopped, off Blockers.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Ch2 id=\"blockers\">Blockers\u003C\u002Fh2>\n\u003Cp>What cannot move without someone. See \u003Ca href=\"\u002Fdocs\u002Fwork\u002Fruns#blockers\">Runs\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Call\u003C\u002Fth>\n\u003Cth>Scope\u003C\u002Fth>\n\u003Cth>What it does\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fblockers\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>blockers:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Everything on Blockers, section by section. \u003Ccode>failedPage\u003C\u002Fcode> and \u003Ccode>pageSize\u003C\u002Fcode> page the failed runs.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Fblockers\u002Fclear\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>blockers:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Clear every failed run at once: \u003Ccode>{ &quot;section&quot;: &quot;failed&quot; }\u003C\u002Fcode>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Fblockers\u002Fretry\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>blockers:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Retry every run in \u003Cstrong>Blocked (resumes automatically)\u003C\u002Fstrong>: \u003Ccode>{ &quot;section&quot;: &quot;blocked&quot; }\u003C\u002Fcode>. Answers how many were retried and queued, the runs started, and each run refused with its reason.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Fblockers\u002Fcancel\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>blockers:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Cancel every run in \u003Cstrong>Blocked (resumes automatically)\u003C\u002Fstrong>: \u003Ccode>{ &quot;section&quot;: &quot;blocked&quot; }\u003C\u002Fcode>. Answers how many were cancelled and each run refused with its reason.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Ch2 id=\"waiting\">Waiting\u003C\u002Fh2>\n\u003Cp>Open work nothing is working on: no run live or queued, no decision waiting, nothing on Blockers, and not finished.\nEach row is one issue or pull request, named \u003Ccode>owner\u002Fname#&lt;number&gt;\u003C\u002Fcode>. The same rows as the \u003Cstrong>Waiting\u003C\u002Fstrong> page.\u003C\u002Fp>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Call\u003C\u002Fth>\n\u003Cth>Scope\u003C\u002Fth>\n\u003Cth>What it does\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fwaiting\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>runs:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Every row, longest waiting first, with how its newest run ended: \u003Ccode>{ rows, total }\u003C\u002Fcode>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Fwaiting\u002Ffinish\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>runs:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Mark a row's work finished: \u003Ccode>{ &quot;pipeline&quot;: &quot;owner\u002Fname#123&quot; }\u003C\u002Fcode>. Recorded on its newest run, as you. No issue or pull request is touched. A \u003Ccode>409\u003C\u002Fcode> (\u003Ccode>not_waiting\u003C\u002Fcode>) when the work is not on the list.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Fwaiting\u002Frestart\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>runs:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Restart a row's work at a step: \u003Ccode>{ &quot;pipeline&quot;: &quot;owner\u002Fname#123&quot;, &quot;task&quot;: &quot;&lt;slug&gt;&quot; }\u003C\u002Fcode>. The newest run's own task retries it; another task of its pipeline routes the work there. Returns the new run. A \u003Ccode>409\u003C\u002Fcode> (\u003Ccode>not_waiting\u003C\u002Fcode>) when the work is not on the list.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Ch2 id=\"executions\">Executions\u003C\u002Fh2>\n\u003Cp>The connected runs of more than one task. See \u003Ca href=\"\u002Fdocs\u002Fwork\u002Fexecutions\">Executions\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Call\u003C\u002Fth>\n\u003Cth>Scope\u003C\u002Fth>\n\u003Cth>What it does\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fexecutions\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>executions:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Executions, a page at a time. Closed ones only with \u003Ccode>closed=true\u003C\u002Fcode>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fexecutions\u002Fboard\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>executions:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Every lane of the board in one read.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fexecutions\u002Fcounts\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>executions:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>How many executions and runs are running, queued, waiting (and of those, waiting on a gate) and blocked.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fexecutions\u002F{id}\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>executions:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>One execution: its runs, links and task graph. Any of its run ids works.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Fexecutions\u002F{id}\u002Fcancel\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>executions:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Stop every open run in it.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Fexecutions\u002F{id}\u002Fclose\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>executions:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Take a finished execution off the board.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Fexecutions\u002F{id}\u002Freopen\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>executions:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Put a closed execution back.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Fexecutions\u002Fclose-completed\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>executions:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Close every execution in the Complete lane under the given filters.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Ch2 id=\"gates\">Gates\u003C\u002Fh2>\n\u003Cp>The calls and questions waiting for your decision. See \u003Ca href=\"\u002Fdocs\u002Fcontrol\u002Fgates\">Gates and tool scopes\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Call\u003C\u002Fth>\n\u003Cth>Scope\u003C\u002Fth>\n\u003Cth>What it does\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fgates\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>gates:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Every gate waiting on you, each with \u003Ccode>requestedBy\u003C\u002Fcode>: the person who asked for its work (\u003Ccode>id\u003C\u002Fcode>, \u003Ccode>name\u003C\u002Fcode>, \u003Ccode>avatarUrl\u003C\u002Fcode>), or \u003Ccode>null\u003C\u002Fcode> when nobody of your enterprise did. \u003Ccode>?requestedBy=&lt;userId&gt;\u003C\u002Fcode> lists only that person's, and \u003Ccode>?requestedBy=none\u003C\u002Fcode> only the ones nobody asked for. Each also carries \u003Ccode>people\u003C\u002Fcode>: the people it is for (\u003Ccode>id\u003C\u002Fcode>, \u003Ccode>name\u003C\u002Fcode>), and \u003Ccode>?forPerson=&lt;userId&gt;\u003C\u002Fcode> lists only the ones waiting on that person. Without it, the whole queue returns.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Fgates\u002F{id}\u002Fdecision\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>gates:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Decide one: \u003Ccode>decision\u003C\u002Fcode> is \u003Ccode>approve\u003C\u002Fcode>, \u003Ccode>reject\u003C\u002Fcode> or \u003Ccode>request_changes\u003C\u002Fcode>, with an optional \u003Ccode>note\u003C\u002Fcode>, \u003Ccode>answers\u003C\u002Fcode> for questions, and \u003Ccode>choice\u003C\u002Fcode> (the key of one of the gate's \u003Ccode>choices\u003C\u002Fcode>) on a gate that offers its own.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Fgates\u002Fchat\u002F{chatId}\u002Fdecision\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>gates:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Answer the question a chat is waiting on. Name it with \u003Ccode>gateId\u003C\u002Fcode>, or the newest is answered.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Cp>\u003Ccode>gates:write\u003C\u002Fcode> decides gates, including merges that go live. Grant it deliberately.\u003C\u002Fp>\n\u003Ch2 id=\"chats\">Chats\u003C\u002Fh2>\n\u003Cp>Talking to a member. See \u003Ca href=\"\u002Fdocs\u002Fwork\u002Fchat\">Chat and plans\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Call\u003C\u002Fth>\n\u003Cth>Scope\u003C\u002Fth>\n\u003Cth>What it does\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fchats\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>chats:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Chats, the most recently active first. \u003Ccode>memberId\u003C\u002Fcode> narrows them to one member. A chat opened for a purpose is not listed.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Fchats\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>chats:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Start a chat with a member: \u003Ccode>{ &quot;memberId&quot;: &quot;…&quot; }\u003C\u002Fcode>. Or open one for a single job, \u003Ccode>{ &quot;purpose&quot;: &quot;create_task&quot; }\u003C\u002Fcode>: a new chat with the COO (the member who has held the role longest), or with \u003Ccode>memberId\u003C\u002Fcode> when you send one, whose greeting is already in it. It closes once the task it proposes is applied or rejected. Refused with \u003Ccode>unknown_purpose\u003C\u002Fcode> for any other purpose, and \u003Ccode>no_coo\u003C\u002Fcode> when nobody holds the COO role.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fchats\u002Funread\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>chats:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>How many replies nobody has read yet, in the chats \u003Ccode>GET \u002Fv1\u002Fchats\u003C\u002Fcode> lists.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fchats\u002F{id}\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>chats:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>One chat and its messages, oldest first. \u003Ccode>limit\u003C\u002Fcode> (1 to 200) returns only the newest. Reading it marks it read.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Fchats\u002F{id}\u002Fmessages\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>chats:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Send a message: \u003Ccode>{ &quot;content&quot;: &quot;…&quot; }\u003C\u002Fcode>. The member's reply follows in the chat.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Fchats\u002F{id}\u002Ftool-calls\u002F{callId}\u002Fdecision\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>chats:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Answer a tool call the member is waiting on: \u003Ccode>allow\u003C\u002Fcode>, \u003Ccode>always\u003C\u002Fcode> or \u003Ccode>deny\u003C\u002Fcode>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Fchats\u002F{id}\u002Fclose\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>chats:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Close the chat.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fchats\u002Ftool-grants\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>chats:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>The &quot;Always allow&quot; answers you have given for one member's tools. Send \u003Ccode>memberId\u003C\u002Fcode>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>DELETE \u002Fv1\u002Fchats\u002Ftool-grants\u002F{grantId}\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>chats:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Withdraw one.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Cp>A token's &quot;Always allow&quot; answers are its own, not a person's, and a person's are not the token's.\u003C\u002Fp>\n\u003Cdiv class=\"prose__planned\">\n\u003Cp class=\"prose__flag\">Planned\u003C\u002Fp>\n\u003Ch2 id=\"plans\">Plans\u003C\u002Fh2>\n\u003Cp>When a member can propose a change to the company as a plan (\u003Ca href=\"\u002Fdocs\u002Fwork\u002Fchat\">Chat and plans\u003C\u002Fa>), you will read it\nhere and decide it as a gate:\u003C\u002Fp>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Call\u003C\u002Fth>\n\u003Cth>Scope\u003C\u002Fth>\n\u003Cth>What it does\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fplans\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>plans:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Plans, newest first, filtered by \u003Ccode>status\u003C\u002Fcode>, \u003Ccode>kind\u003C\u002Fcode>, \u003Ccode>chatSessionId\u003C\u002Fcode>, \u003Ccode>planKey\u003C\u002Fcode> or \u003Ccode>producedByRunId\u003C\u002Fcode> (which also matches a plan whose \u003Ccode>planKey\u003C\u002Fcode> is that run's id). Each plan carries \u003Ccode>people\u003C\u002Fcode>, the people its decision is for, and \u003Ccode>?forPerson=&lt;userId&gt;\u003C\u002Fcode> keeps only the plans waiting on that person.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fplans\u002F{id}\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>plans:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>One plan, its items, and the run and gates behind it.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003C\u002Fdiv>\n\u003Ch2 id=\"memory\">Memory\u003C\u002Fh2>\n\u003Cp>What the company has learned. See \u003Ca href=\"\u002Fdocs\u002Fcontrol\u002Fmemory\">Memory\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Call\u003C\u002Fth>\n\u003Cth>Scope\u003C\u002Fth>\n\u003Cth>What it does\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fmemory\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>memory:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>The notes, with search and filters, a page at a time.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Fmemory\u002Ftrain\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>memory:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Train a team or enterprise note. No task is required. \u003Ccode>layer\u003C\u002Fcode> is \u003Ccode>team\u003C\u002Fcode> or \u003Ccode>enterprise\u003C\u002Fcode>; a team train sends \u003Ccode>teamId\u003C\u002Fcode>, and that team must belong to your enterprise.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fmemory\u002Fconstellation\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>memory:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>The Memory page's map: memories and the links between them, with the same search and filters. \u003Ccode>limit\u003C\u002Fcode> is how many memories are read, 500 unless named and at most 1,000. \u003Ccode>status\u003C\u002Fcode> is \u003Ccode>unavailable\u003C\u002Fcode> when memory could not be read.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fmemory\u002Frecall-health\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>memory:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>How often memory could be read over the last 24 hours, by runs and by chat messages.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fmemory\u002F{id}\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>memory:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>One note and its evidence.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Fmemory\u002F{id}\u002Ftombstone\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>memory:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Exclude a note from every future answer.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Fmemory\u002F{id}\u002Frate\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>memory:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Rate a note \u003Ccode>up\u003C\u002Fcode> or \u003Ccode>down\u003C\u002Fcode>, with an optional \u003Ccode>reason\u003C\u002Fcode>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fmemory\u002Freview\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>memory:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>The review queue: conflicts, and notes rated down.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fmemory\u002Freview\u002Fhistory\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>memory:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Every review decision made.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Fmemory\u002Freview\u002F{id}\u002Fresolve\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>memory:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Resolve a conflict by applying a correction: \u003Ccode>correctionId\u003C\u002Fcode> and a \u003Ccode>reason\u003C\u002Fcode>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Fmemory\u002Freview\u002F{id}\u002Fdismiss\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>memory:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Dismiss an item, with a \u003Ccode>reason\u003C\u002Fcode>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Ch2 id=\"recommendations\">Recommendations\u003C\u002Fh2>\n\u003Cp>Self-improvement's proposed changes to a task. See \u003Ca href=\"\u002Fdocs\u002Fcontrol\u002Fself-improvement\">Self-improvement\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Call\u003C\u002Fth>\n\u003Cth>Scope\u003C\u002Fth>\n\u003Cth>What it does\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Frecommendations\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>recommendations:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>The recommendations waiting for a decision; \u003Ccode>taskId\u003C\u002Fcode> narrows them. With \u003Ccode>view=decided\u003C\u002Fcode>, those decided in the last 60 days.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Frecommendations\u002F{id}\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>recommendations:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>One recommendation, in full.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Frecommendations\u002F{id}\u002Fdecision\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>recommendations:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>approve\u003C\u002Fcode> or \u003Ccode>decline\u003C\u002Fcode>, with a \u003Ccode>reason\u003C\u002Fcode> to decline. Takes an \u003Ccode>idempotencyKey\u003C\u002Fcode>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Ch2 id=\"spend\">Spend\u003C\u002Fh2>\n\u003Cp>Caps on what runs may cost, and today's spend. See \u003Ca href=\"\u002Fdocs\u002Fcontrol\u002Fspend\">Spend and models\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Call\u003C\u002Fth>\n\u003Cth>Scope\u003C\u002Fth>\n\u003Cth>What it does\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fspend\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>spend:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Today's spend and runs, and every cap.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>PATCH \u002Fv1\u002Fspend\u002Fcaps\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>spend:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Set the cap on one \u003Ccode>layer\u003C\u002Fcode> and \u003Ccode>layerId\u003C\u002Fcode>. Raising a cap queues paused runs again.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>PATCH \u002Fv1\u002Fspend\u002Fenabled\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>spend:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Turn spend limits on or off: \u003Ccode>{ &quot;enabled&quot;: false }\u003C\u002Fcode>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Ch2 id=\"models\">Models\u003C\u002Fh2>\n\u003Cp>Your model connections and the tiers they resolve to. See \u003Ca href=\"\u002Fdocs\u002Fcontrol\u002Fspend\">Spend and models\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Call\u003C\u002Fth>\n\u003Cth>Scope\u003C\u002Fth>\n\u003Cth>What it does\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fllm\u002Fconnections\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>llm:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Your model connections, without their keys.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>PATCH \u002Fv1\u002Fllm\u002Fconnections\u002F{id}\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>llm:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Rename a connection, describe it, set its priority (0–99, lowest first across providers for its owner), or set a subscription login's plan.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>PATCH \u002Fv1\u002Fllm\u002Fconnections\u002Forder\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>llm:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Reorder all connections for one owner across providers, passing \u003Ccode>connectionIds\u003C\u002Fcode> in order.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fllm\u002Fconnections\u002F{id}\u002Fusage\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>llm:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>A connection's usage.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fllm\u002Fbindings\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>llm:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Whether a model key is connected, for the enterprise or, with \u003Ccode>layer=team\u003C\u002Fcode> or \u003Ccode>layer=member\u003C\u002Fcode> and \u003Ccode>layerId\u003C\u002Fcode>, one team or member.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Fllm\u002Fbindings\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>llm:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Connect a key: \u003Ccode>apiKey\u003C\u002Fcode>, and \u003Ccode>provider\u003C\u002Fcode> (\u003Ccode>openrouter\u003C\u002Fcode>, the default, \u003Ccode>claude\u003C\u002Fcode>, \u003Ccode>openai\u003C\u002Fcode> or \u003Ccode>grok\u003C\u002Fcode>). \u003Ccode>layer\u003C\u002Fcode> (\u003Ccode>enterprise\u003C\u002Fcode>, \u003Ccode>team\u003C\u002Fcode> or \u003Ccode>member\u003C\u002Fcode>) and \u003Ccode>layerId\u003C\u002Fcode> choose its owner.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>DELETE \u002Fv1\u002Fllm\u002Fbindings\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>llm:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Remove a key, named by \u003Ccode>provider\u003C\u002Fcode>, \u003Ccode>layer\u003C\u002Fcode> and \u003Ccode>layerId\u003C\u002Fcode> in the query.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Fllm\u002Fclaude\u002Foauth\u002Fstart\u003C\u002Fcode>, \u003Ccode>…\u002Fcomplete\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>llm:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Connect a Claude login: start returns the address to sign in at, and complete takes the \u003Ccode>code\u003C\u002Fcode> and \u003Ccode>state\u003C\u002Fcode> it gives back.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Fllm\u002Fopenai\u002Foauth\u002Fstart\u003C\u002Fcode>, \u003Ccode>…\u002Fcomplete\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>llm:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Connect a ChatGPT plan: start returns the address to sign in at and a \u003Ccode>state\u003C\u002Fcode>. Complete takes that \u003Ccode>state\u003C\u002Fcode>, and as \u003Ccode>code\u003C\u002Fcode> the whole address the browser was sent to after signing in.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Fllm\u002Fgrok\u002Foauth\u002Fstart\u003C\u002Fcode>, \u003Ccode>…\u002Fcomplete\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>llm:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Connect a SuperGrok plan, the same way.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fllm\u002Ftiers\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>llm:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Which model each tier runs, per provider.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Fllm\u002Ftiers\u002Foverride\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>llm:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Point a tier at another model the provider offers: \u003Ccode>provider\u003C\u002Fcode>, \u003Ccode>tier\u003C\u002Fcode>, \u003Ccode>model\u003C\u002Fcode>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fllm\u002Fmodels\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>llm:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>The models your connections offer, for a task's exact model.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Ch2 id=\"tools\">Tools\u003C\u002Fh2>\n\u003Cp>The systems your members reach, and the connections that let them. See \u003Ca href=\"\u002Fdocs\u002Ftools\">Tools\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Call\u003C\u002Fth>\n\u003Cth>Scope\u003C\u002Fth>\n\u003Cth>What it does\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Ftools\u002Fbindings\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>tools:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Your tool connections, without their secrets. \u003Ccode>layer\u003C\u002Fcode> and \u003Ccode>layerId\u003C\u002Fcode> narrow them. Every connection always carries \u003Ccode>missingSlotActions\u003C\u002Fcode>: the actions its tasks name under a slot it fills that its \u003Ca href=\"\u002Fdocs\u002Fwork\u002Ftool-slots#slot-actions\">action map\u003C\u002Fa> holds no tool for, each with the tool its Tools directory entry maps it to when the connection is on that entry's own server, otherwise an empty string. \u003Ccode>{}\u003C\u002Fcode> means nothing is missing; it is never \u003Ccode>null\u003C\u002Fcode>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Ftools\u002Fbindings\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>tools:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Connect a tool: an MCP server's address and token, or for a system a member operates in a browser, its sites and start page. \u003Ccode>slots\u003C\u002Fcode> and \u003Ccode>slotActions\u003C\u002Fcode> set the slots it fills and its action map; left out, a new connection starts from its directory entry's map.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>PATCH \u002Fv1\u002Ftools\u002Fbindings\u002F{id}\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>tools:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Change a connection, or move it to another layer. Only the owner, or a member the owner allows, may change its \u003Ccode>mustGate\u003C\u002Fcode> list (the tools a task must gate by name). \u003Ccode>slots\u003C\u002Fcode> sets the \u003Ca href=\"\u002Fdocs\u002Fwork\u002Ftool-slots\">tool slots\u003C\u002Fa> it fills, as a whole list (\u003Ccode>[]\u003C\u002Fcode> clears it), and \u003Ccode>slotActions\u003C\u002Fcode> its \u003Ca href=\"\u002Fdocs\u002Fwork\u002Ftool-slots#slot-actions\">action map\u003C\u002Fa>, as a whole object (\u003Ccode>{}\u003C\u002Fcode> clears it; a blank value clears one action); whoever may edit the connection may change either.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>DELETE \u002Fv1\u002Ftools\u002Fbindings\u002F{id}\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>tools:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Remove it.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>PUT \u002Fv1\u002Ftools\u002Fbindings\u002Fbinders\u002F{humanUserId}\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>tools:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Allow a person in your enterprise to connect, change and remove tools on the enterprise itself. Only a signed-in owner may (\u003Ccode>403\u003C\u002Fcode> \u003Ccode>not_enterprise_owner\u003C\u002Fcode>).\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>DELETE \u002Fv1\u002Ftools\u002Fbindings\u002Fbinders\u002F{humanUserId}\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>tools:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Take that allowance away again. Only a signed-in owner may.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Ftools\u002Fbindings\u002F{id}\u002Fsign-ins\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>tools:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>The sign-ins members have saved on a browser connection's sites.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>DELETE \u002Fv1\u002Ftools\u002Fbindings\u002F{id}\u002Fsign-ins\u002F{memberId}\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>tools:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Forget a member's saved sign-in, on one \u003Ccode>site\u003C\u002Fcode> or all of them.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Ftools\u002Foauth\u002Fredirect-uri\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>tools:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>The redirect address to register with a provider for OAuth.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Ftools\u002Foauth\u002Fstart\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>tools:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Start connecting a tool by OAuth. Optional \u003Ccode>authorizeParams\u003C\u002Fcode> supplies extra authorization URL parameters as a string map; reserved security and permission fields are refused. It finishes in the browser of the person who started it, signed in to the portal, so start it there.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Ftools\u002Fexpress\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>tools:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>The \u003Ca href=\"\u002Fdocs\u002Ftools\">Express\u003C\u002Fa> tools: systems Zero Human has set up so that you connect them by signing in. Each has a \u003Ccode>slug\u003C\u002Fcode>, a name and a line on what it does, and may have a \u003Ccode>category\u003C\u002Fcode>, a \u003Ccode>rank\u003C\u002Fcode> (higher first; above 0 is featured) and search \u003Ccode>keywords\u003C\u002Fcode>. A tool's \u003Ccode>imageUrl\u003C\u002Fcode> is a path on this API.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Ftools\u002Fexpress\u002F{slug}\u002Fconnect\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>tools:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Start connecting an Express tool at a \u003Ccode>layer\u003C\u002Fcode> and \u003Ccode>layerId\u003C\u002Fcode>. It answers the address to sign in at and finishes in the browser of the person who started it, like \u003Ccode>oauth\u002Fstart\u003C\u002Fcode>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Cp>A connection on the enterprise itself is the owner's, and the people the owner allows, signed in: anyone else is\nrefused with \u003Ccode>403\u003C\u002Fcode> \u003Ccode>ceo_bind_only\u003C\u002Fcode>. A token, or an app connected to your enterprise, connects tools on a team,\nmember, role or task. Neither can connect, change or remove a connection on the enterprise itself, or change a\n\u003Ccode>mustGate\u003C\u002Fcode> list, even when the person who approved the app owns the enterprise.\u003C\u002Fp>\n\u003Ch2 id=\"teams\">Teams\u003C\u002Fh2>\n\u003Cp>A charter, a lead, and the members on it. See \u003Ca href=\"\u002Fdocs\u002Fcompany\u002Fteams\">Teams and charters\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Call\u003C\u002Fth>\n\u003Cth>Scope\u003C\u002Fth>\n\u003Cth>What it does\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fteams\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>teams:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Every team.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Fteams\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>teams:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Create one: \u003Ccode>name\u003C\u002Fcode>, and optionally \u003Ccode>slug\u003C\u002Fcode>, \u003Ccode>charter\u003C\u002Fcode>, \u003Ccode>leadMemberId\u003C\u002Fcode> and \u003Ccode>concurrentRunLimit\u003C\u002Fcode>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fteams\u002F{id}\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>teams:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>One team, with its \u003Ccode>tasks\u003C\u002Fcode>: the tasks of the roles its members hold.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>PATCH \u002Fv1\u002Fteams\u002F{id}\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>teams:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Change its name, charter, lead or concurrent-run limit.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>DELETE \u002Fv1\u002Fteams\u002F{id}\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>teams:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Delete it. Your last team cannot be deleted.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Fteams\u002F{id}\u002Fmembers\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>teams:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Put a member on the team: \u003Ccode>memberId\u003C\u002Fcode>, and optionally \u003Ccode>roleId\u003C\u002Fcode>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>DELETE \u002Fv1\u002Fteams\u002F{id}\u002Fmembers\u002F{memberId}\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>teams:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Take a member off it.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fteams\u002F{id}\u002Fmembers\u002F{memberId}\u002Froles\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>teams:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>The roles recorded as held by this member on this team: \u003Ccode>{ &quot;roleIds&quot;: [...] }\u003C\u002Fcode>, sorted by id, and \u003Ccode>[]\u003C\u002Fcode> when none is. A role recorded on none of a member's teams is held on every team they sit on or lead; a role recorded on some is held on those only. A run of a task whose role is recorded here works as this team ahead of the member's other teams (the oldest first, when it is recorded on several).\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>PUT \u002Fv1\u002Fteams\u002F{id}\u002Fmembers\u002F{memberId}\u002Froles\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>teams:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Record which of the member's roles they hold on this team: \u003Ccode>{ &quot;roleIds&quot;: [&quot;…&quot;] }\u003C\u002Fcode>. It replaces what was recorded, \u003Ccode>[]\u003C\u002Fcode> clears it, and the answer is the stored \u003Ccode>{ roleIds }\u003C\u002Fcode>. A body that is not a list of role ids is refused \u003Ccode>400 invalid_role_ids\u003C\u002Fcode>, a role the member does not hold \u003Ccode>409 role_not_held\u003C\u002Fcode>, and a team they neither sit on nor lead \u003Ccode>409 not_on_team\u003C\u002Fcode>; an unknown team or member is a \u003Ccode>404\u003C\u002Fcode>. Nothing is recorded when a call is refused.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Ch2 id=\"members\">Members\u003C\u002Fh2>\n\u003Cp>The AI team members, and their inboxes. See \u003Ca href=\"\u002Fdocs\u002Fcompany\u002Fmembers\">Members and inboxes\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Call\u003C\u002Fth>\n\u003Cth>Scope\u003C\u002Fth>\n\u003Cth>What it does\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fmembers\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>members:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Every member.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Fmembers\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>members:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Create one: \u003Ccode>name\u003C\u002Fcode>, and optionally \u003Ccode>email\u003C\u002Fcode> and \u003Ccode>persona\u003C\u002Fcode>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fmembers\u002F{id}\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>members:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>One member.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>PATCH \u002Fv1\u002Fmembers\u002F{id}\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>members:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Change their name, email or persona. \u003Ccode>concurrencyCap\u003C\u002Fcode> sets how many tasks they may run at once, and also needs \u003Ccode>enterprise:write\u003C\u002Fcode>: above 1 only on a plan that allows it (a \u003Ccode>402\u003C\u002Fcode> names the plan), and never above the company's concurrent runs (\u003Ccode>409\u003C\u002Fcode>). The member read returns \u003Ccode>concurrencyCap\u003C\u002Fcode>, \u003Ccode>effectiveConcurrencyCap\u003C\u002Fcode> (what runs on the current plan) and \u003Ccode>maxConcurrencyCap\u003C\u002Fcode>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fmembers\u002F{id}\u002Favatar\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>members:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Their picture, as an image.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>PUT \u002Fv1\u002Fmembers\u002F{id}\u002Favatar\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>members:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Set it: \u003Ccode>{ &quot;dataUrl&quot;: &quot;data:image\u002Fpng;base64,…&quot; }\u003C\u002Fcode>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>DELETE \u002Fv1\u002Fmembers\u002F{id}\u002Favatar\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>members:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Remove it.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Fmembers\u002F{id}\u002Froles\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>members:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Give them a role: \u003Ccode>{ &quot;roleId&quot;: &quot;…&quot; }\u003C\u002Fcode>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>DELETE \u002Fv1\u002Fmembers\u002F{id}\u002Froles\u002F{roleId}\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>members:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Take a role away.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fmembers\u002F{id}\u002Femails\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>members:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Their inbox, a page at a time. \u003Ccode>unreadOnly=true\u003C\u002Fcode> for unread mail only; \u003Ccode>search=\u003C\u002Fcode> for mail whose sender, subject or text contains the words.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fmembers\u002F{id}\u002Femails\u002F{emailId}\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>members:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>One email. Reading it marks it read.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fmembers\u002F{id}\u002Femails\u002F{emailId}\u002Fattachments\u002F{attachmentId}\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>members:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>An attachment, as the file.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Ch2 id=\"roles\">Roles\u003C\u002Fh2>\n\u003Cp>A job: who holds it, and the tasks it runs. See \u003Ca href=\"\u002Fdocs\u002Fcompany\u002Froles\">Roles\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Call\u003C\u002Fth>\n\u003Cth>Scope\u003C\u002Fth>\n\u003Cth>What it does\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Froles\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>roles:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Every role.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Froles\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>roles:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Create one: \u003Ccode>name\u003C\u002Fcode>, and optionally \u003Ccode>slug\u003C\u002Fcode>. A role belongs to no team: a non-null \u003Ccode>teamId\u003C\u002Fcode> is refused \u003Ccode>400 role_team_removed\u003C\u002Fcode>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Froles\u002F{id}\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>roles:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>One role, its holders, the teams it is held on (\u003Ccode>teams\u003C\u002Fcode>, each with its holders) and its tasks.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Froles\u002F{id}\u002Fmembers\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>roles:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Give the role to a member: \u003Ccode>{ &quot;memberId&quot;: &quot;…&quot; }\u003C\u002Fcode>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>DELETE \u002Fv1\u002Froles\u002F{id}\u002Fmembers\u002F{memberId}\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>roles:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Take it from them.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Froles\u002F{id}\u002Ftasks\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>roles:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Point a task at the role: \u003Ccode>{ &quot;taskId&quot;: &quot;…&quot; }\u003C\u002Fcode>. Its runs then go to the role's holders, on any team or none, and every team a holder sits on has it. This publishes no new version.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>DELETE \u002Fv1\u002Froles\u002F{id}\u002Ftasks\u002F{taskId}\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>roles:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Stop the role running it.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Ch2 id=\"the-org\">The org\u003C\u002Fh2>\n\u003Cp>Everything at once: the shape the portal's map draws. See \u003Ca href=\"\u002Fdocs\u002Fcompany\u002Fenterprise\">Enterprise\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Call\u003C\u002Fth>\n\u003Cth>Scope\u003C\u002Fth>\n\u003Cth>What it does\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Forgs\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>orgs:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Your whole organisation as one tree: teams, their members, the roles they hold, and the tasks of each.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Ch2 id=\"enterprise-settings\">Enterprise settings\u003C\u002Fh2>\n\u003Cp>Settings that belong to the whole enterprise. See \u003Ca href=\"\u002Fdocs\u002Fcompany\u002Fenterprise\">Enterprise\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Call\u003C\u002Fth>\n\u003Cth>Scope\u003C\u002Fth>\n\u003Cth>What it does\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fenterprise\u002Fwebhook-secret\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>enterprise:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Which webhook secret is in use and since when: its last characters, never the secret.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Fenterprise\u002Fwebhook-secret\u002Frotate\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>enterprise:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>A new \u003Ca href=\"\u002Fdocs\u002Fapi\u002Fwebhooks\">webhook\u003C\u002Fa> secret, in this response only. The old one stops working at once.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>PUT \u002Fv1\u002Fenterprise\u002Favatar\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>enterprise:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Set the enterprise's picture: \u003Ccode>{ &quot;dataUrl&quot;: &quot;…&quot; }\u003C\u002Fcode>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>DELETE \u002Fv1\u002Fenterprise\u002Favatar\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>enterprise:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Remove it.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fenterprise\u002Fconcurrency\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>enterprise:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>How many runs may run at once.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>PATCH \u002Fv1\u002Fenterprise\u002Fconcurrency\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>enterprise:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Change it: \u003Ccode>{ &quot;concurrentRunLimit&quot;: 3 }\u003C\u002Fcode>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fenterprise\u002Fchat-memory-depth\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>enterprise:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>How much of memory a chat reply reads, and the depths to choose from.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>PATCH \u002Fv1\u002Fenterprise\u002Fchat-memory-depth\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>enterprise:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Change it: \u003Ccode>{ &quot;chatMemoryDepth&quot;: &quot;large&quot; }\u003C\u002Fcode>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fenterprise\u002Fchat-unprompted-turn-limit\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>enterprise:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>How many turns in a row a chat member may take on its own, with nobody writing: 5 unless changed, 0 when off.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>PATCH \u002Fv1\u002Fenterprise\u002Fchat-unprompted-turn-limit\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>enterprise:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Change it: \u003Ccode>{ &quot;limit&quot;: 2 }\u003C\u002Fcode>, a whole number from 0 (off) to 20.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fenterprise\u002Fmetrics\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>enterprise:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>The company's own metrics, the ones that belong to no single team.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>PATCH \u002Fv1\u002Fenterprise\u002Fmetrics\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>enterprise:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Set them: \u003Ccode>{ &quot;metrics&quot;: [&quot;…&quot;] }\u003C\u002Fcode>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fenterprise\u002Fchangelog-repo\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>enterprise:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>The repository that hosts your public changelog: \u003Ccode>{ &quot;changelogRepo&quot;: &quot;owner\u002Fname&quot; }\u003C\u002Fcode>, or \u003Ccode>null\u003C\u002Fcode> when you have none.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>PATCH \u002Fv1\u002Fenterprise\u002Fchangelog-repo\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>enterprise:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Name, change or clear it: \u003Ccode>{ &quot;changelogRepo&quot;: &quot;owner\u002Fname&quot; }\u003C\u002Fcode> or a clone address without credentials, or an empty value or \u003Ccode>null\u003C\u002Fcode> for none. An address with sign-in details in it is refused with \u003Ccode>400 invalid_changelog_repo\u003C\u002Fcode>. See \u003Ca href=\"\u002Fdocs\u002Ftools\u002Fworkspaces\">Workspaces\u003C\u002Fa>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fenterprise\u002Fauto-update-cloned-tasks\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>enterprise:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Whether quiet updates to a catalog task apply by themselves to your linked clones of it: \u003Ccode>{ &quot;autoUpdateClonedTasks&quot;: true }\u003C\u002Fcode>. On unless you turned it off. See \u003Ca href=\"\u002Fdocs\u002Fcompany\u002Fenterprise#settings-on-the-enterprise-page\">Enterprise\u003C\u002Fa>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>PATCH \u002Fv1\u002Fenterprise\u002Fauto-update-cloned-tasks\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>enterprise:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Turn it on or off: \u003Ccode>{ &quot;autoUpdateClonedTasks&quot;: false }\u003C\u002Fcode>, the body \u003Ccode>{ autoUpdateClonedTasks: boolean }\u003C\u002Fcode> with a JSON \u003Ccode>true\u003C\u002Fcode> or \u003Ccode>false\u003C\u002Fcode>. Anything else, \u003Ccode>&quot;true&quot;\u003C\u002Fcode> or \u003Ccode>1\u003C\u002Fcode> included, is refused with \u003Ccode>400 invalid_auto_update_cloned_tasks\u003C\u002Fcode> and the stored value is kept. Answers with what is now stored.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fenterprise\u002Fsuccessor-outcomes\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>enterprise:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>The outcomes a task's next step can wait on, \u003Ccode>succeeded\u003C\u002Fcode> first: \u003Ccode>{ &quot;outcomes&quot;: [&quot;succeeded&quot;, &quot;failed&quot;, …] }\u003C\u002Fcode>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Cp>No token can manage API tokens, whatever \u003Ccode>enterprise:write\u003C\u002Fcode> would otherwise reach: see \u003Ca href=\"#portal-only\">Portal only\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2 id=\"catalogue\">Catalogue\u003C\u002Fh2>\n\u003Cp>The teams, roles and tasks you can take into your enterprise. See \u003Ca href=\"\u002Fdocs\u002Fcommunity\u002Ftasks\">Task directory\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Call\u003C\u002Fth>\n\u003Cth>Scope\u003C\u002Fth>\n\u003Cth>What it does\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fcatalog\u002Ftasks\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>catalog:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>The catalogue, a page at a time.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fcatalog\u002Ftasks\u002F{id}\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>catalog:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>One task in it, with its current version in full: the skill on \u003Ccode>currentVersion.skillMd\u003C\u002Fcode>, and its tools, guardrails, gates, successors, inputs, spend and version number. \u003Ccode>currentVersion\u003C\u002Fcode> has the same shape as reading that version on its own.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fcatalog\u002Ftasks\u002F{id}\u002Fversions\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>catalog:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Every version of that task, newest first, each marked \u003Ccode>current\u003C\u002Fcode> or not. No skill text.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fcatalog\u002Ftasks\u002F{id}\u002Fversions\u002F{versionId}\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>catalog:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>One version as it was, with its skill and whether it is current: compare the version you cloned with the current one.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Fcatalog\u002Ftasks\u002F{id}\u002Fclone\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>catalog:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Install it, linked to the original. It names no team: it keeps the original's role, every team a holder of that role sits on has it, and it keeps the \u003Ca href=\"\u002Fdocs\u002Fwork\u002Fschedules#schedules-on-a-clone\">schedule\u003C\u002Fa> its publisher runs it on.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Fcatalog\u002Ftasks\u002F{id}\u002Fcopy\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>catalog:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Copy it as your own task: \u003Ccode>name\u003C\u002Fcode> and \u003Ccode>slug\u003C\u002Fcode>, and optionally \u003Ccode>assigneeRole\u003C\u002Fcode>, which is the original's unless you send one. It keeps the original's \u003Ca href=\"\u002Fdocs\u002Fwork\u002Fschedules#schedules-on-a-clone\">schedule\u003C\u002Fa>, as a clone does.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fcatalog\u002Fteams\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>catalog:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Portable team templates, a page at a time, including their charter, teammate role grouping, roles and tasks with tools and approvals. Each task says whether your enterprise already holds a clone of it (\u003Ccode>clonedByMe\u003C\u002Fcode>, \u003Ccode>cloneStale\u003C\u002Fcode>, \u003Ccode>cloneOnVersion\u003C\u002Fcode>).\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fcatalog\u002Fteams\u002F{id}\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>catalog:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>One team template in full. No publisher member identities or credentials.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Fcatalog\u002Fteams\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>catalog:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Publish explicit portable content: \u003Ccode>name\u003C\u002Fcode>, \u003Ccode>slug\u003C\u002Fcode>, \u003Ccode>description\u003C\u002Fcode>, \u003Ccode>charter\u003C\u002Fcode> and \u003Ccode>teammates: [{roleIds: [...] }]\u003C\u002Fcode>. Every role must already be a public catalog role and appear in exactly one teammate slot. Requires your plan's catalog publishing flag.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Fcatalog\u002Fteams\u002F{id}\u002Fclone\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>catalog:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Adopt atomically: \u003Ccode>name\u003C\u002Fcode>, \u003Ccode>slug\u003C\u002Fcode>, optional \u003Ccode>teammateNames\u003C\u002Fcode> (one per slot), \u003Ccode>taskIds\u003C\u002Fcode> (defaults to all eligible tasks) and \u003Ccode>moneyCentsDay\u003C\u002Fcode> (defaults to 1000). Creates a private team, fresh teammates and identities on your domain, roles and linked tasks. A role you already have with a template role's slug (your COO's \u003Ccode>coo\u003C\u002Fcode>, for example) is reused, not refused, and so is a task you already have (of the same original or slug): only the tasks you lack are installed, under their own slugs (\u003Ccode>reusedTaskIds\u003C\u002Fcode> in the response lists the rest). Every plan can clone, within its existing member limit. Each task it installs keeps its \u003Ca href=\"\u002Fdocs\u002Fwork\u002Fschedules#schedules-on-a-clone\">schedule\u003C\u002Fa>: the one the template suggests, else the one its publisher runs it on, listed as \u003Ccode>schedules\u003C\u002Fcode> on \u003Ccode>GET \u002Fv1\u002Fcatalog\u002Fteams\u002F{id}\u003C\u002Fcode>. Without \u003Ccode>schedules\u003C\u002Fcode> in the body, they start on in order while your plan has room, and the rest arrive paused. \u003Ccode>schedules: [{ &quot;taskId&quot;: &quot;…&quot;, &quot;enabled&quot;: true, &quot;cron&quot;: &quot;…&quot; }]\u003C\u002Fcode> says which to switch on, at the time you send. Every other one arrives paused, one you send switched off at the \u003Ccode>cron\u003C\u002Fcode> you send with it, and switching on more than your plan has room for is refused with nothing installed. A task that needs an input with no default (such as \u003Ccode>repo\u003C\u002Fcode>) is listed too, with \u003Ccode>missingInputs: [&quot;repo&quot;]\u003C\u002Fcode>, and the review's \u003Ccode>requiredInputs\u003C\u002Fcode> lists each such input once, with the \u003Ccode>taskIds\u003C\u002Fcode> that need it. \u003Ccode>inputValues: { &quot;repo&quot;: &quot;acme\u002Fapp&quot; }\u003C\u002Fcode> gives each value to every new task that declares the field (a task you already had keeps its own values), so its schedule can be switched on. A key no cloned task declares, or a value of the wrong type, is refused with \u003Ccode>400\u003C\u002Fcode> and nothing installed, and switching on a schedule whose input you did not send is refused with \u003Ccode>400\u003C\u002Fcode> \u003Ccode>input_required\u003C\u002Fcode>. A schedule you send switched off counts as left off on purpose; send it with \u003Ccode>&quot;leftOff&quot;: false\u003C\u002Fcode> when it is off only because its input has no value yet, and it arrives paused at its \u003Ccode>cron\u003C\u002Fcode>, waiting for that input. The response's \u003Ccode>pausedSchedules\u003C\u002Fcode> names every schedule the clone left paused: \u003Ccode>[{ &quot;taskId&quot;: &quot;…&quot;, &quot;cron&quot;: &quot;…&quot;, &quot;missingInputs&quot;: [&quot;repo&quot;], &quot;leftOff&quot;: false }]\u003C\u002Fcode>, with the new task's id, the inputs it still lacks and whether you left it off on purpose; it is \u003Ccode>[]\u003C\u002Fcode> when every carried schedule is on. A schedule paused only for want of an input reads as waiting (\u003Ccode>schedule.waiting.missingInputs\u003C\u002Fcode>) on \u003Ccode>GET \u002Fv1\u002Ftasks\u002F{id}\u003C\u002Fcode> and in \u003Ccode>waitingSchedules\u003C\u002Fcode> on \u003Ccode>GET \u002Fv1\u002Fteams\u002F{id}\u003C\u002Fcode> (each with \u003Ccode>missingFields\u003C\u002Fcode>, the \u003Ccode>key\u003C\u002Fcode>, \u003Ccode>label\u003C\u002Fcode> and \u003Ccode>type\u003C\u002Fcode> of every input it lacks): set the value with \u003Ccode>PUT \u002Fv1\u002Ftasks\u002F{id}\u002Finput-values\u003C\u002Fcode>, then switch the schedule on with its normal save. Setting the value never switches it on by itself. \u003Ccode>slotFills: [{ &quot;slot&quot;: &quot;codehost&quot;, &quot;bindingId&quot;: &quot;…&quot; }]\u003C\u002Fcode> fills each \u003Ca href=\"\u002Fdocs\u002Fwork\u002Ftool-slots\">tool slot\u003C\u002Fa> the tasks declare with one of your connections, without rewriting the tasks. \u003Ccode>GET \u002Fv1\u002Fcatalog\u002Fteams\u002F{id}\u002Freview\u003C\u002Fcode> lists the slots, with the connections that fill them and could.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Fcatalog\u002Froles\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>catalog:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Publish your own role's portable name and slug: \u003Ccode>{ &quot;sourceRoleId&quot;: &quot;…&quot; }\u003C\u002Fcode>. Its tasks are your public tasks that run as it: the ones already public join it now, and each one you publish later joins it then. Private tasks are never published implicitly. The role's live KPIs are copied onto it, unsigned and with no readings, so a team clone gives them to the roles it creates; a KPI read from a task in the catalogue names that catalogue task, and any other source is left blank. Requires your plan's catalog publishing flag.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fcatalog\u002Fshare\u002Froles\u002F{roleId}\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>catalog:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>How one of your roles stands with the catalogue: each task that runs as it (\u003Ccode>listed\u003C\u002Fcode>, \u003Ccode>outdated\u003C\u002Fcode> when it has a newer version than the catalogue holds, \u003Ccode>elsewhere\u003C\u002Fcode> when public but not on this role, \u003Ccode>unlisted\u003C\u002Fcode> when nobody has decided, \u003Ccode>left_out\u003C\u002Fcode>), the entries still on the role whose tasks moved, were retired or are gone (\u003Ccode>strays\u003C\u002Fcode>), how many \u003Ccode>changes\u003C\u002Fcode> the listing is behind on, and how many of the role's live KPIs travel with it (\u003Ccode>kpis\u003C\u002Fcode>).\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fcatalog\u002Fshare\u002Fteams\u002F{teamId}\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>catalog:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>What sharing one of your teams would publish: its roles, each with \u003Ccode>included\u003C\u002Fcode> and its own listing as above, the roles its entry names that the team no longer has, how many \u003Ccode>changes\u003C\u002Fcode> the entry is behind on, the team KPIs that travel (\u003Ccode>kpis\u003C\u002Fcode>), and the role KPIs the included roles bring (\u003Ccode>roleKpis\u003C\u002Fcode>).\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Fcatalog\u002Fshare\u002Fteams\u002F{teamId}\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>catalog:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Share one of your teams, or bring its entry up to date. \u003Ccode>roleSlugs\u003C\u002Fcode> names the roles that go; the rest are left out, and stay left out when you share again without \u003Ccode>roleSlugs\u003C\u002Fcode>. Optional \u003Ccode>name\u003C\u002Fcode>, \u003Ccode>description\u003C\u002Fcode>, \u003Ccode>kindOfWork\u003C\u002Fcode> and \u003Ccode>businessFunction\u003C\u002Fcode>. Each included role you have in the catalogue takes its live KPIs as they stand now, replacing the set it carried, so a changed target updates and a withdrawn KPI goes; a left-out role keeps the set it has.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fcatalog\u002Froles\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>catalog:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>The catalogue's public roles, a page at a time, each with the public tasks on it. Each task says whether your enterprise already holds a clone of it (\u003Ccode>clonedByMe\u003C\u002Fcode>, \u003Ccode>cloneStale\u003C\u002Fcode>, \u003Ccode>cloneOnVersion\u003C\u002Fcode>), as \u003Ccode>GET \u002Fv1\u002Fcatalog\u002Ftasks\u003C\u002Fcode> does.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fcatalog\u002Froles\u002F{id}\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>catalog:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>One role and the public tasks on it, each with your enterprise's clone state.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Fcatalog\u002Froles\u002F{id}\u002Fclone\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>catalog:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Install the role and the tasks on it, linked to the originals, in one go: \u003Ccode>{ &quot;teamId&quot;: &quot;…&quot; }\u003C\u002Fcode>, the team its holder is seated on. Add \u003Ccode>createTeammate: true\u003C\u002Fcode>, optional \u003Ccode>teammateName\u003C\u002Fcode>, \u003Ccode>taskIds\u003C\u002Fcode> and \u003Ccode>moneyCentsDay\u003C\u002Fcode> to create a fresh teammate holding the role, with a daily cap (1000 cents by default). Omitting \u003Ccode>createTeammate\u003C\u002Fcode> keeps the original role-only behavior. \u003Ccode>memberId\u003C\u002Fcode> instead gives the role to a teammate you already have, who joins the team and keeps their own cap; it cannot be sent with \u003Ccode>createTeammate\u003C\u002Fcode>. A role you already have with that slug is reused, whatever team its holders sit on. Deprecated tasks are skipped. A task you already have (of the same original or slug) is reused, not copied, and listed in \u003Ccode>reusedTaskIds\u003C\u002Fcode>; only the tasks you lack are installed, under their own slugs, so cloning the role onto a second team installs nothing again. \u003Ccode>roleHeldOnTeam\u003C\u002Fcode> in the response says whether anyone on the team holds the role: until someone does, the team does not have its tasks. Each task it installs keeps the \u003Ca href=\"\u002Fdocs\u002Fwork\u002Fschedules#schedules-on-a-clone\">schedule\u003C\u002Fa> its publisher runs it on; a reused task keeps its own. \u003Ccode>slotFills\u003C\u002Fcode> fills the tasks' \u003Ca href=\"\u002Fdocs\u002Fwork\u002Ftool-slots\">tool slots\u003C\u002Fa> as for a team.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Cp>Team and role adoption preserves each task's approval gates and version provenance. Credentials, AI accounts,\nmemory, publisher member identities and run history stay behind. Of the publisher's schedules only the cron comes\nacross, never their timezone or run input: see \u003Ca href=\"\u002Fdocs\u002Fwork\u002Fschedules#schedules-on-a-clone\">Schedules on a clone\u003C\u002Fa>.\nSelected workflows cannot omit a task\nthey hand off to unless your enterprise already has it. A refusal rolls back the whole adoption. Repeating a\nsuccessful adoption is refused rather than creating a second team or duplicate tasks. Inspect your teams and tasks\nafter a timeout before retrying. A clone needs your own AI connection and any listed tool connections to run.\u003C\u002Fp>\n\u003Cp>Actual team content and the new team sizes per plan are configured separately; these routes do not manufacture\ncustomer templates or change plan policy.\u003C\u002Fp>\n\u003Ch2 id=\"webhooks\">Webhooks\u003C\u002Fh2>\n\u003Cp>What your enterprise's \u003Ca href=\"\u002Fdocs\u002Fapi\u002Fwebhooks\">webhooks\u003C\u002Fa> received, and replaying it.\u003C\u002Fp>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Call\u003C\u002Fth>\n\u003Cth>Scope\u003C\u002Fth>\n\u003Cth>What it does\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fwebhooks\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>webhooks:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Deliveries, a page at a time.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fwebhooks\u002F{id}\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>webhooks:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>One delivery: its request, response, and what followed.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Fwebhooks\u002F{id}\u002Freplay\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>webhooks:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Replay it. Send an \u003Ccode>idempotencyKey\u003C\u002Fcode>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Ch2 id=\"without-a-token\">Without a token\u003C\u002Fh2>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Call\u003C\u002Fth>\n\u003Cth>What it does\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fhealth\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Whether the API is up, and the version it runs.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Fwebhooks\u002F{enterprise}\u002Ftasks\u002F{task}\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Start a run of a task, named by its slug. Authenticated by your webhook secret. See \u003Ca href=\"\u002Fdocs\u002Fapi\u002Fwebhooks\">Webhooks\u003C\u002Fa>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>POST \u002Fv1\u002Fwebhooks\u002F{enterprise}\u002Fgates\u002F{gateId}\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Decide a gate. Authenticated by your webhook secret.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fpublic\u002Fexpress-tools\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>The \u003Ca href=\"\u002Fdocs\u002Ftools\">Express\u003C\u002Fa> tools every enterprise is offered: each one's \u003Ccode>slug\u003C\u002Fcode>, name, description, \u003Ccode>category\u003C\u002Fcode>, how it signs in, the text of its page, an example task when it has one, and the path of its logo.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>GET \u002Fv1\u002Fpublic\u002Fexpress-tools\u002F{slug}\u002Fimage\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>An Express tool's logo, as an image.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Ch2 id=\"portal-only\">Portal only\u003C\u002Fh2>\n\u003Cp>These belong to a person signed in to the portal, not to a credential. No API token can use them, whatever its\nscopes:\u003C\u002Fp>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Routes\u003C\u002Fth>\n\u003Cth>What they are\u003C\u002Fth>\n\u003Cth>A token is refused with\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>\u003Ccode>\u002Fv1\u002Fenterprise\u002Fapi-tokens\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Creating, rotating, changing and revoking API tokens.\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>403\u003C\u002Fcode> \u003Ccode>api_token_cannot_manage_tokens\u003C\u002Fcode>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>\u002Fv1\u002Fenterprise\u002Fconnections\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Apps connected to your enterprise, and revoking them.\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>403\u003C\u002Fcode> \u003Ccode>api_token_cannot_manage_connections\u003C\u002Fcode>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>\u002Fv1\u002Fusers\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>The people in your enterprise, what each may reach, and each person's own mailbox address. Owners only.\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>403\u003C\u002Fcode> \u003Ccode>api_token_scope\u003C\u002Fcode>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>\u002Fv1\u002Fenterprises\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Creating an enterprise, and the pictures of the enterprises a person belongs to.\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>403\u003C\u002Fcode> \u003Ccode>api_token_scope\u003C\u002Fcode>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>\u002Fv1\u002Fauth\u002Fme\u003C\u002Fcode>, \u003Ccode>\u002Fv1\u002Fauth\u002Fenterprise\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Who is signed in, and which enterprise their session is in.\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>403\u003C\u002Fcode> \u003Ccode>api_token_scope\u003C\u002Fcode>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>\u002Fv1\u002Fconsent\u002Fenterprises\u003C\u002Fcode>, \u003Ccode>…\u002Fmembers\u003C\u002Fcode>, \u003Ccode>…\u002Fapprove\u003C\u002Fcode>, \u003Ccode>…\u002Fdecline\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>The screen where a person connects an app to an enterprise.\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>403\u003C\u002Fcode> \u003Ccode>api_token_scope\u003C\u002Fcode>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Cp>A token with no \u003Ccode>enterprise\u003C\u002Fcode> scope is refused \u003Ccode>api_token_scope\u003C\u002Fcode> on the first two, before it gets that far. Signing\nin and out (the rest of \u003Ccode>\u002Fv1\u002Fauth\u003C\u002Fcode>) happens in a browser, with a session a token does not have.\u003C\u002Fp>\n",[12,16,19,22,25,28,31,34,37,41,44,47,50,53,56,59,62,65,68,71,74,77,80],{"id":13,"text":14,"level":15,"planned":8},"reading-this-page","Reading this page",2,{"id":17,"text":18,"level":15,"planned":8},"tasks","Tasks",{"id":20,"text":21,"level":15,"planned":8},"runs","Runs",{"id":23,"text":24,"level":15,"planned":8},"blockers","Blockers",{"id":26,"text":27,"level":15,"planned":8},"waiting","Waiting",{"id":29,"text":30,"level":15,"planned":8},"executions","Executions",{"id":32,"text":33,"level":15,"planned":8},"gates","Gates",{"id":35,"text":36,"level":15,"planned":8},"chats","Chats",{"id":38,"text":39,"level":15,"planned":40},"plans","Plans",true,{"id":42,"text":43,"level":15,"planned":8},"memory","Memory",{"id":45,"text":46,"level":15,"planned":8},"recommendations","Recommendations",{"id":48,"text":49,"level":15,"planned":8},"spend","Spend",{"id":51,"text":52,"level":15,"planned":8},"models","Models",{"id":54,"text":55,"level":15,"planned":8},"tools","Tools",{"id":57,"text":58,"level":15,"planned":8},"teams","Teams",{"id":60,"text":61,"level":15,"planned":8},"members","Members",{"id":63,"text":64,"level":15,"planned":8},"roles","Roles",{"id":66,"text":67,"level":15,"planned":8},"the-org","The org",{"id":69,"text":70,"level":15,"planned":8},"enterprise-settings","Enterprise settings",{"id":72,"text":73,"level":15,"planned":8},"catalogue","Catalogue",{"id":75,"text":76,"level":15,"planned":8},"webhooks","Webhooks",{"id":78,"text":79,"level":15,"planned":8},"without-a-token","Without a token",{"id":81,"text":82,"level":15,"planned":8},"portal-only","Portal only",1794928142701]