Implementation: DESIGN (server) · Exposure: PUBLIC PREVIEW (contract). The Agency API is not live yet. This page describes the published v0.3 contract so you can review and build against it; details may change before alpha.
The catalog endpoints list what a request can refer to. They are read-only, cursor-paginated and need scope catalog:read. They open with the rest of the API, after a run can survive restart, resume, verify, replay and receipt-backed completion.

Endpoints

All five take the same query parameters:
The registry entries in the examples on this page (capability IDs, model class IDs, profile contents, semantics text) are illustrative. The real entries are whatever the registries return.

List capabilities

The capability registry. A capability is a stable semantic ability with an ID starting cap.. IDs are independent of whichever backend provides the ability. Use them in capabilities.allow and capabilities.deny on a run request and in authority grants.

Parameters

Responses

CapabilityPage of Capability:

Example

List agents

Logical composite agents. An agent is the external identity you address in agent on a request, optionally pinned to a version (allternit-code@v1). The default agent is allternit-code.

Parameters

Responses

AgentPage of Agent:

Example

List model classes

Logical model classes by trust class and locality. This endpoint returns classes, not models. Concrete models are interchangeable components and are never listed. No vendor or model name appears in a default response. Use class IDs (they start mc.) in models.allow_classes and models.deny_classes on a run request. Model or vendor names in those fields are rejected.

Parameters

Responses

ModelClassPage of ModelClass:

Example

trust_classes is the set of data trust classes a class may receive. locality is local, fabric or remote.

List authority profiles

Named authority profiles and the grants each expands to. Three profiles exist: read-only, code-safe and code-write. No bypass equivalent is ever public. Each definition is versioned; a run records the profile as id@version in Run.resolved.authority.

Parameters

Responses

AuthorityProfilePage of AuthorityProfile: filesystem_scope (FilesystemScope): approval_requirements items (ApprovalRequirement): grants items are Grant objects and network is a NetworkPolicy; both are described under Create a run.

Example

List completion criteria

The versioned, extensible completion-criteria registry. Each criterion states, in verifier_semantics, exactly what a pass means, and names the kind of verifier that checks it. Built-in criterion IDs: tests_pass, no_new_regressions, build_passes, typecheck_passes, lint_clean, artifact_exists, requirement_verified, human_review. Refer to a criterion in completion.require by ID (latest version at resolution time) or as {id, version} to pin it. The resolved version is recorded in Run.resolved.completion.

Parameters

Responses

CompletionCriterionPage of CompletionCriterion:

Example