Pricing Docs MCP

Human Testers for Your AI Code

Call on-demand professional testers through an API. Get results in minutes and only pay for time-spent testing.

Try it on your site

Free To TryNo credit card required
$npx runhuman
Use with Claude Code
#67Open
Claude AI
Claude Code5 minutes ago

Added OAuth login and streamlined checkout

runhuman2 minutes ago

tested by JordanJordan MiguelMiguel

  • Authentication
    0:15
  • OAuth login flow
    0:32
  • Password reset
    0:58
  • Checkout flow
    1:24
  • Mobile button alignment
    1:47
checkout-test.mp4
1:47 • 3.2 MB
<2min avg wait time Screenshot & video recordings 99.9% uptime
Pricing

10x Cheaper Than AI Computer Use

On-demand usage billing at $0.0018/sec of human testing time.

20-step test:
$0.189
humans
vs
$1.94
Opus 4.5
Costs scale linearly, not exponentially
No token costs for screenshot processing
POPULAR

General Use

Most popular for CI/CD pipelines

$0.0018 /second
Wait Time
<5 minutes
SLA Guarantee
Full refund if missed
Example Cost
60s test = $0.108
120s test = $0.216
✓ Real human testers
✓ Video recordings included
✓ AI-extracted results
✓ API & MCP support

Real Human Feedback

Your product is tested by real humans using real accounts. Test complex SSO/authentication user flows, catch UI/UX issues, and other AI blindspots.

Real Human Feedback

CI/CD Integration

Integrate easily with our GitHub Action or use any CI/CD pipeline including Jenkins. Add human verification to your automated deployment workflow.

CI/CD Integration

Detailed Results

Receive richly annotated results in your custom schema that include a video recording of the test session, screenshots, and console logs.

Detailed Results

Designed for AI-native Teams

Full featured dashboard, MCP, and API allows both your teammates and your AI agents to run and manage tests with ease.

Designed for AI-native Teams

Use Runhuman with
any framework

How it works

3 ways to call humans

Pull Request #123 feat: new checkout flow ● Checks: 3 passing QA Test Running

GitHub Action

Trigger human QA tests during PRs or deployments with our GitHub Action

Try GitHub Action
Coding Agent MCP Protocol create_job()

Agent MCP

Let your agent call a human tester to navigate complex frontend features or test auth

Try MCP Server
your-app.ts import { runhuman } from 'runhuman' const result = await runhuman ( { url : 'https://myapp.com' , description : 'Test checkout' , schema : { success: boolean } } ) // { success: true } POST /jobs

REST API

Incorporate human testers to your bespoke automation pipelines with our REST API

Read API Docs

Trusted by developers worldwide

@alexdev @alexdev

I build AI workflows that need human taste and judgment at certain steps. Before Runhuman, that meant stopping everything and doing it myself, or managing testers. But now, i have access to people via API, a Task Rabbit for Claude to use to get unstuck or to verify he's not building something insane. It's incredible that my AI agents can run humans without me!

@mikejy @mikejy

Integrating Runhuman was a game-changer for my AI agents. Real human feedback in the loop means they actually get things right the first time.

@sococa @sococa

I integrated Runhuman into all our CI pipelines. It's very cheap and fast using the Instant tier for critical flows and the General Use tier for everything else. We're shipping faster than ever with real people validating our features, UX, and overall experience on every push. QA as a Service!

@edwardchen @edwardchen

We trust our releases more now. That confidence alone is worth it.

@CCPires @CCPires

Runhuman helps me catch the things automated tests miss. With a simple API call, I get real human feedback that makes my releases more reliable and my AI workflows feel safer.

@kenji_m @kenji_m

Getting real human validation in my development workflow has been incredible. The structured feedback helps me iterate faster and ship with confidence.

@tyler-mills @tyler-mills

Simple API, real humans, actual results. Runhuman gives me the human-in-the-loop validation I need without the overhead of managing testers.

@priya

I signed up and went through the full onboarding flow. Account creation was very smooth and fast. I tested the Playground and explored how tests are set up in UI mode (URL selection, test instructions, timing, and output schema). I tried running a real test on a live website (Zara DE) to understand the full flow. At that point, I realized that running tests requires creating an API key, which makes sense since the product is clearly built for real, production-level use rather than a simple demo. Even without running the final test, the experience made it very clear how Run Human is intended to be used: it's developer-focused, structured, and designed for serious human-in-the-loop QA rather than a toy tool. The boundaries between setup, execution, and human validation are very nice.

Ready to add human QA to your pipeline?

Get started in minutes with our simple API.