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.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.
What you can build
CI/CD evaluation gates
Block a Vercel deploy or a PR merge if a UX evaluation drops below a
Krippendorff α threshold.
Live design feedback
Queue an autouser pass from inside Figma or a PR comment. Get structured
ratings back in minutes, not days.
Warehouse sync
Stream every rating into Looker, BigQuery, or Snowflake via webhooks and
watch trends across releases.
Agent tools
Mount the Autousers MCP server into Claude or Cursor; let the agent create
and analyse evaluations.
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. |
Conventions
The API is Stripe-style:- JSON request and response bodies,
application/json. - Cursor pagination via
starting_after/ending_before(see Pagination). - Errors share a single envelope with a stable
error.typetaxonomy (see Errors). - Every response carries an
X-Request-Idheader — quote it in support tickets.
Where to start
Quickstart
Mint a key, list evaluations, dry-run a new one. Five minutes.
Authentication
The four auth paths, the 13-scope vocabulary, key rotation.
Webhooks
Stop polling. Verify signatures. Retry semantics.
Integrations
MCP server, CLI, Figma plugin, Chrome extension, SDKs.
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 for the deprecation lifecycle.
Talk to us
- Bugs and feature requests: github.com/autousers-ai
- Security:
security@autousers.ai - Sales:
sales@autousers.ai