Skip to main content
Every tutorial starts with a credential boundary, builds one complete path, tests its failure states, and ends with observable readback and cleanup.

Open the framework matrix

Compare every supported language, runtime, API plane, credential location, and recommended integration path before choosing a tutorial.

Start with a Praxa workflow

Run a durable task

Submit, poll, stream, and optionally cancel an Execution Fabric run with a personal server-side API key.

Run a mission lifecycle

Create a budgeted Gateway mission, resume SSE, signal, cancel, and read the terminal projection.

Federate existing memory

Read from Mem0, Zep, Graphiti, LangGraph, Letta, OpenAI Agents, or a custom source without migrating provider data.

Use hosted memory candidates

Create, query, export, and erase isolated portable candidates in the qualification-preview plane.

Add MCP tools

Register or remotely connect all 12 Aura-compatible governed tool contracts with approval and scope checks.

Receive webhooks

Verify raw signatures, deduplicate deliveries, acknowledge quickly, and reconcile durable run state.

Web and server frameworks

TypeScript

Use the official SDK or native Node.js fetch.

Next.js

Build an App Router backend-for-frontend.

Nuxt

Use Nitro routes and private runtime config.

Express

Add a validated Express 5 boundary.

Cloudflare Workers

Use edge secrets and a bounded Worker handler.

Python

Build a reusable HTTPX client and tests.

FastAPI

Add dependency-based auth and Pydantic validation.

Rust

Use a pooled reqwest client in a trusted server.

Go

Use net/http, contexts, and httptest.

Java & Spring

Use Spring RestClient and safe controller errors.

.NET

Use IHttpClientFactory and typed JSON.

Framework boundary pattern

Compare shared authentication, tenancy, idempotency, and response rules.

Mobile frameworks

React Native & Expo

Call your backend with Fetch and test offline/background recovery.

SwiftUI

Use URLSession, app-session auth, and lifecycle reconciliation.

Kotlin & Android

Use Ktor Client without placing Praxa credentials in the APK.
Mobile and browser applications must call your authenticated backend. Do not embed Praxa API keys, delegated Gateway tokens, provider clients, or webhook secrets in an application bundle.

Agent frameworks

Vercel AI SDK

Adapt package-owned schemas and executable tools to a ToolLoopAgent.

OpenAI Agents

Connect remote MCP and federate a backend-owned session.

LangGraph

Federate long-term store records while excluding checkpoints.

Choose an agent framework

Select the smallest tool, mission, MCP, or memory integration.

Operate and prove the integration

Add observability

Combine run state, resumable events, usage, delivery status, traces, and coverage without logging secrets.

Build resilient event consumption

Pair a durable SSE cursor with a signed webhook inbox and reconciliation.

Test your integration

Run success, denial, replay, isolation, outage, event, deletion, and cleanup checks.

Open the API Playground

Explore generated cURL, JavaScript, and Python requests with disposable least-privilege credentials.

Shared completion criteria

You are done only when the chosen tutorial proves:
  1. credentials stay in the intended trusted boundary;
  2. missing auth and invalid input fail before Praxa is called;
  3. tenant and subject are server-derived;
  4. exact retries reuse the stored body and idempotency key;
  5. under-scoped, revoked, and foreign-tenant requests fail closed;
  6. admission is followed to terminal or effect readback;
  7. logs and artifacts contain no secrets or raw sensitive payloads;
  8. disposable credentials and data are cleaned up.
Last modified on August 14, 2026