Core Loop

The core product loop is the recommended API path for Agent hosts:


observe -> guide -> agent action -> feedback -> measure

Endpoint	Call it when
POST /v1/observe	The host has memory, execution evidence, validation output, or handoff state to record.
POST /v1/guide	The Agent needs governed context before acting.
POST /v1/feedback	The host knows whether exposed memory helped or hurt.
POST /v1/measure	The host wants a product effect report for the loop.

Shared fields

Field	Meaning
`tenant_id`	Logical tenant boundary. Local installs usually use `default`.
`scope`	Project, repo, workspace, or task boundary. Keep it stable across observe and guide.
`run_id`	Execution session identifier.
`task_signature`	Stable task or workflow identity.
`consumer_agent_id` / `agent_id`	Agent identity for context and attribution.
`consumer_team_id` / `team_id`	Shared lane for planner, worker, verifier, reviewer, and handoff flows.

The Runtime adds defaults for local development, but production-quality host loops should pass stable identity explicitly.

SDK base


import { createAionisClient } from "@aionis/sdk";
 
const aionis = createAionisClient({
  baseUrl: "http://127.0.0.1:3001",
  scope: "checkout-migration",
});

HTTP base


curl -s http://127.0.0.1:3001/health

Start with POST /v1/observe.