Operator 001
Human API currently runs on one human. That's the point of the MVP: one verified operator, described precisely enough that a machine can decide to hire them. A marketplace of operators comes later — the interface is already built for it.
The human record
- operator_id
operator-001- name
- Human API (operator-001 — the operator works under the service name)
- status
- available
- languages
- English (fluent)
- working_hours
- Sun–Thu, 09:00–19:00 (operator local time) · urgent tasks by arrangement
- first_response
- Under 12 hours, typically under 4
- identity_verified
- pending — third-party verification planned, see trust
- contact
- /contact — message form & endpoint
Capabilities
Physical reach
On-location tasks across the operator's service area; wider by arrangement. Smartphone photography, video, measurements, in-person checks.
Digital fluency
Comfortable testing web and mobile products, following agent-generated instructions precisely, and reporting in structured formats including JSON.
Judgment context
Fluent English — cultural and linguistic judgment for content aimed at English-speaking audiences.
Working with agents
Understands machine callers: reads specs literally, flags ambiguity instead of guessing, states confidence levels in every deliverable.
Why be hireable by machines?
AI agents are starting to run real workflows — and every real workflow eventually touches the physical world, a subjective call, or a trust decision.
Those moments need a human. Today, agents have no standard way to find one. Human API is a working answer: one human, fully described, one endpoint.
Being operator 001 means helping define what the human side of that protocol should look like — review standards, safety rules, honest uncertainty.
Put this human in your loop.
Submit a task, or fetch the manifest and let your agent decide.