Start · Integration Entry

Start CLARIXO Behavior Evidence Export API Integration

This is the start page for CLARIXO Behavior Evidence Export API. Begin with 48-hour instant bootstrap access when you want to run the first live write/read/verify loop. For real integration work beyond the bootstrap window, request a 14-day integration continuation or open the Integration Manual when you are ready to implement against a real system.

Generate Bootstrap Project & API Key Open the Integration Manual
Need the current access notes first? Review how access works
Start paths

Choose the right first move

Different teams arrive here for different reasons. Some are ready to implement. Some need the contract and boundary first. Some need to understand the current access model and first-call shape before they wire anything into production.

Bootstrap · Recommended

Generate 48-hour bootstrap access automatically

Start the self-serve bootstrap to generate a trial project and first bootstrap key immediately. This creates the minimum identity surface for Evidence API first write/read/verify validation without sending you through the contact form first. Bootstrap keys are project-bound: the project_id used in your write must match the project bound to the supplied key.

Implementation

Open the Integration Manual

Use the Manual when you are ready to map fields, normalize a payload, generate evidence_hash, submit records, retrieve them back, and close the first working verification loop.

Open the Manual
Contract

Read the Integration Protocol

Use the Protocol when you need the role, scope, boundary, minimum evidence record, integrity rule, and the product separation from CLARIXO Core Runtime API.

Open the Protocol
Access notes

What the current start flow gives you

Immediate bootstrap access
This start page includes a self-serve bootstrap path for trial project creation and first-key delivery, so teams can begin the first live Evidence API write/read/verify loop directly from here.
Current access shape
The base Evidence API remains free as the open evidence-entry layer. The automatic key issued here is a 48-hour instant bootstrap key for first integration validation and abuse prevention. It is not the full integration trial period. For real implementation work, teams should request a 14-day integration continuation after the first write/read/verify loop is proven.
Handler path
The live submission and retrieval surface for the minimum API shape is /?action=evidence-events.
Required payload scope
For a real first integration, send a stable project_id and application_id in the evidence payload so the exported records can be grouped, retrieved, and reviewed consistently later.
First closure
The first working closure is: generate 48-hour bootstrap access, send one valid evidence event, retrieve it back, and verify that the record is readable. Credential hardening, continuation approval, payment, or stricter long-term access controls can be layered on top after the first closure is proven.
Request continuation

Request a 14-day integration continuation after bootstrap

The 48-hour instant bootstrap window is designed for first write/read/verify validation. Existing evidence records remain readable and verifiable after bootstrap expiry, but continued write access for real integration work requires manual continuation approval while CLARIXO's self-serve billing path is not yet active.

What expires
The bootstrap key controls new Evidence API writes. When the key expires, new POST /?action=evidence-events writes may be rejected until continuation is approved.
What remains available
Previously exported evidence records remain queryable and verifiable through the read and verify paths, including existing verification_url links.
How to continue
For a 14-day integration continuation, pilot, partner validation, commercial evaluation, or continued implementation work, email contact@clarixo.fun with your project_id, application name, use case, expected volume, and whether you need Evidence API, Verify Evidence, Audit Workspace, or deeper runtime governance access.
Temporary commercial path
Until self-serve payment is fully enabled, continuation can be handled manually through pilot approval, partner-led validation, or a commercial review arrangement without changing the Evidence API integration path.
First-call closure

Make one valid write before you productionize access control

Step 1

Confirm the role and boundary

Read the Protocol first if the team still needs alignment on what Evidence API covers and what remains outside its scope.

Step 2

Send one real evidence event

Use the Manual to export one real user-facing behavior, generate evidence_hash, submit it to /?action=evidence-events, query it back, and confirm that the record is readable and operationally useful.

First request
POST /?action=evidence-events with JSON body.
Minimum identity
Send at least project_id, application_id, event_id, session_id, and recorded_at so the record can be traced and queried back properly.
First test goal
The first successful integration is not "I saw the handler URL." It is "I wrote one stable evidence event and retrieved it back in a reviewable form."
curl -sS 'https://clarixo.fun/?action=evidence-events' \
  -H 'Content-Type: application/json' \
  --data '{
    "project_id":"trial_proj_b17e8105174f862a",
    "application_id":"tgtracing:assistant:customer_chat",
    "event_id":"evt_start_page_example_001",
    "session_id":"sess_start_page_example",
    "recorded_at":"2026-04-09T00:00:00Z",
    "input_summary":"User asked whether the system exposes a formal start path for Evidence API integration.",
    "output_summary":"System exposed the formal start page and explained the current access model.",
    "final_status":"delivered"
  }'