Skip to main content
The API Playground is generated from the same checked OpenAPI documents used by this reference. Choose an endpoint in the sidebar, enter a disposable bearer key, review the generated request, and send it to https://api.praxa.io.
Use a disposable least-privilege key. Do not paste provider credentials, Integration Gateway OAuth tokens, webhook signing secrets, production customer content, or organization secrets into the playground.

​
Available API planes

The deployment-specific OAuth Integration Gateway remains in API Reference. It is not included here because each deployment has its own HTTPS origin and token authority; executing those requests against api.praxa.io would teach the wrong contract.

Admit a durable task

Open the interactive request builder for POST /v1/execute.

Create a memory candidate

Open the subject-scoped candidate builder for POST /v1/memory/records.

Authenticate safely

Create a disposable personal key, choose exact scopes, test revocation, and move the request into a trusted backend.

Handle failures

Distinguish validation, auth, conflict, rate-limit, server, and unknown-outcome recovery.

Review endpoint coverage

Map all 15 active operations to scopes, success evidence, negative tests, and cleanup.

​
Test an Execution Fabric request

1

Create a personal workspace key

Open API keys and select only the scopes required by the operation. For example, use execute:write for POST /v1/execute and runs:read for a run read.
2

Open an endpoint

Choose an operation under Execution Fabric. Required path, query, header, and body fields are generated from the OpenAPI contract.
3

Review before sending

For mutations, create one stable Idempotency-Key for the logical request. Reuse it only for exact retries of that body.
4

Verify the outcome

A 202 task response proves admission. Follow the returned run link or event stream until you observe the state your integration requires.

​
Test a memory candidate

Use only disposable content while the authenticated qualification matrix is pending.
  1. Create a portable envelope with a memory:write key and save its candidate ID.
  2. Query the exact subject with a memory:read key and require retrievalMode: "lexical".
  3. Export the subject as NDJSON and preserve X-Praxa-Next-Cursor when present.
  4. Delete with a new stable idempotency key.
  5. Query again and confirm content is absent; export again and confirm a content-free deletion receipt exists.
Deleting a candidate does not delete the original provider record.

​
Understand responses

  • 401 means the key is missing, malformed, revoked, or otherwise invalid.
  • 403 means the authenticated principal lacks authority or is outside the tenant boundary.
  • 409 means a state or idempotency conflict; never retry it blindly.
  • 429 and retryable 5xx responses may include retry guidance.
  • Every credential-bearing request should be treated as no-store by your application.
Every generated endpoint page now includes cURL, Node.js, and Python requests, representative success and problem responses, endpoint-specific verification, retry rules, production boundaries, and cleanup. The interactive form remains generated from the checked OpenAPI schema.

Durable task tutorial

Build the same request into Node.js, Python, Next.js, or a Cloudflare Worker and verify the run end to end.

Memory candidate tutorial

Run the complete create, query, export, deletion, scope, revocation, and isolation matrix.
Last modified on August 14, 2026