Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.idun-group.com/llms.txt

Use this file to discover all available pages before exploring further.

Every idun-agent-standalone deployment exposes the same HTTP API. This reference is rendered from a snapshot of the live FastAPI app’s OpenAPI spec (refreshed manually on releases — see Spec source below), so every shape on every page matches what the server returns at that snapshot.

​
Authentication

The auth model is pinned at boot via IDUN_ADMIN_AUTH_MODE. Pick the row that matches your deployment.

None

Default for local dev. Every endpoint is open. No header, no cookie, no token.

Password

Admin endpoints need a signed session cookie. Set it with POST /admin/api/v1/auth/login. Runtime stays open.

SSO

Admin and runtime accept an OIDC Bearer token. Runtime falls back to X-Idun-User-Id for trace scoping.
Full setup, claim mapping, and edge cases on the auth overview.

​
Surfaces

The 42 endpoints group into seven surfaces. Pick one from the left sidebar.

Runtime

The chat surface. POST /agent/run (AG-UI streaming), session listing, graph introspection, health.

Agent configuration

CRUD on the live agent config: model, prompts, tools. Writes hot-reload the engine.

Auth & SSO

Password login and logout, OIDC provider config, GET /auth/me.

Dashboard

Aggregated counters and traffic series sourced from the local trace store.

Integrations & tools

MCP servers, prompts, guardrails, integrations. Everything a tool needs to be reachable from the agent.

Observability

Wire and unwire external exporters: Phoenix, Langfuse, OTel collectors.

Traces

Read, filter, and delete locally-captured traces and spans.

​
A first call

The shortest “hello world”: stream a single message through the AG-UI protocol. 
curl -N -X POST http://localhost:8000/agent/run \
  -H "Content-Type: application/json" \
  -H "Accept: text/event-stream" \
  -d '{
    "threadId": "demo-thread",
    "runId": "demo-run",
    "messages": [
      { "role": "user", "content": "Say hello in one sentence." }
    ]
  }'
Each event is a JSON line; pipe through jq to follow the run. Drill into POST /agent/run on the left for the full event vocabulary.

​
Spec source

This reference reflects a snapshot of GET /openapi.json from a running standalone. To refresh the spec before a release, run curl -sS http://localhost:8000/openapi.json > docs/standalone/openapi.json and commit the result; the API pages regenerate automatically on the next deploy.

Standalone overview

How the standalone wraps the engine, what ships in the wheel, when to use it.
Last modified on May 22, 2026