SDK
Evigauge SDK Reference
Instrument your agents so Evigauge can reconstruct why they did what they did.
This document covers the Python SDK (opexia-trace), the TypeScript /
OpenTelemetry route, framework adapters, and the opexia CLI.
Companion documents: REST API Reference · MCP & Claude Code Plugin
Naming: Evigauge vs opexia
The product is Evigauge (formerly OpexIA). The rename is a brand change only.
Every identifier in code stays opexia. Renaming any of these breaks
installation, imports, auth, or span validation:
| Surface | Value — do not rename |
|---|---|
| PyPI package | opexia-trace |
| Python import | import opexia.trace |
| Console scripts | opexia, pxcore-mcp, pxcore-proxy |
| Auth header | x-opexia-api-key |
| Ingest host | ingest.opexia.dev |
| Span attributes | opexia.* |
| Env vars | OPEXIA_API_KEY, OPEXIA_TRANSPORT, … |
| Local WAL | .opexia-wal/spans.jsonl |
| Config files | .opexia/shipcheck.yml, .opexia/agentmap.lock |
Language support at a glance
| Python | TypeScript / JavaScript | |
|---|---|---|
| Package | pip install opexia-trace | No Evigauge npm package — use OpenTelemetry JS |
| Setup | opexia.trace.init(...) | OTLP/JSON exporter + attribute helpers |
| Decorator / wrapper | @observe, ReasoningTrace | withOpexiaTrace() |
| Auto-instrumentation | ✅ patches LLM clients | ➖ manual, or OTel auto-instrumentation |
| Crash-safe WAL | ✅ built in | ➖ rely on BatchSpanProcessor |
CLI (shipcheck, audit, live) | ✅ | ✅ (the CLI is language-agnostic) |
There is no
@opexia/tracenpm package, and none is planned — TypeScript instruments through native OpenTelemetry JS exporting OTLP/JSON. The helper module in TypeScript setup does the rest.