Back to Home

UserZero Documentation

Automated AI beta testing, QA, and ecosystem integration for your SaaS applications.

How UserZero Works

UserZero acts as your team's autonomous beta tester. Register your SaaS application (like taskflowapp.xyz), provide test credentials, and our AI agents will visually navigate the DOM, click buttons, fill forms, and discover bugs exactly like human users would.

The 24-Hour Testing Cycle

Every 24 hours, our asynchronous cron workers automatically wake up and test your active projects. We deduct 1 Testing Credit per mission. To protect limits, projects are automatically paused if you haven't logged in within the last 30 days. No runaways, no surprise bills.

Plans & Personas

Free TierActive

  • • 1 Project limit
  • • 30 Testing Credits / month
  • • Full API Access

Runs the Typical User persona nightly, ensuring your app's core paths are stable.

Pro Tier$10 / mo

  • • 5 Projects limit
  • • 150 Testing Credits / month
  • • Full API Access

Every 24 hours, it randomly cycles through the Bug Hunter, UX Critic, Accessibility Expert, or Typical User to catch extreme edge cases.

Ecosystem Polling API (Headless Syncing)

UserZero isn't just a dashboard—it's a headless QA engine designed to send context into orchestrators like SpecStack or IDE coding agents like Copilot.

GET/api/v1/projects/[id]/interactions?since=[date]

Authenticates via Bearer Token (UserZero API Key). Pulls all AI insights and artifacts generated since your last poll, bundled with a fresh markdown summary.

{
  "sender": "UserZero: The QA Persona",
  "summary": "# Mission Complete\\nI tested the authentication flow and found that...",
  "entities": [
    {
      "kind": "insight",
      "domain": "engineering",
      "format": "markdown",
      "title": "Missing Loading State on Login",
      "content": "Severity: Medium\\n\\nSteps to reproduce..."
    }
  ]
}

Event-Driven Runs API

Instead of waiting for the daily cron runs, you can trigger UserZero testing dynamically from your CI/CD pipeline (e.g., GitHub Actions) as soon as you deploy to staging.

POST/api/v1/runs

Authenticates via Bearer Token. Triggers a new asynchronous mission.

// Example Payload
{
  "projectId": "proj_123xyz...",
  "persona": "QA Tester" // optional
}

// Response
{
  "success": true,
  "missionId": "miss_456abc...",
  "status": "pending"
}

Feed API

Query a timeline of the most recent insights, metrics, and actions taken by the AI agent on a specific project. Perfect for syncing updates to other AI orchestrators or dashboards.

GET/api/v1/projects/[id]/feed

Authenticates via Bearer Token. Returns the last 50 universal entity nodes associated with the project.

{
  "success": true,
  "data": [
    {
      "id": "ent_abc123",
      "kind": "insight",
      "title": "Authentication Flow Tested",
      "content": "Successfully interacted with login forms...",
      "createdAt": "2026-05-25T12:00:00.000Z"
    }
  ]
}

Model Context Protocol (MCP) Server

UserZero provides a native Model Context Protocol (MCP) server, allowing external AI coding assistants (like Cline, Cursor, or Sidekick42) to securely control UserZero natively from your IDE.

Add the following configuration to your MCP-compatible client to integrate UserZero's toolset autonomously.

{
  "mcpServers": {
    "userzero-qa": {
      "url": "https://userzeroagent.com/api/mcp",
      "env": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}

Available MCP Tools:

get_daily_brief - Fetches synthesized markdown of the day's test insights.

Additional REST API Endpoints

Alongside the main endpoints, UserZero exposes standard read access to core elements for custom dashboard integrations. Provide your token via Bearer Authorization header.

EndpointMethodDescription
/api/v1/projectsGETList all projects owned by the authenticated user.
/api/v1/projects/[id]/insightsGETGet categorized tracking items (Bugs, Recommendations).
/api/v1/projects/[id]/tasksGETGet the actionable To-Do task checklist generated by AI.
/api/v1/projects/[id]/chatPOSTChat programmatically with the project context.

The Universal Node Schema

All data generated by UserZero (findings, bug reports, visual specs) is saved using the Universal Node Schema. Because UserZero and tools like SpecStack speak the exact same underlying language (`kind: "insight"`, `format: "markdown"`), you never need heavy integration adapters. QA automation feeds naturally into your backlog context.