You need a Tuor account with access to at least one organization. Sign up at tuor.dev.
Create a project
Projects are the unit of organization in Tuor. Every trace belongs to exactly one project; each trace’s self-describingspans control how its trajectory renders.
In the Web Console:
- Open the Projects tab in the top navigation.
- Click Create Project.
- Give it a name (1-100 characters).
- Open the project and copy its ID from the Config tab (IDs look like
proj_aB3x…). You will use this asproject_idin every ingest request.
output_schema — enum label pickers, boolean toggles, or json blocks — while paths you leave out get a control inferred from the value’s type. There’s no project-level output type to choose. See Reviewer Blueprints for the payload recipes.
Get an API key
API keys authenticate programmatic traffic from your services to Tuor. They are scoped to the organization that issued them. Only organization admins can create them.- Open Settings → API Keys in the Web Console.
- Click Create New Key and give it a name (e.g.
production-ingest,staging). - Copy the key shown on screen — it starts with
tuor_and is shown only once. Store it in your secret manager.
Send your first trace
Replaceproj_abc123 with the project ID you copied from the Web Console.
The simplest possible ingest:
TraceDetailResponse with the new trace’s id, status (pending), timestamps, structured tag summaries, and event timeline. The trace should appear immediately on the Traces page for the corresponding project in the Web Console.
Call Tuor from application code
Call the API directly from your service code and keep the API key in your server-side secret manager.Where next?
- Get familiar with the trace data model and lifecycle before wiring Tuor into production traffic.
- The Integration API documents trace ingest, fetching, tagging, and export.
- If you want corrections to flow back into your system in real time, set up an outbound webhook.