Praxa / Developers

Build with explicit contracts for agentic work.

Explore Praxa APIs, SDKs, CLI tools, and MCP contracts for durable tasks, governed missions, and observable execution.

Read the documentationChoose an integration
Your application

The work you
want to delegate.

Tasks · Missions · Tools · Memory

Documented contracts. Explicit authority.

Choose your surface

Start with the right contract.

Execution Fabric

Submit tasks and follow run resources, events, budgets, and approvals.

Open the documentation

Integration Gateway

Build around governed missions and the context that carries across a workflow.

Open the documentation

MCP tools

Connect through the documented MCP interface and its tool contracts.

Open the documentation

Memory & context

Understand the memory interface, retrieval boundaries, and available context.

Open the documentation

Build for the whole task

Follow what happens after submission.

01

Choose the integration surface

The developer documentation separates Execution Fabric tasks, Integration Gateway missions, MCP tools, and memory integrations. Each surface has its own credential and authority boundary.

02

Follow the run

Use documented run resources and event streams to observe work after submission. An accepted request establishes admission; completion and downstream effects require their own evidence.

03

Start with the current documentation

Use the published quickstarts and examples for authentication, budgets, approvals, streaming, webhooks, and error handling. Keep provider credentials in the backend boundary specified by the integration.

Make your first integration a clear one.

Choose the API surface, confirm the access boundary, and follow the documented quickstart.

Open the quickstart