---
title: Product and app testing by a real human
description: Hire a real human to test your product, app, or agent flow: onboarding walkthroughs, bug reproduction, usability and accessibility passes, with annotated screenshots or video.
canonical: https://humanforai.dev/use-cases/product-testing
task_type: product_or_app_testing
last-updated: 2026-09-06
---

# Product and app testing by a real human

Automated tests tell you the code works; they can't tell you a first-time user gets lost on step two. One real human walks through your product on a real device, narrates what they expected versus what happened, and hands back annotated screenshots or video your team or your agent can act on.

This file is the machine-readable twin of https://humanforai.dev/use-cases/product-testing. Submit at /request, or read /for-agents for the endpoints.

## When your workflow needs this

- **First-run and onboarding walkthroughs** — a fresh pair of eyes goes from landing page to activated user, flagging every point of confusion.
- **Bug reproduction on a real device** — a human reproduces the report, documents exact steps, and captures the evidence.
- **Usability and accessibility passes** — keyboard navigation, contrast, screen-reader sanity, unclear labels; the `accessibility_and_usability_check` service is the same flow, one field away.

## How to submit it

One JSON request — no auth, no SDK. Or connect over MCP and the human becomes a tool: `claude mcp add --transport http human-for-ai https://humanforai.dev/mcp`. Every task is reviewed by the human operator before acceptance; first response under 12 hours, any day of the week. Free during the pilot.

```
POST https://humanforai.dev/api/v1/tasks
Content-Type: application/json

{
  "task_type": "product_or_app_testing",
  "description": "Walk through signup at [url] as a new user; note every confusing step; stop at the dashboard.",
  "output_format": "annotated_screenshots",
  "contact_email": "you@example.com"
}
```

The response returns a `task_id` and a status URL to poll: submitted → accepted → delivered (or rejected, with a reason). The deliverable also goes to your `contact_email`. Full API documentation: /api.md.

## Questions agents and builders ask

- **What should the task description include?** The URL or install path, the persona to adopt, where to start and stop, and what to pay attention to. Arrange test accounts via `message_human_operator` first — never put live credentials in a task description.
- **What deliverables can I get?** Annotated screenshots, a written report, structured JSON (e.g. issue list with severity), or screen-recorded video.
- **Can an AI agent order testing autonomously?** Yes — agents connect over MCP or REST and submit test tasks like any other tool call.
- **Is unreleased software kept private?** Handled with common-sense discretion; formal confidentiality is available by prior agreement.

## Other things the human does

- /use-cases/human-in-the-loop-api.md — a human-in-the-loop API for AI workflows
- /use-cases/real-world-verification.md — real-world verification by a real human
- /use-cases/ai-output-review.md — human review of AI output
- /use-cases/physical-world-tasks.md — physical-world tasks and local errands

Full catalog: /services.md · connection details: /for-agents.md