ΛXIØM Lens

ΛXIØM Lens

Governed AI calls. Receipts your product can act on.

AXIØM Lens sits between your application and every model it calls, governing the request, returning a branchable decision, and recording what happened.

Get API keySee a governed decision

OpenAI-compatible  ·  Anthropic-compatible  ·  Local MCP tools

Product evidence

See the decision, not just the answer.

POST /v1/govern returns an AxiomGovernanceDecision the host app can branch on: decision, reason, hidden_axis, required_next_action, and system_effect.

Instrument panel
POST /v1/govern

Proposed next action

Promote the release candidate to production.

AxiomGovernanceDecision

require_verification

The proposed production promotion crosses a proof boundary without rollback evidence.

decisionrequire_verification
hidden_axismotion_without_progress
required_next_actionhold_and_request_evidence
system_effectreturn to human
Decision object
AxiomGovernanceDecision
01

decision

require_verification

02

reason

The proposed production promotion crosses a proof boundary without rollback evidence.

03

hidden_axis

motion_without_progress

04

required_next_action

hold_and_request_evidence

05

system_effect

should_return_to_human: true

Governed boundary
Trace visible

Request

received

Pre-lens

contracted

Model

routed

Governor

verified

Receipt

persisted

Governance stays separate from model choice, while every stage remains inspectable by the host application.

Provider routing
Team policy
RouteProvider
byokCustomer key
frontier-managedOpenRouter
axiom-consensusManaged models

For developers

One governed API. Two decision surfaces.

Branchable names live on POST /v1/govern as AxiomGovernanceDecision. Chat Completions and Messages still return axiom_governance.action as allow, warn, repair, or refuse.

OpenAI and Anthropic-compatible HTTP routes
Local or self-hosted MCP tools for agents and IDEs
Receipts linked to the team decision ledger
Get API keyRead documentation
POST /v1/govern
curl https://api.axiomlens.com
/v1/govern \
  -H "Authorization: Bearer axm_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "current_state": {
      "release": "candidate",
      "evidence": "incomplete"
    },
    "proposed_next_action": {
      "type": "promote",
      "target": "production"
    }
  }'
AxiomGovernanceDecisionrequire_verification
{
  "decision": "require_verification",
  "reason": "The proposed production promotion crosses a proof boundary without rollback evidence.",
  "hidden_axis": "motion_without_progress",
  "required_next_action": "hold_and_request_evidence",
  "system_effect": {
    "should_continue": false,
    "should_call_model": false,
    "should_call_tools": false,
    "should_return_to_human": true
  }
}

2

API formats

OpenAI and Anthropic compatible

2 + 1

Route policies

Consensus and Managed live; BYOK staged

4

Chat actions

allow, warn, repair, refuse

2

Integration surfaces

Hosted HTTP API and local MCP tools

Commercial access

Use a live managed route or stage BYOK.

Consensus and Managed Frontier execute through the hosted kernel today. BYOK storage is ready, but execution stays blocked until the kernel can retrieve credentials without exposing them.

BYOK staging

Prepare your own provider keys.

Owners can encrypt and stage provider credentials now. The hosted kernel does not retrieve or use them yet, so BYOK calls remain disabled.

Encrypted-at-rest owner-managed storage
Prefixes shown; raw values never returned
Runtime activation requires a future secure retrieval path
Open Providers

Managed Frontier

Use provider access supplied by AXIØM.

Run through AXIØM-managed routing under your plan allowance, with quota enforcement and attributed usage visible in Billing.

No separate provider account required
Allowance and spend controls before model calls
Governance receipts in the hosted decision ledger
View access options

Hosted API calls write team-scoped receipts. MCP runs separately in the environment you configure and does not automatically write to the portal ledger.

Set up MCP