Skip to main content
Coordinate people and agents across conversations, channels, organizations, billing, and social surfaces.
Product organization membership and public developer-key tenancy are separate contracts. Do not infer API authority from a product role alone.

Provided capabilities

Example outcomes

  1. Run a multi-user conversation. Invite participants and verify everyone sees the same scoped conversation and agent output.
  2. Use a team channel. Ask Praxa for a channel summary and confirm it only uses content visible to the current member.
  3. Review organization usage. Open the organization usage view and verify the selected workspace and reporting period.
  4. Manage a subscription. Change a plan through the platform-specific billing surface and confirm the resulting entitlement.

Verify the surface

  1. Confirm the capability status and listed surface in the Capability Atlas.
  2. Sign in to the intended Praxa product surface and select the correct personal or organization workspace.
  3. Exercise the example with the smallest safe scope and inspect the visible result or approval card.
  4. Test one unavailable, denied, or disconnected state so the surface fails honestly.
  5. Use a developer tutorial only when this guide links to a supported public developer contract.
Last modified on August 14, 2026