Documentation

Debug in the browser. Record in code. Gate in CI.

Use the docs as one loop: debug a trace in the browser, install the recorder in code, capture traces automatically, then turn findings into CI release gates.

Start Here

Run the full adoption path in three steps before diving deeper into policy and enterprise controls.

1. Debug in browser

Start with a real failing trace in the debugger and confirm the failing step plus next fix.

2. Install the recorder

Use pip, npm, or go get once, then capture traces automatically from real code paths.

3. Gate in CI

Promote stable traces into CI checks so reliability failures block risky releases.

env
# Install the recorder for your stack
pip install sepurux
npm install @sepurux/recorder
go get github.com/sepurux/go-recorder@latest

SEPURUX_API_BASE_URL=https://app.sepurux.dev/api/backend
SEPURUX_UI_BASE_URL=https://app.sepurux.dev
SEPURUX_API_KEY=<project_api_key>
SEPURUX_PROJECT_ID=<project_uuid>
bash
curl -X POST https://app.sepurux.dev/api/backend/v1/traces \
  -H "Content-Type: application/json" \
  -H "X-API-Key: $SEPURUX_API_KEY" \
  -H "X-Project-Id: $SEPURUX_PROJECT_ID" \
  -d '{
    "trace_version": "0.1",
    "source": "docs.quickstart",
    "task": {"name": "refund_flow"},
    "events": [
      {"type": "model", "name": "triage_refund", "input": {"order_id": "ord_123"}}
    ]
  }'

Reference Resources

Direct links for implementation detail, rollout support, and the public integration surface.

API Reference Guide

Public request examples, headers, and the core endpoints most teams need to wire traces, runs, and CI.

Guide

Full Explorer Access

The full interactive explorer and raw OpenAPI schema live inside the authenticated product workspace so project-scoped and administrative routes stay protected.

In-app
Need help designing a rollout path for your team? Visit Join the waitlist or email support@sepurux.com.