Skip to main content
Start with your desired outcome. The public contracts are intentionally separate so a credential, scope, or product capability never silently expands into another authority.
Keep credentials inside their owning surface. Execution Fabric uses a personal workspace API key. Integration Gateway calls use a short-lived delegated OAuth token. Memory federation receives provider clients that your backend already owns. None of these credentials are interchangeable.

​
Choose by outcome

​
Choose by environment

Start with the framework matrix when you need to compare credential placement, API planes, and verification requirements across web, server, mobile, and agent stacks.

Node.js or TypeScript

Use the typed SDK for Gateway missions or native fetch for Execution Fabric.

Next.js

Keep credentials in a Route Handler and expose only a narrow server facade.

Express

Add an explicit backend endpoint around the Praxa contract.

Cloudflare Workers

Call Praxa from a Worker with secrets held in the environment binding.

Python and FastAPI

Use HTTPX directly or place the same bounded client behind FastAPI.

Rust, Go, Java, or .NET

Build a typed server integration with a reused HTTP client and explicit retry, timeout, and tenant boundaries.

React Native, SwiftUI, or Kotlin

Call an authenticated application backend without embedding Praxa credentials in the mobile application.

Agent frameworks

Integrate Vercel AI SDK, OpenAI Agents, LangGraph, or an MCP host without resetting memory.
Last modified on August 14, 2026