REF · 01
DOC
STARTS FROM
Quickstart · cookbook
Agent Studio Open
Local-first IDE for agent traces. Quickstart, concepts, cookbooks, CLI, and the export path into CI.
OPEN REFERENCE
OPEN →RESOURCES · DOCUMENTATION
Start in the right place.
The docs are organized around the decisions teams make first. How to get started. How to connect the stack. How to deploy. How to keep the review readable.
SIX REFERENCES · ONE LOOP · ONE RECORD
CATEGORIES
Three lanes
Start and ship, connect and automate, operate and review. Pick the one that matches the job.
LATEST
Versioned with the platform
Reference and quickstart pages move when the surface they describe moves.
TOPICS
Setup · review · deploy
Install, run, review the result, sign the packet, and operate the workflow under change.
DOCUMENTATION MAP
Pick the reference that matches the job.
Six references. Each opens a path the team uses while building, connecting, or defending the work.
REF · 02
DOC
STARTS FROM
Managed cloud
Deployment guide
Managed cloud setup, key handling, first-run guidance, and the controls reviewers ask about first.
OPEN REFERENCE
OPEN →REF · 03
DOC
STARTS FROM
SDK · API
Developers hub
SDK installs, REST endpoints, typed clients, and the snippets that get the first run on the board.
OPEN REFERENCE
OPEN →REF · 04
DOC
STARTS FROM
Webhooks · CI
Integrations
Signed webhooks, CI connectors, incident routing, and the catalog of systems that already speak.
OPEN REFERENCE
OPEN →REF · 05
DOC
STARTS FROM
Walkthroughs
Tutorials
Runnable walkthroughs from first install to a reviewed regression bank and rollout checklist.
OPEN REFERENCE
OPEN →REF · 06
DOC
STARTS FROM
Controls · review
Security policy
Posture, controls, and the review material that procurement and risk owners open first.
OPEN REFERENCE
OPEN →DOCUMENTATION
Need the right page mapped to the workflow?
We'll point your team to the right quickstart, connector, or review material and show how it lines up with the live product.
↳ STARTS WITH
An install, a setup question, or a reviewer asking which page covers the control.
↳ LEAVES WITH
A working code path, a reviewed reference, and the next step already named.