Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.xenovia.io/llms.txt

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

​
Govern agent behavior without rebuilding your stack

Xenovia gives you a control layer for agent runtimes. Route model traffic through an OpenAI-compatible proxy, or gate non-LLM actions with the Xenovia SDK, and enforce policy without rewriting your application architecture.

Quickstart

Route one request through Xenovia, confirm trace headers, and add your first policy.

Choose an integration

Pick the right path for OpenAI SDK, LangChain, LlamaIndex, Vercel AI SDK, Agents SDK, or the Xenovia SDK.

Policies and Approvals

Write request and response policies in Rego, then decide when to block, redact, or escalate.

Trace and investigate

Track each call with session IDs, tool activity, policy outcomes, and remediation context.

​
Two ways to integrate

Proxy mode

Point any OpenAI-compatible client at Xenovia. You keep your prompts, tools, and framework code, while Xenovia adds policy evaluation, provider routing, session tracking, and traces.

Python SDK

Gate tool calls, file writes, API requests, or database mutations that happen outside the model call itself. Use execute() for one-off checks or @guard() to wrap functions.

​
What Xenovia adds

  • Request-stage and response-stage Rego policy enforcement
  • Session-linked traces with turn counts and request headers for correlation
  • Central provider credentials and upstream routing
  • Tool visibility, block reasons, and escalation handoff points
  • Optional semantic intent checks before risky requests proceed
1

1. Pick your path

Start with Getting Started to decide between proxy mode and SDK mode.
2

2. Prove the plumbing

Run the Quickstart and confirm a trace appears for a known request.
3

3. Add controls

Move to Policies and Approvals and start with one rule that blocks or redacts something concrete.
4

4. Expand observability

Use Traces and Remediation to group sessions, add custom properties, and investigate drift.

​
What Xenovia records

  • Request and response bodies, token counts, latency, and TTFT
  • Session ID, session turn, session path, and trace linkage
  • Tool names, arguments, and results when present
  • Policy outcomes, reasons, and intent actions
  • Custom request metadata via X-Xenovia-Property-* headers