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

# Introduction

> REST API, webhooks, and SDKs for AI-driven UX evaluation.

The Autousers API lets you create evaluations, queue AI personas
("autousers") to rate designs, collect human ratings, compute
inter-rater agreement, and stream events into your own systems.

This is the **developer reference**. For end-user product help (videos,
walkthroughs, conceptual onboarding) see the
[help center](https://autousers.ai/help).

## What you can build

<CardGroup cols={2}>
  <Card title="CI/CD evaluation gates" icon="git-pull-request">
    Block a Vercel deploy or a PR merge if a UX evaluation drops below a
    Krippendorff α threshold.
  </Card>

  <Card title="Live design feedback" icon="figma">
    Queue an autouser pass from inside Figma or a PR comment. Get structured
    ratings back in minutes, not days.
  </Card>

  <Card title="Warehouse sync" icon="database">
    Stream every rating into Looker, BigQuery, or Snowflake via webhooks and
    watch trends across releases.
  </Card>

  <Card title="Agent tools" icon="robot">
    Mount the Autousers MCP server into Claude or Cursor; let the agent create
    and analyse evaluations.
  </Card>
</CardGroup>

## API surfaces

The same `/v1` surface powers four first-party clients. Each is a thin
wrapper over this REST API.

| Surface          | Auth                     | Use it for                                        |
| ---------------- | ------------------------ | ------------------------------------------------- |
| Web app          | Supabase session cookie  | The dashboard at `app.autousers.ai`.              |
| `ak_live_*` keys | Bearer API key           | Server-to-server, CI/CD, the CLI, the MCP server. |
| OAuth 2.1        | Audience-bound HS256 JWT | Third-party MCP apps (Claude Desktop, Cursor).    |
| Figma plugin JWT | HS256 JWT (7-day expiry) | The `Autousers` Figma plugin.                     |

See [Authentication](/authentication) for full details on each path.

## Conventions

The API is **Stripe-style**:

* JSON request and response bodies, `application/json`.
* Cursor pagination via `starting_after` / `ending_before` (see [Pagination](/pagination)).
* Errors share a single envelope with a stable `error.type` taxonomy
  (see [Errors](/errors)).
* Every response carries an `X-Request-Id` header — quote it in support
  tickets.

```bash theme={null}
curl https://app.autousers.ai/api/v1/auth/whoami \
  -H "Authorization: Bearer ak_live_..."
```

## Where to start

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Mint a key, list evaluations, dry-run a new one. Five minutes.
  </Card>

  <Card title="Authentication" icon="key" href="/authentication">
    The four auth paths, the 13-scope vocabulary, key rotation.
  </Card>

  <Card title="Webhooks" icon="webhook" href="/webhooks/overview">
    Stop polling. Verify signatures. Retry semantics.
  </Card>

  <Card title="Integrations" icon="plug" href="/integrations/overview">
    MCP server, CLI, Figma plugin, Chrome extension, SDKs.
  </Card>
</CardGroup>

## Stability

The `/v1` surface is stable. We will not ship a breaking change inside
`/v1`. Once a route, request shape, or response shape is published, it
stays. See [Versioning](/versioning) for the deprecation lifecycle.

## Talk to us

* Bugs and feature requests: [github.com/autousers-ai](https://github.com/autousers-ai)
* Security: `security@autousers.ai`
* Sales: `sales@autousers.ai`