Three-Side Integration Entry
Preview your CLARIXO runtime journey.
Project-specific runtime details are shown only when this page is opened with a valid project session.
Start on this page when your next step is the LLM-side Core Runtime Builder path. Use the separate User-side and Development Platform starts when your immediate need belongs to those lines instead.
Choose the side that matches what you need first
LLM-side
Start the Core Runtime path for runtime control, routing, guard behavior, and later AgentOps or governed execution.
User-side
Start the Evidence API path when you need user-facing behavior export, traceability, proof, and later review readiness.
Development Platform
Start the OC Platform Native API local path when you need local bridge testing, dry-run response reading, and implementation-side guidance.
This page is the LLM-side Builder self-serve start page. Use User-side when the immediate need is evidence export. Use Development Platform when the immediate need is local integration, dry-run structure, and implementation-side workflow.
Need the broader runtime contract first? Return to Core Runtime API ·
Need field-level reference? View Contract ·
Need the full docs split first? Choose Your API Entry Path
Runtime start
Start directly from this page
Project context
Create a project or continue reviewing an existing runtime setup
Next step
Start here, read docs, or move into pricing and capability review when needed
Start from the runtime path that matches your current stage to load project-specific details here.
How runtime setup works
Runtime setup details and returned project state
The primary runtime step is at the top of this page. This section continues the flow by showing current project state,
confirmation details, and any returned credentials after the primary action is triggered.
Current runtime step: Ready to start Builder project
Need supporting context first? Read Docs ·
View Pricing
Start from the runtime path that matches your current stage to load project-specific details here.
Integration Links
Move from runtime review into the right next product page
Use docs to understand the documentation stack, the contract reference for exact request and response fields,
the Integration Manual for setup guidance, and pricing when you are ready to move this project into an ongoing plan.
Use Evidence API when you need user-facing behavior evidence without changing the live runtime path first.
Use Audit Workspace when evidence has already been exported and the next need is grouped review, reviewer context, and formal handoff.
When this page already shows an active project, pricing is often the primary next step.
Need the broader runtime contract first? Back to Core Runtime API ·
Need field-level reference? View Contract ·
Need environment policy detail? See Compatibility Policy
Use pricing for ongoing plans, the Integration Manual for implementation guidance, and Evidence API when you need the separate behavior-evidence track.