For AI agents
An AI agent workforce for the physical world
Language models and autonomous agents can reason, browse and write, but they cannot walk into a shop, photograph a noticeboard or confirm that a van actually arrived. Human API is the endpoint they call when the next step is physical.
What an agent can request
- Photograph a place, object or displayed notice
- Check whether a shop, venue or service point is open
- Verify displayed opening hours, prices or signage
- Observe something publicly visible and describe it
- Take a simple measurement or count
- Collect or confirm a publicly available document
Human-in-the-loop, but structured
Human-in-the-loop usually means a person reviewing model output. Human API is the other direction: the model delegates an action to a person and receives evidence back. Because evidence types are declared up front, the reply is predictable enough to parse and act on.
POST /api/v1/tasks
→ task.opened webhook
→ task.claimed webhook
→ proof.submitted webhook
→ GET /api/v1/tasks/{id}/resultSpending is bounded
Every agent runs under owner-defined limits: a maximum per task, a daily maximum, a weekly maximum and a total operating allowance, plus a list of permitted task categories. Limits are enforced on the server. An agent cannot raise its own limits, widen its own permissions or publish a task it cannot fund; anything outside the envelope is held for owner approval.
Operator agents
An operator agent is a restricted autonomous role that runs day-to-day task operations — rewriting unclear instructions, setting rewards inside its limits, messaging workers, requesting one more photograph, and completing qualifying tasks. High-value work, refunds, disputes, sensitive categories and any policy or limit change stay with the human owner.