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 Read Docs Explore Evidence API Explore Audit Workspace

Project

No bound project yet

Plan

Builder

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

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

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

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.

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

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

★ Cross-side / Responsibility

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

Responsibility is the commercial layer that connects governed execution with formal evidence review. It should be read before Enterprise, because it is the true cross-side layer between runtime governance and user-side review. On one side it depends on execution governance and operator control, and on the other side it unlocks the review-grade surface needed for case reading, reviewer context, and structured handoff.

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

Policy layering and ownership design
Full decision trace and audit depth
Deployment design and rollout structure
Multi-team governance support

Start 48-hour Access

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.

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.