UNCLOSED / DOCUMENTATION
Use these guides to set up your workspace, invite collaborators, and connect an agent through the API. The feature guide explains what is available today and how the experiment tools fit into the wider workflow.
Start in your agent, save the project context, and explore how experiments and evidence fit into the same workflow.
Guided concept + pilot setup ↗WORK TOGETHER / 02Request access, start a project, and invite the people you want to investigate with.
Account pilot ↗BUILD WITH IT / 03Create a scoped credential, make your first request, and add a project through the API.
API quickstart ↗A small first step
Creating a project organizes your work. It does not launch an agent, authorize an experiment, or start spending on compute.
Invite collaborators from your workspace’s People area. Choose a role that matches their contribution: viewer, commenter, editor, or owner. Invitees must verify their email and receive platform approval before product access.
For an agent, open Agent access and create a key with only the scopes it needs. Its authority also depends on your current role and membership. Keep the secret in your secret manager; it is displayed only once.
Understand agent permissions →THE APP / FEATURE GUIDE
“Account pilot” means part of the hosted pilot for approved accounts. “Built, gated” means implemented and tested, with deployment or customer qualification still required. Neither label guarantees that your account can run experiments.
| Feature | How it helps | Status |
|---|---|---|
| Workspaces and projects | Give each investigation a shared home, question, and description. | Account pilot |
| Project discussions | Keep reasoning, questions, and decisions available to collaborators. | Account pilot |
| Invitations and roles | Choose who can view, comment, edit, or manage a workspace. | Account pilot; real collaborator journeys still being qualified |
| Scoped API keys | Let API-capable agents and scripts contribute within your permissions; revoke access when needed. | Account pilot; integration requires setup |
| Budget windows and journal | Set finite allowances and inspect recorded financial activity. | Account pilot; not a full provider invoice |
| Provider connections and costs | Check Cloudflare read access and inspect partial reported overages. | Account pilot; GitHub depends on app configuration |
| Reviewed source library | Keep pinned code, inputs, environment details, and file hashes with the project. | Built, gated |
| Campaigns and attempts | Define finite work, track authorization and run state, and request dispatch or cancellation. | Built, gated; public execution disabled |
| Results and checkpoints | Browse recorded outputs and download files checked against their recorded hashes. | Built, gated |
| Replay exports | Preserve the context for later offline verification and replay after the system confirms that execution has ended. | Built, gated; compatible environment and new compute may be needed |
| Reporting and statements | Filter recorded evidence by project and date; export bounded JSON/CSV statements. | Built; availability depends on the hosted release and workspace access |
Engineering tests establish implemented behavior. Real identity, customer cloud execution, billing reconciliation, and operational recovery have separate qualification gates.
PLANNED / CONNECTING THE WHOLE JOURNEY
Collaborative document editing is planned. The intended experience lets people and agents update a research brief, link evidence, discuss results, and preserve the decisions behind the next step.
For now, use a project description for the brief and discussions for comments and decisions. Keep longer documents in your existing editor and add their links to the project.
Automatic conversation capture, one-click connections to specific agents, external-run ingestion, and side-by-side experiment comparison against custom criteria are also planned. The current API is not a universal transcript or experiment importer.
Connect through the available API →Product status / Account pilot
Approved accounts can create workspaces and projects, invite collaborators, hold discussions, configure API credentials, and review workspace budget records.
Cloudflare read-access checks and partial cost imports are supported. GitHub enrollment depends on the deployment’s app configuration.
The experiment infrastructure includes reviewed source libraries, campaigns with defined limits, execution controls, results, checkpoints, replay exports, and richer reporting.
These features are implemented; availability depends on the hosted release and workspace permissions. Public experiment execution remains disabled. The homepage previews use illustrative content, not live run results.
Workspace budgets record allowances. Provider imports record partial Cloudflare usage overages and their assigned workspace shares. They exclude fixed fees and taxes and are not complete, reconciled invoices. Missing coverage remains unknown rather than zero.
Published SDK packages and durable webhooks are not available in this preview. API examples use ordinary HTTP.