Agents
Agents are the coding agents a task can run with besides the built-in ones: your organization's own, registered from a GitHub repo or installed from the ACP registry, and the catalog connectors Jaah publishes. Register, edit, refresh and delete agents, turn catalog connectors on or off, and list what a task may pick.
List catalog connectors
Lists every active catalog connector with whether your organization has turned it on, plus any withdrawn connector it had turned on, marked by its `status`.
Turn off a catalog connector
Turns a catalog connector off for your organization. Requires permission to edit agents across the organization (403); an unknown connector returns 404. Returns the connector.
Turn on a catalog connector
Turns a catalog connector on for your organization, so its tasks can pick it; turning on one already on changes nothing. Requires permission to edit agents across the organization (403); a withdrawn connector returns 409 and an unknown one 404. Returns the connector.
List the agent marketplace
Lists every agent your organization can use: the built-in ones, its own agents, the catalog connectors and its registry installs. Each entry names the personas it takes, a cost band from Jaah's price list (built-in agents only), how many of your live nodes can run it, whether the agent router may pick it and why not, and its outcome-ledger profile. Every figure is Jaah's own measurement, never one an agent's publisher reported, and the list is readable whatever the plan.
List ACP registry agents
Lists the agents in the ACP registry that your plan includes, each with whether it can be installed (and the reason when not) and the version your organization has installed, if any. Returns 403 when your plan includes no registry agent.
Install an ACP registry agent
Installs an agent from the ACP registry as one of your organization's agents, pinned to the registry's current version. Requires the Org Owner or Org Admin role; returns 201 with the agent, 404 for an unknown entry, 409 when it or an agent of the same name is already installed, and 422 when the entry cannot be installed or your plan does not include it.
List agents
Lists your organization's own agents, ordered by name, followed by the catalog connectors it has turned on. Every endpoint in this area except List agent choices returns 403 while Agents is not on the organization's plan.
Register agent
Registers an agent from a GitHub repo, sub-path and ref, read with the caller's own GitHub connection and pinned to the resolved commit; `env` sets its environment variables. Returns 201 with the agent, or 422 listing each reason in `errors` when the repo cannot be read or is not a valid agent, in which case nothing is stored.
List agent choices
Lists the entries of the console's agent picker: the built-in agents the organization has an account for and whose provider its plan runs, then its active agents and enabled catalog connectors whose entry its plan includes (SDK agent, or the registry agent itself). With `persona`, an agent that cannot run that persona comes back with `disabled` true and the reason.
Delete agent
Deletes an agent no task or project uses. Returns 204 with no body, or 409 when tasks or projects still use it, naming their counts and listing the first of each the caller can see; disable the agent instead.
Update agent
Changes an agent's `ref` or `subpath` (re-read at once; a failure is a 422 that changes nothing), its `status` (`active` or `disabled`), its whole `env` map, or a registry agent's `key_account_id`. A registry agent's ref, sub-path and environment cannot change (422). Only whoever registered the agent, or someone who may edit agents across the organization, may change it (403); returns the updated agent.
Refresh agent
Re-reads the agent's ref from its repo and re-validates it, moving the agent to the ref's current commit. A failure is recorded on the agent as `resolve_error` and returned as a 422 while the last good version keeps running; a registry agent returns 409, since it is pinned to its registry version.