Skip to main content
This page is for teams that run interviews inside their own product, for their own customers. Your application owns the customer experience and how results are presented. User Intuition runs the interviews and returns the evidence.

Start in the sandbox

Build and test against staging before you touch production. The sandbox has its own dashboard, API, and MCP URLs, uses staging API keys, and disables participant links: preview interviews with Test with AI. See the sandbox quickstart.

Keep each customer’s work separate

Give each customer its own organization. A single API key works across every organization its user is an active member of. Name the target organization on every call with the X-UI-Organization-ID header; without it, the request acts in the key’s default organization. See organizations and workspace selection and API keys. The API has no endpoint for creating organizations. To provision an organization for each of your customers, talk to Partnerships.

Run the research workflow

Build a research agent covers the sequence: create a draft, design the plan, choose recruitment, and follow progress and evidence. The study lifecycle lists the state transitions.

Make your integration reliable

Billing

Billing is per interview and per organization. Each interview uses credits based on its format; see billing and credits. Whether a completed interview uses credits depends on its quality rating. Each organization has its own credit balance and payment method, so a newly provisioned customer organization starts with no credits. You set your own pricing to your customers on top of User Intuition’s. Use GET /api/public/v1/usage/interviews to read interview counts and credits used for an organization; see reference and usage.

Runnable examples

The developer examples run in fixture mode with no API key or spending: