Skip to main content
Use this atlas to answer two separate questions: what can Praxa do on its product surfaces, and what can your application call through a documented developer contract.
A product capability is not automatically a public API. Follow the linked developer service when one exists. Keep Execution Fabric API keys, Integration Gateway OAuth tokens, and provider credentials in their documented boundaries.

Developer services

Praxa product capabilities

These capabilities are grouped by the product job they support. Each guide includes example outcomes and the runtime boundary you should verify.

Core chat and AI pipeline

9 provided capabilities with examples and supported surfaces.

Agent runtimes and surfaces

6 provided capabilities with examples and supported surfaces.

Memory and personalization

8 provided capabilities with examples and supported surfaces.

Research, documents, and media

7 provided capabilities with examples and supported surfaces.

Browser and computer automation

3 provided capabilities with examples and supported surfaces.

Commerce and real-world actions

5 provided capabilities with examples and supported surfaces.

Communication and inboxes

3 provided capabilities with examples and supported surfaces.

Automations and proactive agent

6 provided capabilities with examples and supported surfaces.

Custom agents and multi-agent

5 provided capabilities with examples and supported surfaces.

Teams, organizations, and social

7 provided capabilities with examples and supported surfaces.

Device and context

4 provided capabilities with examples and supported surfaces.

Core chat and AI pipeline

Agent runtimes and surfaces

Memory and personalization

Research, documents, and media

Browser and computer automation

Commerce and real-world actions

Communication and inboxes

Automations and proactive agent

Custom agents and multi-agent

Teams, organizations, and social

Device and context

Status boundaries

  • Live means the capability is available on at least one listed Praxa product or package surface.
  • Beta means it is reachable only in the documented opt-in, cohort, or sandbox.
  • Partner preview is not general availability.
  • Deployment-specific means your organization must operate or receive an Integration Gateway origin and OAuth flow.
  • Qualification preview means source and deployment exist, but authenticated production proof is still incomplete.
Capabilities that are building, dark, parked, or removed are intentionally absent from the provided-capability catalog. See Service status for the public release model.
Last modified on August 14, 2026