CLARIXO
Pricing

Pricing across the LLM-side and the User-side, with Responsibility spanning both.

CLARIXO pricing is structured across two primary sides. Core Runtime API follows the main LLM-side pricing ladder, Evidence API remains the separate User-side self-serve path, and Audit Workspace belongs to the User-side architecture while access to it is provided through Responsibility rather than standalone purchase.

Start Core Runtime Integration Start Paid Access Read Docs Explore Evidence API Explore Audit Workspace
Project
No bound project yet
Plans

Choose the product path that matches your operating stage

CLARIXO pricing is now shown by side so teams can immediately understand where runtime control begins, where user-facing evidence begins, and where cross-side responsibility starts to matter.
LLM-side
The LLM-side pricing group covers runtime control, routing, fallback visibility, AgentOps, Approval Gateway, execution governance, and organization-wide deployment layers.
User-side
The User-side pricing group covers behavior evidence export and formal review surfaces. Evidence API remains permanently free, while Audit Workspace is used together with Responsibility.
Cross-side / Responsibility
Responsibility is the connecting commercial layer across both sides. It links governed execution on the LLM-side with formal evidence review and handoff on the User-side.
Where to go next
Use Core Runtime API when your team is choosing pricing depth on the LLM-side. Use Evidence API when your team needs the separate User-side evidence path with self-serve entry and permanently free behavior evidence export. Use Audit Workspace when your team is evaluating the User-side review surface made available through Responsibility.
LLM-side plans

Runtime control and governed execution

Choose the commercial depth that matches how far your AI system has moved into production operation, operator handling, and execution governance.

Builder

Builder

Start building with core CLARIXO runtime access, routing basics, and essential runtime visibility.

Recommended for first integrations, small teams, and early production validation.

$39

per month

  • Up to 3 projects
  • Core API access
  • Routing and fallback basics
  • Essential runtime signals
Start 48-hour Access
Pro

Pro

Scale into production with deeper runtime visibility, drift signals, fallback control, and explainable execution review.

Recommended for production teams that need stronger runtime visibility and scaling support.

$199

per month

  • Up to 10 projects
  • Higher monthly API volume
  • Deeper runtime visibility
  • Drift, fallback, and confidence visibility
Start 48-hour Access
Business · AgentOps

Business

Operate live AI systems with AgentOps: runs, triage, queue, escalation, and operator-facing workflows.

Recommended for teams already running live agents and needing operator-facing control.

$499

per month

  • Everything in Pro
  • AgentOps runs and run detail
  • Queue, triage, and escalation workflow
  • Operator action visibility
Start 48-hour Access
Control · Approval Gateway

Control

Govern execution with Approval Gateway, proposed action review, and explicit execution governance before live execution continues.

Recommended for teams that need approve, block, escalate, and governed execution control in production.

$999

per month

  • Everything in Business
  • Approval Gateway access
  • Execution governance
  • Approve, block, and escalate flow
Start 48-hour Access
User-side plans

Behavior evidence and formal review

Start from the user-facing evidence path when your first need is proving what AI did, then move into formal review when responsibility-sensitive handling becomes necessary.

Evidence API

Evidence API

Export user-facing AI behavior as traceable, provable, and auditable evidence records without changing the runtime path first.

Recommended for teams that want the fastest user-side entry and a permanent free evidence path.

$0

per month · permanently free

  • Self-serve start path
  • Behavior evidence export
  • Traceability and proof support
  • First write and first read workflow
Start free with Evidence API
Audit Workspace

Audit Workspace

Read grouped evidence, carry reviewer context, and prepare structured case export when formal review is required.

Recommended for teams evaluating review-grade handling on the user-side.

Included

Available with Responsibility

  • Grouped evidence reading
  • Reviewer notes and case context
  • Formal case export
  • Used together with Responsibility
Explore Audit Workspace
HIC Runtime

HIC Continuity Safety Pressure Test

Test whether your AI keeps pushing users when they are hesitant, overloaded, afraid of mistakes, or asking to slow down.

Recommended for long-memory AI assistants, copilots, support AI, healthcare AI, and application-layer agents.

from $1,500

pressure test and pilot engagement

  • Hesitation and overload testing
  • Unsafe continuation detection
  • Pause and pacing evaluation
  • Structured continuity risk review
Explore HIC Pressure Test
★ Cross-side / Responsibility

Responsibility spans the LLM-side and the User-side.

$1,999

per month

Responsibility is the SaaS responsibility workflow layer that connects governed execution with formal evidence review. It makes Audit Workspace available for review-grade handling and can connect teams to the separate L2 Responsibility Object API under protocol service terms when protocol-grade responsibility objects are required.

Start 48-hour Access Open Audit Workspace
Enterprise · Organization Layer

Enterprise

Extend from the Responsibility layer into organization-wide governance, policy layering, audit depth, deployment design, and multi-team operating structure.

Recommended for organizations that already need cross-side responsibility handling and now require organization-wide rollout, policy design, and ownership structure.

Custom

typical deployments start from $10,000/month · contact us

  • Policy layering and ownership design
  • Full decision trace and audit depth
  • Deployment design and rollout structure
  • Multi-team governance support
Contact Enterprise
CLARIXO is not priced like a token-hungry AI service. This system is a runtime control and visibility layer, not a device-heavy or inference-heavy AI product, so entry pricing is designed to stay adoptable while higher-value pricing is concentrated in AgentOps, Approval Gateway and execution governance, formal responsibility review, and organization-wide deployment layers. Lower entry pricing does not mean reduced system capability. It means teams can start with runtime control, routing, fallback visibility, confidence signals, and guard behavior first, then expand into governed execution, formal responsibility handoff, and organization-wide control when operational value becomes real. If a project is already bound, plan selection keeps that project context attached during upgrade and rollout.
Capability mapping

Read CLARIXO pricing by side, then by cross-side expansion

CLARIXO pricing is no longer best understood as one flat plan ladder. It is structured around the LLM-side, the User-side, the cross-side Responsibility layer between them, and the Enterprise extension that follows after responsibility-sensitive operation becomes organization-wide.
LLM-side plans
Builder, Pro, Business, and Control belong to the LLM-side pricing family. They move from runtime foundations into deeper production visibility, AgentOps, Approval Gateway, and governed execution.
User-side plans
Evidence API and Audit Workspace belong to the User-side path. Evidence API remains the permanently free foundation-layer entry for behavior evidence export, while Audit Workspace is the formal review surface used together with Responsibility.
Cross-side / Responsibility
Responsibility is not just another plan inside the LLM-side ladder. It is the cross-side commercial layer that connects governed execution on the LLM-side with review-grade evidence handling on the User-side.
Enterprise extension
Enterprise comes after Responsibility. It extends the responsibility-sensitive operating model into organization-wide governance, policy layering, audit depth, deployment design, and multi-team ownership structure.
Which path fits first
Choose the LLM-side first when your team begins from runtime control and execution governance. Choose the User-side first when your first need is proving what AI did for users. Move into Responsibility when both sides need to be connected through formal review and handoff, and move into Enterprise when that responsibility model expands across the organization.
API & Protocol Usage

L2 Responsibility Object API is a separate protocol service

CLARIXO keeps LLM-side and User-side protection as SaaS services for AI Agent teams. The L2 Responsibility Object API is different: it is a separate protocol-facing service for generating responsibility-bearing objects before downstream TAL handoff.
Evidence API
Evidence API remains the free or low-friction intake path for user-facing AI behavior records. It helps teams capture what happened before they move into formal responsibility attribution or audit review.
L2 Responsibility Object API
The L2 Responsibility Object API turns eligible behavior or evidence records into responsibility-bearing objects with closure, authority, attribution, threshold, and trace-continuity signals. This is not a generic SaaS feature card. It is a separate protocol service with pricing handled under protocol access, usage, volume, retention, verification, and downstream handoff terms. Typical protocol access starts from $10,000–$25,000/month, while regulated, high-volume, or downstream handoff deployments are custom quoted.
Relationship to TAL
Within the TAL collaboration, CLARIXO / TGTRACING serves as a Layer 2 responsibility-attribution reference implementation. The L2 Responsibility Object API exposes this boundary as an integration interface for TAL-compatible responsibility attribution.
Downstream boundary
The L2 Responsibility Object API does not replace VRIL / L2.5 readiness checks, EVIDE / L3 evidentiary anchoring, Royal Road / L4 transit consistency, Pantheon / L5 admissibility, or downstream enforcement. A CLARIXO L2 object may be responsibility-consumable without inheriting downstream TAL guarantees.
What it does
It generates responsibility-bearing L2 objects, exposes responsibility closure, checks authority coherence, surfaces attribution consistency, preserves classification context, reports threshold status, reports trace continuity, and marks drift, hold, or downstream-consumable states.
What it does not do
It does not certify L2.5 readiness, externally anchor evidence at L3, decide formal admissibility at L5, execute enforcement actions at L6, or inherit downstream TAL guarantees.
Billable usage
A billable L2 protocol unit is one successfully created responsibility object. Basic reads, public verification, failed validation responses, and idempotent replay are not treated as primary billable units. Protocol pricing is handled separately based on responsibility-object volume, retention, verification, audit export, and downstream handoff requirements; object-level unit prices are scoped during the protocol access discussion rather than published as a fixed public list price.
Current endpoint shape
POST /?action=l2-responsibility-promote
GET /?action=l2-responsibility-promote&verify=1&l2_object_id=...
Future stable API shape
POST /v1/l2/responsibility-objects
GET /v1/l2/responsibility-objects/{object_id}
GET /v1/l2/responsibility-objects/{object_id}/verify
Discuss Protocol Access Start Evidence API Explore Audit Workspace
How pricing works

Choose a side first, then expand into cross-side responsibility when it becomes operationally necessary

Pricing principle
CLARIXO is designed for monthly continuation, not prepaid lock-in.
If users are satisfied this month, they continue next month. If not, they are free to leave. That is part of the boundary.
CLARIXO pricing is designed so teams do not need to enter at the highest commercial layer on day one. Teams that begin from runtime control can move through the LLM-side path from Builder to Control as production operation, operator handling, and execution governance deepen. Teams that begin from user-facing proof can start directly from the permanently free Evidence API path on the User-side. Responsibility becomes the next commercial step when governed execution and formal review need to be linked across both sides. Enterprise then extends that model into organization-wide governance, ownership structure, deployment design, and policy layering. This page keeps project context attached during plan selection. The default paid upgrade path is provider-bound and moves through clear stages: create an upgrade request, bind the provider session to the current project, complete the provider callback step, and then activate the selected plan so plan activation, history, and billing records stay aligned. Billing terms, renewal timing, and cancellation details are governed by our Terms of Service, Privacy Policy, and Refund Policy.