> ## Documentation Index
> Fetch the complete documentation index at: https://docs.praxa.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Design with Praxa product capabilities

> Explore Praxa's live and beta product capabilities by outcome without mistaking every product surface for a public API.

The [Capability Atlas](/overview/capabilities) separates developer contracts
from product experiences. A capability can be available in the Praxa product
without being exposed as a public SDK, CLI, MCP tool, or HTTP endpoint.

## Choose an outcome

<CardGroup cols={2}>
  <Card title="Chat and orchestration" icon="comments" href="/product-guides/chat-and-models">
    Conversation, routing, planning, delegation, and governed execution.
  </Card>

  <Card title="Memory and personalization" icon="brain" href="/product-guides/memory-and-personalization">
    Recall, preferences, context, and evidence-aware personalization.
  </Card>

  <Card title="Research and media" icon="magnifying-glass" href="/product-guides/research-documents-and-media">
    Search, extraction, documents, images, audio, and citations.
  </Card>

  <Card title="Automation and workflows" icon="gears" href="/product-guides/automations-and-plans">
    Scheduled, recurring, and event-driven product workflows.
  </Card>

  <Card title="Agents and specialists" icon="robot" href="/product-guides/custom-and-multi-agent">
    Specialized agents, collaboration, and custom agent experiences.
  </Card>

  <Card title="Teams and organizations" icon="users" href="/product-guides/teams-organizations-and-social">
    Shared collaboration and organization-facing product capabilities.
  </Card>
</CardGroup>

## Translate a product need into a developer integration

1. Find the outcome in the Capability Atlas.
2. Check its status and listed surfaces.
3. Open the related product guide for testable examples.
4. If a developer contract is listed, follow its tutorial and reference.
5. If no developer contract is listed, use the product surface; do not infer an
   undocumented API from the capability name.

<Card title="Browse all 63 provided capabilities" icon="grid-2" href="/overview/capabilities">
  Filter mentally by audience, surface, and status, then open the matching
  outcome guide.
</Card>