The public map · Product status
What is open, what is in pilot, and what lies ahead.
A roadmap should help customers plan without turning intention into a present-tense promise. Every item below carries an availability label.
How to read this page
Three labels. No hidden tense.
In the public contract
The operation appears in OpenAPI and can be checked against the live endpoint.
Usable with bounded expectations
The surface is live or entering live use, but support, scale, or contract maturity remains limited.
Direction, not a promise
The capability is a public intention. Do not build a dependency on it until its status changes.
The contract wins
If this page and OpenAPI ever disagree, treat the operation as unavailable and report the mismatch.
The castle gates are open
Available in the core API.
These customer jobs are represented in the current OpenAPI contract. Individual schemas and authorization requirements remain authoritative there.
Bounded trial and onboarding
Discover jobs, read onboarding, validate a profile, and try a no-key recipe.
/v1/jobs · /v1/trial
Durable agent runs
Create a run, read its state, and cancel by ID when the contract permits.
/v1/agent-runs
Research missions
Start from a template, inspect the mission, and approve a bounded transition.
/v1/mission-runs
Customer-controlled context
Remember, search, relate, correct, quarantine, forget, and inspect integrity.
/v1/memory · /v1/brain
Trust and evidence
Inspect audit events, traces, evaluation suites, and evaluation runs.
/v1/audit-events · /v1/evaluations
Platform setup
Inspect models, providers, adapters, budgets, usage, routing, skills, tools, and sandbox capabilities.
/v1/models · /v1/usage
Lanterns on the next path
Pilot surfaces now being hardened.
These are deliberately visible so early customers can use them without mistaking pilot availability for a finished service-level guarantee.
Self-service workspace
Create a workspace, issue scoped keys, and inspect customer-local account state.
Continuous customer vault
Search and export the customer’s own agent history through tenant-isolated storage.
/v1/vault
Beyond the far gate
Planned directions—not present capabilities.
| Status | Direction | What would make it available |
|---|---|---|
| Planned | Recurring schedules | Durable account-scoped authorization, schedule indexing, failure recovery, and a public contract |
| Planned | Customer-authorized connectors | Closed OAuth callback flow, credential configuration, revocation tests, and public contract coverage |
| Planned | Team roles and shared workspaces | Public identity model, role contract, isolation tests, and workspace UI |
| Planned | Completion and approval webhooks | Signed delivery contract, retries, replay protection, and customer controls |
| Planned | Audit exports for teams | Stable export schema, retention controls, and clean import/readback tests |
| Planned | Connector and recipe ecosystem | SDK contract, permission boundaries, admission tests, and versioning policy |
The rule of the realm
Roadmap language never expands customer authority.
Availability is inspectable
Current operations belong in the contract and must return explicit HTTP state.
Pilots remain bounded
Early access is useful only when limitations and support expectations stay visible.
Plans remain conditional
Sequence and timing can change. Customers should not need to reverse-engineer the tense.
Effects remain approved
No roadmap item can turn authentication into blanket permission for external action.