Free Evidence Intake · User-side Protection

Start free behavior evidence capture and basic verification.

Free Evidence Intake is the first user-side step for exporting user-facing AI behavior as traceable, readable, and verifiable evidence records. It is designed for behavior capture and basic verification first, with a clearly marked TAL upgrade path toward Layer 2 Responsibility Attribution when closure, authority, and responsibility must be assessed.

TAL Chain Entry Point
Layer 2 Responsibility Attribution remains an upgrade path, not part of the free intake claim.
Use this page to generate a free intake key, write one behavior evidence event, and verify that the record is readable. Move into Layer 2 when formal responsibility closure, bound authority, classification context, and stable trace continuity are required.
Generate Free Intake Key Back to User-side Protection
Need the current access notes first? Review how access works
Free intake path

Generate a free intake key, then prove the first evidence loop

Start here when your first need is behavior evidence capture and basic verification. The free intake path gives you a short bootstrap window to create a project, receive a key, write one evidence event, read it back, and verify that the record is usable before you request continuation or Layer 2 responsibility attribution.

Free Intake · Recommended

Generate 48-hour free intake access automatically

Generate a trial project and free intake key immediately. This creates the minimum identity surface for the first behavior evidence write/read/verify loop. Intake 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 Free Evidence Intake gives you

Immediate free intake access
This page includes a self-serve free intake path for trial project creation and first-key delivery, so teams can begin the first live behavior evidence write/read/verify loop directly from here.
Current access shape
Free Evidence Intake remains the open user-side evidence-entry layer for behavior capture and basic verification. The automatic key issued here is a 48-hour instant intake key for first validation and abuse prevention. It is not Layer 2 Responsibility Attribution certification and it is not the full integration trial period.
Handler path
The live submission and retrieval surface remains /?action=evidence-events. This batch does not change the underlying Evidence API handler, verification path, schema, or L2/L3 handoff semantics.
Required payload scope
For a real first intake, 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 intake proof
The first working proof is: generate 48-hour free intake access, send one valid evidence event, retrieve it back, and verify that the record is readable. Responsibility attribution, continuation approval, payment, and stricter long-term access controls can be layered on top after this proof is established.
Request continuation or upgrade

Continue after free intake proof

The 48-hour free intake window is designed for first behavior evidence write/read/verify validation. Existing evidence records remain readable and verifiable after intake expiry, but continued write access, formal review, or responsibility attribution requires a continuation or upgrade path.

What expires
The free intake key controls new evidence 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 or upgrade
After your first evidence loop is complete, use the request buttons shown in the generated key result panel to record a 14-day continuation intent or a Layer 2 Responsibility Attribution upgrade discussion. You can also open the L2 Object Interface to review the controlled responsibility-object loop: derive an L2 view from existing evidence, promote selected evidence into a separate L2 Responsibility Object, read the promoted object, and verify its source evidence hash, schema, promotion policy, and mutation boundary. Recording an upgrade intent does not complete Layer 2 and does not grant L2→L3 handoff readiness. You can also email contact@clarixo.fun with your project_id, application name, use case, expected volume, and the path you need next.
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 intake proof

Prove one valid evidence loop before you productionize access control

Step 1

Confirm the free intake boundary

Free Intake covers behavior evidence capture and basic verification. It does not claim Layer 2 Responsibility Attribution or L2→L3 handoff readiness by itself.

Step 2

Send one real evidence event

Use the generated key to export one real user-facing behavior, 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 proof goal
The first successful intake is not "I generated a key." It is "I wrote one stable evidence event, retrieved it back, and confirmed it is readable and verifiable."
curl -sS 'https://clarixo.fun/?action=evidence-events' \
  -H 'Content-Type: application/json' \
  --data '{
    "project_id":"your_free_intake_project_id",
    "application_id":"your_app:behavior_export",
    "event_id":"evt_free_intake_example_001",
    "session_id":"sess_free_intake_example",
    "recorded_at":"2026-05-01T00:00:00Z",
    "input_summary":"User asked for a behavior that should remain traceable.",
    "output_summary":"System produced a user-facing outcome that was captured as a basic evidence record.",
    "final_status":"delivered"
  }'