Getting started
Every guide uses the same five values. Set them once in your shell.
export PLATFORM_BASE='https://us.trazio.cerebrixos.com' # or https://ca.trazio.cerebrixos.com export TENANT_ID='<your-tenant-id>' export PIPELINE_ID='<your-pipeline-id>' export TENANT_JWT='<short-lived-jwt>' # reads, queries, uploads export PLATFORM_PROTOCOL_TOKEN='<write-only-token>' # collectors that cannot mint a JWT
Where each value comes from
Self-serve (most people). Create your workspace in the console. It gives you the tenant and pipeline IDs, the collector token (shown once) and a data token you can use as TENANT_JWT. You don't need your own identity provider.
Managed by Trazio. If the Trazio team set up your pipeline, they give you the values instead:
| Value | What it is | Who gives it to you |
|---|---|---|
PLATFORM_BASE | The regional endpoint for your pipeline. The country hostname selects that deployment. | Your Trazio administrator, at onboarding. |
TENANT_ID, PIPELINE_ID | Which organisation and which stream of data you are writing to. | Your Trazio administrator. You cannot create these yourself. |
TENANT_JWT | A short-lived signed token scoped to exactly this tenant and pipeline. It carries the permissions each guide lists. | Your own identity provider mints it; the platform verifies it against your published keys. |
PLATFORM_PROTOCOL_TOKEN | A write-only token for collectors and log shippers. It can send data but cannot read anything. | Your Trazio administrator. Rotate it any time with client.rotate_protocol_token(). |
Never put either credential in source control, an image, an MCAP attachment or a device log.
Check the connection
curl --fail-with-body -sS \
"$PLATFORM_BASE/v1/query/$TENANT_ID/$PIPELINE_ID?limit=1" \
-H "Authorization: Bearer $TENANT_JWT" | jq '{tenant_id, pipeline_id, count}'
Your tenant and pipeline IDs coming back means the token, tenant and pipeline all match. The same check from the SDKs:
npm install trazio-telemetry export PLATFORM_BASE_URL="$PLATFORM_BASE" PLATFORM_TENANT_ID="$TENANT_ID" PLATFORM_PIPELINE_ID="$PIPELINE_ID" npx trazio-telemetry doctor
doctor only checks that your environment variables are set. It does not contact the platform.
Always send a stable event ID
Give every event an Idempotency-Key (or an event_id of your own). A retry then resolves to the same stored record instead of a duplicate.
Connect an AI assistant
Assistants need no token. They sign in with your CerebrixOS account.
- Add the connector
https://trazio.cerebrixos.com/mcpin Claude or ChatGPT. - Approve the connection and choose Continue with CerebrixOS.
- The first time, enter the one-time invite code your administrator gave you.
The assistant can then search events, recordings, video and incidents in your pipeline. It is read-only: it cannot send data, change settings or delete anything.
Next
Pick your use case from the index.