NOLGIANOLGIADocs

Agent

The operator model

On this page
  1. Provision and deprovision
  2. Configure
  3. Desired state
  4. Observe

You provision one NOLGIA Agent per account with POST /agent, which requires an active Studio, Team or Enterprise subscription. Starter and Pro plans cannot provision an agent. Configure its environment, read its desired state and inspect the work it creates.

The NOLGIA Agent and the work it creates
The NOLGIA Agent and the work it creates

Provision and deprovision #

GET /agent reads your agent; POST /agent provisions it asynchronously. DELETE /agent deprovisions it and revokes its access token.

Method Path What it does
GET /agent Get the current user's NOLGIA Agent, if provisioned.
POST /agent Provision the current user's NOLGIA Agent (one per account; requires an active subscription).
DELETE /agent Deprovision the current user's NOLGIA Agent and revoke its access token.
GET /agent/usage Credits spent and jobs created by the current user's agent.
GET /agent/manifest Return the complete desired state for the current user's agent as a single, server-computed source of truth: its installed abilities (with pinned versions), its available presets, and the pinned CLI + runtime versions. This is the one list a pod-side reconciler materializes. Increment 1 enumerates what already exists in the DB (abilities + presets + version pins); the CLI-embedded skills and the base-image skill library are a separate increment pending an object-store decision.
GET /agent/config List the agent's custom configuration entries. Secret values are redacted (empty string) in the response.
PUT /agent/config Upsert custom configuration entries (e.g. TELEGRAM_BOT_TOKEN) injected into the agent pod's environment. A running agent is flipped back to pending_deploy so the deploy pipeline applies the change (typically within ~5 minutes).
POST /agent/dashboard/ticket Mint a short-lived ticket URL for embedding the agent's live dashboard.
POST /agent/heartbeat Report the agent pod's materialized state (installed ability versions) upstream.

Configure #

Desired state #

Endpoint What it tells you
GET /agent/manifest Desired abilities with pinned versions, available presets, and pinned CLI and runtime versions.
POST /agent/heartbeat The pod reports installed ability versions; compare installed_version with latest_version on GET /agent/abilities to observe drift.

Observe #

GET /agent/usage reports credits spent and jobs created. POST /agent/dashboard/ticket creates a 120-second ticket for the embedded dashboard and accepts browser sessions only.

Field Type Required Description
credits_spent integer Yes Total credits consumed by generations the agent's token created.
jobs_total integer Yes Number of jobs created with the agent's token.
recent_jobs array of Job Yes