> ## 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.

# API Introduction

> Programmatic access to proxy management, traces, policies, and approval workflows.

The Xenovia API provides programmatic access to runtime governance operations: creating and managing proxies, reading trace data, evaluating policies, and integrating operator approval workflows into external systems.

<CardGroup cols={2}>
  <Card title="Proxy management" icon="hexagon-nodes">
    Create proxies, configure providers, attach policies and intent definitions.
  </Card>

  <Card title="Trace retrieval" icon="file-chart-column">
    Pull trace records for audits, debugging, and incident response. Filter by session, policy outcome, intent action, or time range.
  </Card>

  <Card title="Approval workflows" icon="user-check">
    Integrate operator approvals into existing review systems. Confirm or deny escalated actions programmatically.
  </Card>

  <Card title="Policy management" icon="gavel">
    Upload and update Rego policies per proxy. Policies take effect within the 5-minute Redis cache TTL.
  </Card>
</CardGroup>

## Base URL

```
https://api.xenovia.io/api/v1
```

## Design

* **REST** — resource-oriented endpoints with predictable HTTP semantics.
* **JSON** — all request and response bodies are `application/json`.
* **Bearer auth** — `Authorization: Bearer xe_...` on every request.
* **Traceable** — every mutating operation produces an audit record tied to the acting API key.

## Common operations

* Create and manage proxy inventory with owners, environments, and declared scope.
* Fetch runtime-derived agent and tool identities observed under a proxy.
* Read trace details: policy decisions, intent scores, session turns, tool call records.
* Upload or update Rego policies per proxy (request-stage and response-stage independently).
* Confirm or deny pending escalations from the approval queue.
* Query aggregate metrics: block rates, intent score distributions, session volumes.

See [Authentication](/api-reference/authentication) for token handling and [Errors and Limits](/api-reference/errors-and-limits) for status codes and retry guidance.