Salanor DocsAegis · APS-1

Aegis integration guide

Documentation for your developers embedding Salanor in production apps — signed AI activity, policy on tool calls, and human approvals.

SDKs: TypeScript (@salanor/aegis) is full-featured for pilots. Python and Go clients support sign + ingest — see SDK overview.

Typical integration flow

  1. Org admin creates ingest API key + agent signing key in the console.
  2. Your service installs @salanor/aegis and stores secrets in your env.
  3. Each agent workflow uses a trace_id; LLM steps call signAndIngest.
  4. Outbound tools (Stripe, CRM, etc.) use wrapFetch for policy + audit.
  5. Operators review traces and exports in the console — not in your repo.

Quick links

Production endpoints