Ω-API Integrations

Use the surface you want — dashboard, API, exports, or hooks. Every route reaches the same Ω-API judge.

The interface changes. The judge does not.

Available now

HTTP API. every language, over HTTP · Bearer key.

GitHub examples / HTTP runner. call the judge from any language over HTTP · on GitHub →

Python SDK. pip install omega-api · PyPI → · source →

JavaScript SDK. npm install @dailui/omega-api · npm → · source →

MCP server. give agents the judge as one tool · npx @dailui/omega-api-mcp · npm → · source →

OpenTelemetry instrumentation. put the judge’s decisions into your observability stream · pip install omega-api-otel · PyPI → · source →

Dashboard. the visual surface for reading the signal.

CSV / JSON export. join the process shape to your own logs.

observed_event hook. send the observed outcome back to Ω-API — it anchors the session after the fact.

Webhook alerts. where your plan enables them.

Quickstart

Create an account and get an API key, then send one call per turn. API keys are scoped by environment where enabled.

curl -X POST https://omega.dailui.com/api/v1/judge.php \
  -H "Authorization: Bearer <your-api-key>" \
  -H "Content-Type: application/json" \
  -d '{
    "session_id": "sess_123",
    "input": "customer message",
    "output": "agent reply"
  }'

The response carries the decision and the gate to act on:

{
  "turn_id": "t_1",
  "decision": "PROCEED",
  "reason_family": "ok",
  "side": "coupling",
  "operator": { "gate": { "action": "release", "release_original": true } }
}

decision is one of PROCEED · CLARIFY · STOP. In Operator mode, apply operator.gate.action before releasing the response. The session fingerprint (csm_shape_rle) and grade come from the desk or the export, not the per-turn reply.

One rule for every integration

Every integration is a thin client over the same call. There is no client-side session state to manage — the judge keeps it server-side, per session_id. You send the turn, you read the gate, you act. That is the whole contract.

Register, then meter

Every route is the same: register → key → judge → meter. Even from the command line, you register.

Your first 100 judgments are free. After that, billing applies. Same judge, same meter — whichever surface you use.

The dashboard

The dashboard is one way to read the signal, not the product.

The dashboard proves the signal. Integrations distribute it.

One judge behind every surface

The signal is produced by Ω-API’s proprietary geometric judge. The interface is open. The judging method is proprietary.

How the judge works →

Get your API key.

First 100 judgments are free.

Get your API key