Praxa Execution Fabric

​

How a task moves through the fabric

POST /v1/execute                submit a task, under a policy
        |
        v
   run starts                   routed across models and tools under that policy
        |
        v   (only if the policy calls for it)
   approval.required             event carries the exact action plus an approval digest
        |
        v
   you decide                   POST /v1/runs/:id/approve  { action_digest, decision }
        |
        v
   run finishes                 outcome + receipt: what ran, which policy, who approved, verified how

​

Status legend

​

Documentation

​

Getting started

• getting-started/overview.md — what the fabric is and how a request flows end to end
• getting-started/concepts.md — runs, events, receipts, policy, and tenancy in one page
• getting-started/quickstart.md — make your first authenticated call

​

API reference

• api/execute.md — POST /v1/execute: submit a task, choose turn or task mode
• api/runs.md — GET /v1/runs/:id: read a run’s current state
• api/events.md — GET /v1/runs/:id/events: stream a run’s events, resume with Last-Event-ID
• api/approvals.md — POST /v1/runs/:id/approve: resume a paused run
• api/usage.md — GET /v1/usage: tenant-scoped usage and spend readback
• api/webhooks.md — POST /v1/webhooks: register a delivery endpoint
• api/errors.md — the RFC 9457 error format every endpoint shares
• api/openapi.yaml — machine-readable OpenAPI 3.1 specification

​

Keys & access

• keys-and-access/api-keys.md — creating, scoping, and rotating praxa_sk_ keys
• keys-and-access/scopes-and-tenancy.md — tenants, scopes, and the three principal types
• keys-and-access/rate-limits.md — per-key limits and response headers

​

Approvals & policy

• approvals-and-policy/approvals.md — how a run pauses and how you resume it
• approvals-and-policy/policy-engine.md — the policy parameter and how risk tiers get decided
• approvals-and-policy/budgets-and-limits.md — budget ceilings and what happens when a run hits one

​

Security

• security/security-model.md — tenant isolation and credential handling
• security/data-handling.md — what’s stored, for how long, and whether any of it trains a model
• security/receipts-and-audit.md — receipts and the hash-chained evidence trail behind them

​

SDK

• sdk/typescript.md — the TypeScript client
• sdk/streaming.md — consuming a run’s event stream in code
• sdk/errors-and-retries.md — client-side retry and error-handling semantics

​

Use cases

• use-cases/overview.md — the three markets the fabric is built for
• use-cases/agent-builders.md — upgrading an existing custom agent onto the fabric
• use-cases/coding-and-desktop.md — cloud execution lanes for desktop coding sessions
• use-cases/business-workflows.md — internal org workflows on the same substrate

​

Enterprise

• enterprise/teams-and-organizations.md — org-level tenancy and billing
• enterprise/billing-and-plans.md — tiers, metering, and the plan ladder
• enterprise/deployment-and-isolation.md — dedicated isolation, and why there’s no self-hosted option

​

How-to guides

• how-to/build-an-approval-ui.md — render an approval payload correctly (render == record == what actually runs)
• how-to/receive-webhooks.md — verify signatures and handle retries
• how-to/bring-your-own-keys.md — connect your own provider credentials
• how-to/migrate-from-provider-apis.md — moving from a direct model API to the fabric

​

Reference

• faq.md — common questions, answered honestly
• status-and-roadmap.md — what’s shipped and what’s next, in customer terms
• glossary.md — terms used across these docs

​

Support