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

# Unified Actions

> Normalized endpoints for documents, identity, and permissions across every connector.

The Unified Actions expose the same normalized schema across every connector in a category. Instead of learning each provider's API format, authentication scheme, and data model, you write your integration once and StackOne handles the differences:

* **Data models** — consistent field names and structures across providers
* **Pagination** — cursor-based pagination works the same whether the provider uses offsets, pages, or cursors
* **Error formats** — standardized error responses, with provider-specific details when available

<Tip>
  **Building AI agents?** Use the [Call Actions](/embed/call-actions/overview) protocols instead — MCP, the Agent SDK, A2A, or RPC. Same data, optimized for LLM tool calling.
</Tip>

<CardGroup cols={3}>
  <Card title="Documents" icon="file-lines" href="/documents/introduction">
    Files, folders, and drives — search, upload, and download across storage providers.
  </Card>

  <Card title="IAM" icon="id-card" href="/iam/introduction">
    Users, groups, roles, and policies across identity providers.
  </Card>

  <Card title="Permissions Check" icon="user-check" href="/permissions-check/introduction">
    Verify what a user can access before your agent acts.
  </Card>
</CardGroup>

## Resources

<CardGroup cols={2}>
  <Card title="Embed Overview" icon="map" href="/embed/getting-started">
    The path to embedding StackOne in your product, from setup to production.
  </Card>

  <Card title="API SDKs" icon="cube" href="/platform-api/api-sdks">
    Official client SDKs for the StackOne API — TypeScript, Ruby, PHP, Java, and C#.
  </Card>
</CardGroup>