LLM And Agent APIs

These APIs cover AI Orchestration chat, tool execution, approvals, autonomous agents, A2A delegation, the LLM gateway, and OpenAI-compatible proxy routes.

Route Map

Chat And Tool Execution

Approvals

Agents And A2A

The repository also ships Production Feature Agent blueprints that compile their prompts, built-in skills, schedule, service identity, and Eden-only tool scope into ordinary POST /api/v1/llm/agents requests. They use these same lifecycle, run, log, metrics, and A2A routes.

Investigation Runs

Agent Gateway

Gateway Governance And Proxy

OpenAI-compatible proxy routes are mounted separately:

Gateway Key Governance Configuration

Gateway key create and update requests can include built-in policy fields, key-specific custom terms, and template-backed lookup configuration.

{
  "name": "document-summary-gateway",
  "endpoint_id": "local-ollama",
  "model_allowlist": ["llama3.1"],
  "custom_pii_terms": [
    {
      "term": "SIU-INV-4419",
      "label": "investigation_id",
      "action": "redact"
    }
  ],
  "pii_lookup_templates": [
    {
      "template_id": "lookup-customer-account-pii",
      "input_fields": [
        {
          "name": "account_id",
          "source": "user_message_regex",
          "pattern": "(?i)account(?: id)?[:# ]+(?P<value>[A-Z0-9-]+)",
          "required": true,
          "value_type": "string"
        }
      ],
      "records_path": "",
      "redaction_fields": [
        {
          "path": "/full_name",
          "label": "customer",
          "action": "redact"
        }
      ],
      "max_rows": 1,
      "error_mode": "block"
    }
  ],
  "work_metadata": {
    "workflow": "document_summary"
  }
}

pii_lookup_templates references saved Gateway Read templates. Lookup-derived values are request-scoped and are not persisted back into organization or key dictionaries. Telemetry records safe identifiers, statuses, and counts only.

Governance Feature Kinds

The generic feature-record API accepts these feature kinds:

Configuration And Catalogs

Credentials

Per-user database credentials are mounted outside the LLM API:

Credential read and rotation responses never return a password and carry Cache-Control: no-store. Rotation activates a replacement credential already provisioned on the target database; Eden does not change the target account. Clients should reuse a stable rotation_id when retrying so DBOS returns the same durable workflow instead of scheduling another rotation.

See Per-User Database Credentials And Rotation for the complete registration and rotation workflow.

Projects, Conversations, And Notifications

Admin LLM APIs