Skip to main content
Use this page to choose a supported integration path. Availability, package publication, deployment, and authenticated qualification are separate facts.

​
Available developer surfaces

For the complete package and product matrix, use Service status and the Capability Atlas.

​
Execution Fabric v1 boundary

The partner-preview API accepts mode: "task" and derives tenant ownership from a personal workspace key. It does not accept browser sessions, Supabase tokens, caller-selected owners, organization tenants, or request-level agent/tool/policy/delivery overrides. The available task lifecycle is: Admission is not completion. Follow the run resource, reconnectable event stream, or signed webhook until you observe the terminal evidence your application requires.

​
Qualification previews

​
Hosted memory candidates

The four /v1/memory/* operations are deployed and fail closed without a valid key. Authenticated positive, wrong-scope, revoked-key, idempotency-conflict, and cross-tenant production qualification is still pending. Use disposable content and keep the candidate plane separate from Praxa personal memory, AHCE, task context, and provider-owned source data.

​
Exact browser-action approvals

The public approval refinement remains unavailable until its production qualification is complete. Do not build a general tool-approval UI from the current task contract. Continue to treat awaiting_approval as a readable run state and preserve the exact recorded action when your issued integration supports it.

​
Not part of the current public contract

  • rich mode: "turn" execution and a public /v1/chat route;
  • organization API keys, organization execution, or organization memory scopes;
  • caller-selected agents, tools, context, policy packs, or delivery overrides;
  • a provider credential vault or hosted provider connect, sync, import, mirror, or cutover workflow;
  • AHCE or Praxa personal-memory ingestion;
  • a public customer-authored workflow DSL or experiment execution API;
  • generic tool approvals or a claim that every provider action can be rolled back;
  • a shared public Integration Gateway origin or token issuer.

​
Before production use

  1. Pin package and API versions in your application.
  2. Keep credentials in their owning server-side boundary.
  3. Test correct scope, wrong scope, revocation, cross-tenant identifiers, exact retries, changed-body conflicts, rate limits, and cleanup.
  4. Verify a run, event, webhook receipt, export, or deletion receipt separately from model prose and HTTP admission.
  5. Record your own authenticated staging canary before enabling customer data or consequential effects.

Production checklist

Turn the status boundary into a release gate for your application.
Last modified on August 14, 2026