Praxa developer documentation

Praxa gives developers separate, explicit contracts for durable task execution, governed agent missions, MCP tools, observability, webhooks, and read-only federation across existing memory systems. Start with the outcome you need; each surface has its own credential, authority, and release boundary.

Explore every use case

Compare the available execution, mission, MCP, memory, webhook, observability, and research surfaces with concrete examples.

Follow an end-to-end tutorial

Integrate Praxa with TypeScript, Next.js, Nuxt, Express, Workers, Python, Rust, Go, Spring, .NET, mobile, agent frameworks, or an existing memory provider—and test the result.

Run the reference examples

Test the HTTP request, memory federation, and MCP package contracts locally before creating a live credential.

Try the API Playground

Generate and send scoped cURL, JavaScript, or Python requests for the concrete api.praxa.io contracts.

Read the Execution Fabric guide

Submit durable tasks, observe runs, read usage, and receive signed webhooks through the personal-tenant partner preview.

Choose an integration surface

If you need to…	Start with	Credential and authority
Submit, observe, or cancel a durable task	Execution Fabric	Personal workspace API key for `https://api.praxa.io`
Create a budgeted mission with signals and resumable events	TypeScript SDK	Short-lived OAuth token and your deployment-specific Integration Gateway origin
Add governed operations to an MCP-compatible agent	MCP Contracts	The public contracts package; runtime calls still use a Gateway token
Operate missions from a terminal or CI job	CLI	The same deployment-specific Gateway origin and OAuth token
Query Mem0, LangGraph, Zep, Graphiti, Letta, or OpenAI Agents memory	Memory Federation	Provider clients and credentials owned by your backend
Stage portable records for lexical query, export, and erasure	Hosted memory candidate tutorial	Personal workspace key with `memory:read` or `memory:write`; qualification preview
Reproduce published performance evidence	Benchmarks & Research	No production credential for public artifacts

Do not move credentials between surfaces. In particular, an Execution Fabric API key is not an Integration Gateway OAuth token, and a memory-provider credential belongs only in the backend process that creates that provider client.

Run your first durable task

Create a personal workspace key with execute:write, then send one stable idempotency key for the logical task:

curl --fail-with-body https://api.praxa.io/v1/execute \
  -H "Authorization: Bearer $PRAXA_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: weekly-review-2026-08-13" \
  -d '{
    "apiVersion": "v1",
    "requestId": "weekly-review-2026-08-13",
    "mode": "task",
    "task": { "input": "Summarize this week and propose the next safe action." },
    "idempotencyKey": "weekly-review-2026-08-13"
  }'

A 202 response proves that the task was admitted or exactly replayed. Follow the returned run resource or event stream to verify completion; admission alone does not prove a downstream effect.

Run a governed mission

If your organization operates an Integration Gateway deployment, install the public SDK and use the origin and short-lived OAuth token issued by that deployment:

npm install @praxa/sdk@0.3.0

import { PraxaClient } from "@praxa/sdk";

const praxa = new PraxaClient({
  baseUrl: process.env.PRAXA_BASE_URL!,
  accessToken: () => process.env.PRAXA_ACCESS_TOKEN!,
});

const mission = await praxa.createMission(
  {
    goalSpec: { task: "Prepare the weekly review" },
    resourceBudget: {
      maximumSteps: 12,
      maximumToolCalls: 8,
      maximumElapsedMs: 120_000,
      maximumParallelism: 2,
    },
  },
  "weekly-review-2026-08-13",
);

for await (const event of praxa.missionEvents(mission.runId)) {
  console.log(event.id, event.event, event.data);
}

Build from a tested example

Durable tasks

Submit, poll, stream, cancel, and verify a v1 task.

Memory federation

Combine read-only memory sources and test provenance and partial outages.

MCP tools

Signed webhooks

Verify raw-body signatures, deduplicate deliveries, and test replay.

Framework backends

Keep credentials server-side across JavaScript, Python, Rust, Go, Java, .NET, and mobile-backed integrations.

Integration test matrix

Prove success, isolation, idempotency, degradation, and cleanup behavior.

Get started

Core Concepts

Releases

Praxa developer documentation

Explore every use case

Follow an end-to-end tutorial

Run the reference examples

Try the API Playground

Read the Execution Fabric guide

Choose an integration surface

Run your first durable task

Run a governed mission

Build from a tested example

Durable tasks

Memory federation

MCP tools

Signed webhooks

Framework backends

Integration test matrix

Explore every use case

Follow an end-to-end tutorial

Run the reference examples

Try the API Playground

Read the Execution Fabric guide

​Choose an integration surface

​Run your first durable task

​Run a governed mission

​Build from a tested example

Durable tasks

Memory federation

MCP tools

Signed webhooks

Framework backends

Integration test matrix

Choose an integration surface

Run your first durable task

Run a governed mission

Build from a tested example