Skip to main content
Production host: Use https://platform.praxa.io/developers for the developer portal. The deployed shell preserves the platform origin through authentication, clears supported email-link credentials from the URL, restores the browser session after reload, and requires durable legal acceptance before developer routes render.
The portal uses your existing Praxa account. It does not create a second identity, subscription, or organization authority.

​
Read the status labels first

This page separates three proof lanes:
  • Live means the capability is deployed and has production evidence.
  • Source-ready means the implementation and repository tests exist, but the current documentation does not claim a migration, Worker deployment, or authenticated production canary for that change.
  • Unavailable means there is no customer-callable product boundary.
Passing source tests does not move a capability into the live lane.

​
Surface truth table

​
Portal-native build surfaces

The source-ready agent and workflow routes keep users on the platform origin. They reuse the same server authorization, row-level security, publishing, metering, and approval rules as the existing Praxa product surfaces. Rehosting the UI does not create a new execution authority. The newer workflow mutation authority is a separate source-ready backend seam and stays hidden until its migration, deployment, and denial/success canaries pass. The draft preview playground is also separate from POST /v1/execute. It tests the selected agent’s current server-owned draft. Preview calls consume real model capacity, do not retain the preview conversation, and do not let the browser inject a model or recover a one-time API-key secret.

​
Run and trace explorer

The current Observe surface shows owner-safe task state, lifecycle phase, projection events, and safe totals. It never exposes raw prompts, private reasoning, executor leases, credentials, provider costs, or margins. Call the live surface a projection timeline, not a full distributed trace. Langfuse and internal task events are implementation infrastructure. A newer source-ready causal-trace contract exposes only value-free lineage and digests; it is not live until its migration, retention worker, permission checks, and redaction canary pass. Neither source creates a tenant-safe replay API or mature receipt by itself.

​
API-key console

The personal console supports list, create, rotate, and revoke. A new secret is shown once. Authoritative storage keeps a SHA-256 hash and display suffix, not recoverable plaintext. The browser cannot select an arbitrary tenant. Organization keys remain unavailable.

​
Account and organization boundary

The source-ready account page edits the authenticated user’s name, nickname, private agent preferences, and avatar. It also shows the account provider, email, verification state, and sign-out action. Praxa’s current production web authentication is OAuth/email-link based; the portal does not pretend there is a separate Praxa password to recover. The source-ready organization page can list and create Praxa organizations, list members, add an existing Praxa username, change eligible member/admin roles, and remove access when the caller has existing owner/admin authority. Membership does not authorize organization-scoped /v1 keys, usage, billing, or execution. Read Agent evaluation datasets for the source-ready dataset boundary and Status and roadmap for activation gates. Developer documentation is published at https://docs.praxa.io.
Last modified on August 14, 2026