Status: Production partner preview — personal tenant keys, the minimal durable-task boundary, run reads, resumable SSE, cancellation requests, and usage readback and automatic signed webhooks are live. Exact recorded browser-action approval remains pending activation. Production canaries have proved zero-cost pre-dispatch cancellation and scheduled uncertain-outcome reconciliation for a provider-in-flight cancellation. Turn mode, general tool approval, request-level overrides, organization execution, and mature receipts remain closed.The Praxa Execution Fabric is an API for delegated work. In the live partner preview, you submit a minimal durable task under Praxa’s server-derived defaults, follow its safe run projection through reads, SSE, or signed webhooks, and read tenant-scoped usage. The broader product direction routes work across models, tools, agents, and memory under configurable policy, pauses risky steps for approval, and produces mature audit receipts.
What it is
You submit a task. The live minimal path pins the execution lane and policy server-side; request-level agent, tool, context, policy, and delivery overrides are rejected. Every admitted run passes through a billing reservation and later settlement or fail-closed reconciliation. Exact recorded browser actions have a source-ready digest-bound approval path. Configurable policy, arbitrary tool approval, and mature receipt projection remain later phases. The product direction is accountable routing across models and tools. The live preview proves a smaller boundary—durable admission, lifecycle projection, cancellation request, and usage evidence—not yet the full policy-and-receipt claim.Who it’s for
Agent builders. If you already publish agents on Praxa’s custom-agent platform, you hold a deployment-scoped key today and call that deployment through the existing custom-agent API. The fabric currently adds only the strict personal durable-task boundary; arbitrary agent/tool/policy control is the future direction, not a live upgrade path. Coding-tool developers. A trusted local script can call the minimal cloud task boundary while a Codex or Claude Code session stays local. Direct Praxa Control composer integration, repo/context transfer, and selectable cloud tools remain planned; local provider credentials do not transit through/v1.
Teams. Organization workflows are a target audience. Organization
execution, RBAC for fabric keys, policy packs, evidence ledger, pooled billing,
and organization receipts are unavailable today.
The five parts
One door.POST /v1/execute is the task execution contract. The current
production preview admits only mode: "task"; mode: "turn" returns
400 invalid_request, and /v1/chat is not routed.
Dispatcher. The live lane is server-selected. Caller-selected models,
providers, tools, agents, and failover policy are unavailable.
Permission system. Praxa’s existing domains fail closed before risky actions.
The source-ready public path projects only exact recorded browser actions and binds
each decision to its action digest. The unified configurable policy engine remains
unavailable.
Meter. Admitted bundled tasks pass reservation and settlement authority.
Usage readback counts completed provider evidence; trustworthy public tool-call
counts and BYO funding are unavailable.
Logbook. The live run and event resources expose a deliberately narrow,
customer-safe projection. Mature per-run receipts and evidence export remain
unavailable.
Where to go next
- Concepts: the vocabulary behind runs, events, approvals, policies, receipts, tenants, keys, and billing.
- Quickstart: call a published agent today, or preview your first
execute()run.