Why this matters
The Collinear Platform offers hosted assessment and visualizations for synthetic datasets. Before you can invoke the hosted Platform API or connect your Trait Basis runs to managed judges, you need a few identifiers from the Collinear dashboard:- A platform login so you can reach your organization’s spaces
- At least one Space to scope datasets, judges, and runs
- A Collinear Platform API key (separate from the Trait Basis key used by the SDK)
- The Space ID that keeps uploads scoped to the right workspace
- One or more Judge IDs for scoring conversations through the API
Step 1 - Log in to the platform
Why it’s important: You need platform access before you can manage spaces, retrieve keys, or view judge metadata.Step 2 · Create your first Space
Why it’s important: Spaces scope every dataset upload, judge, and evaluation you run. The Platform API requires aspace_id on most write requests, and the dashboard keeps keys organized per space.
Step 3 · Copy your Platform API key
Why it’s important: Hosted API endpoints (for uploads, judges, and synthetic runs) expect theAuthorization: Bearer ${COLLINEAR_API_KEY} header. This key lives alongside your space, and it is distinct from the TRAIT_BASIS_API_KEY used by the SDK.
Step 4 · Grab your Space ID
Why it’s important: Upload and judge requests includespace_id so the platform knows where to store datasets, logs, and scores. Using the wrong ID sends artifacts to the wrong workspace.
Step 5 · Locate the Judge ID
Why it’s important: Every call to/api/v1/judge/conversation or judge upload endpoints needs the judge identifier so the platform can route evaluations to the correct scoring model.
Next steps
With the login, key, space, and judge IDs ready, you can:- Run the Trait Basis quickstart locally and keep your platform key separate from the SDK key.
- Follow the updated Platform API example to upload the JSONL you generated.
- Jump into the API reference when you’re ready to script hosted evaluations.