---
title: Real-world verification by a real human
description: Human verification for AI agents: a real person physically verifies businesses, products, addresses, prices, and conditions, and returns evidence — photos, reports, structured JSON.
canonical: https://humanforai.dev/use-cases/real-world-verification
task_type: real_world_verification
last-updated: 2026-09-06
---

# Real-world verification by a real human

Web data lies, listings go stale, and no API can see a shelf. When your agent needs ground truth — does this business exist, is this product in stock, does the address match — a real human goes, looks, and reports back with evidence you can parse.

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

## When your workflow needs this

- **Business and storefront checks** — confirm a company physically exists at its claimed address: signage, opening hours, actual activity, with timestamped photos.
- **Shelf, stock, and price checks** — is the product on the shelf, at what price, in what condition?
- **Deliveries and real conditions** — confirm something arrived, works, or matches its description: packages, installations, venues, printed materials.

## 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": "real_world_verification",
  "description": "Verify that [business] at [address] is open and operating; photograph the storefront and posted hours.",
  "location_required": true,
  "location_detail": "City, address or area",
  "output_format": "text_report_with_photos",
  "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 evidence does the human return?** Whatever you request as `output_format`: a written report, a report with photos, structured JSON, or video. Results state their confidence explicitly.
- **Where can things be verified?** Coverage is confirmed at review: submit with `location_required` true and a concrete `location_detail`; the operator accepts, declines, or counter-proposes a remote alternative before any work starts.
- **How is this different from a data API?** A data API returns what was recorded; this returns what is physically there right now, observed by a person who notices what nobody indexed.
- **What does it cost?** Nothing during the proof-of-concept pilot.

## Other things the human does

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

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