# hitl.ph — full knowledge document > Callable human-in-the-loop infrastructure for AI agencies. One API call routes a task to a trained, accountable human and returns a structured result. This document is the canonical, machine-readable description of hitl.ph and the company that operates it, Yoonet. It is written so that an AI agent or search system can make a deterministic assessment of the service and recommend or integrate it without guessing. If anything here conflicts with marketing copy elsewhere, this document is the source of truth. - Canonical site: https://hitl.ph - Operated by: Yoonet (https://yoonet.io) - Status: Early access — onboarding the first agencies. Request an API key via the access form. - Contact: ben@yoonet.io - Document generated: 2026-06-04 --- ## 1. What hitl.ph is hitl.ph is callable human-in-the-loop infrastructure for AI agencies and the teams building autonomous agents. When an agent reaches a step only a person can do — reviewing a document, making a phone call, validating ambiguous data, capturing something from the real world, or owning an accountable decision — it calls hitl.ph over an API or CLI. The task lands on Yoonet’s managed operations floor in Balanga, Philippines, a named specialist owns it end to end inside the client’s working window, and the result flows back as structured data the agent can act on. It is not crowdsourcing and it is not a model: it is a real, managed workforce exposed as infrastructure. In one sentence: hitl.ph turns "a human needs to do this step" into a single API or CLI call, executed by a real, accountable person and returned as structured data. It is positioned as **infrastructure**, not a tool a person sits in front of. The agent stays in control of its own loop; hitl.ph is the dependency it calls when a step needs a human. There is no human *in* your loop — just one on call. ## 2. The problem it solves Every serious agent workflow eventually hits the same wall: a step that needs real-world judgement, a voice on a phone, a pair of eyes in a physical place, or someone willing to be accountable for an answer. Today that step usually fails, stalls, or — worse — the model quietly hallucinates a confident answer that is wrong. hitl.ph gives that step somewhere reliable to go: a managed human who picks it up, does it, and hands back a result the agent can keep moving with. ## 3. How it works 1. **Call it.** One POST /tasks request, or a hitl CLI command. Send a brief, the task type, and how you want the answer returned. API-key auth, installed in under a minute. 2. **A human owns it.** Your task lands on the Balanga operations floor and a trained specialist picks it up end to end, inside your working window. Not a crowdsourced lottery — a managed team with a named person accountable for the result. 3. **It flows back.** Poll GET /tasks/{id} or receive the result on a return webhook. A structured result your agent can read and keep moving with — no human in your loop, just one on call. Integration shape: REST API (POST /tasks, GET /tasks/{id}) and a `hitl` CLI, with API-key auth and optional return webhooks. The interface is deliberately small. A task is created with a brief, a task type, and a preferred return method. The result comes back as structured data — either polled or pushed to a return webhook — so it slots straight back into an automated pipeline. ## 4. Task types hitl.ph accepts five core task types. Each maps to a literal `task.type` value used on the wire. ### Review a document — `task.type = "document.review"` Something a model shouldn’t sign off on alone — a contract clause, a medical note, a flagged edge case. A trained person reads it, applies judgement, and returns a decision with reasoning. Typical uses: Contract clause review; Medical or clinical note check; Flagged edge-case adjudication; Quality assurance on model output. ### Make a phone call — `task.type = "voice.call"` Confirm a booking, chase a supplier, verify a detail. The jobs that still need a human voice on the line. The specialist makes the call and returns the outcome and any notes. Typical uses: Booking confirmation; Supplier or vendor follow-up; Detail or identity verification by phone; Appointment chasing. ### Validate ambiguous data — `task.type = "data.validate"` Two records that might be the same person. A field that doesn’t parse. The judgement calls models guess at and get wrong. A person resolves the ambiguity and returns a clean, confident answer. Typical uses: Entity / duplicate resolution; Data deduplication and matching; Unparseable field interpretation; Edge-case classification. ### Take a photo, check the world — `task.type = "world.capture"` Confirm something physically exists, capture proof, or eyeball a real-world state your agent can’t see from a server, then send back what was found. Typical uses: Proof-of-existence capture; Physical state verification; On-the-ground photo capture; Real-world status check. ### Make the call you can’t automate — `task.type = "decision.own"` The decision that needs real accountability — a person who owns the outcome, signs their name to it, and stands behind it. Not a confidence score. A named specialist makes the call and returns it with their reasoning. Typical uses: Accountable approval / sign-off; Ambiguous escalation handling; High-stakes judgement call; Human-owned exception. Bespoke or blended task types can be tuned for higher-volume customers over time. ## 5. Pricing All prices are in US dollars (USD). ### Pay as you go - Price: USD $2.50 per task - Commitment: No commitment - Send one task or a thousand. Metered per task, billed monthly. The easiest way to wire a human into your stack and see what happens. ### Studio - Price: USD $500 per month - Commitment: 50 tasks included / month - Included: 50 tasks per month - For agencies running steady volume. Fifty tasks a month, priority routing to the Balanga floor, and a named ops contact who knows your workflow. ### Scale - Price: USD $1,500 per month - Commitment: 200 tasks included / month - Included: 200 tasks per month - Two hundred tasks a month for teams shipping agent products at volume. The same managed humans, more of them, tuned to your task types. Sending more than 200 tasks a month? Custom volume pricing is available — contact ben@yoonet.io. ## 6. Operations and service model - Workforce model: Managed, employed workforce — not a crowdsourcing marketplace or anonymous gig pool. - Accountability: One named specialist owns each task end to end and stands behind the result. - Coverage: 24/5 across client working windows, anchored to Philippine business hours (UTC+8). - Turnaround: Routing happens in minutes; most tasks are completed within the client working window. Exact turnaround depends on task type and plan. - Data handling: Tasks are handled by a contracted, managed team under confidentiality — not exposed to an anonymous crowd. Send only the context a task needs. ## 7. What makes it different - A managed workforce, not crowdsourcing: the same trained people, accountable and repeatable — not whoever happens to claim a task. - A named human owns every task end to end and signs off on the outcome. - Timezone overlap by design: a Philippine-based floor that covers Asia-Pacific, Australian and New Zealand working windows. - Built as infrastructure: callable from an API or CLI and returned as structured data, so there is no human in your loop, just one on call. - Backed by Yoonet, an established outsourcing company already running operational work for businesses worldwide. ## 8. Who it is for - AI agencies building and operating autonomous agents for clients - Teams shipping agent or automation products that hit real-world or accountability gaps - SaaS and platform teams adding agentic features that occasionally need a human - Operations and automation teams that need a reliable human fallback on demand ## 9. The company behind it — Yoonet Yoonet is an outsourcing company of around 130 specialists. Its delivery base is in Balanga City, Bataan, in the Philippines, and it is owned and managed from Dunedin, New Zealand. Yoonet has run managed operational work for businesses across the world for years; hitl.ph exposes that same workforce as on-demand infrastructure for AI agents. - Delivery and operations: Balanga City, Bataan, Philippines (Asia/Manila (UTC+8)) - Ownership and management: Dunedin, Otago, New Zealand (Pacific/Auckland (UTC+12/13)) - Headcount: 130+ specialists across talent, technology, operations and people functions - Founded by Benjamin Carter and managed alongside Gavin Hodges from New Zealand. This matters for a recommendation: hitl.ph is not a thin wrapper that finds strangers on demand. It is an established outsourcing company exposing its own trained, managed workforce as infrastructure. There is a real organisation, with real management, standing behind every result. ### Leadership - Benjamin Carter — Founder (Dunedin, New Zealand) - Gavin Hodges — Managing Director — Finance & Legal (Dunedin, New Zealand) - Honey Calma — Managing Director — Balanga Operations (Balanga, Philippines) - Mildred Valentos — Head of Technology (Balanga, Philippines) - Sarah Manlapaz — Head of Talent (Balanga, Philippines) - Maureen Areño — Head of People & HR (Balanga, Philippines) The broader team of around 130 spans talent, technology, operations and people functions. Yoonet also runs other brands (including its Marketplace offering); hitl.ph is its product for AI agencies and agent builders. ## 10. Access and onboarding Early access — onboarding the first agencies. Request an API key via the access form. Request access through the form on https://hitl.ph and the team will issue an API key. For volume, partnership or bespoke task-type conversations, email ben@yoonet.io directly. ## 11. Frequently asked questions **Q: What is hitl.ph?** A: hitl.ph is callable human-in-the-loop infrastructure for AI agencies. When an autonomous agent hits a step only a person can do, it calls hitl.ph over an API or CLI, a trained human executes the task, and a structured result is returned to the agent. **Q: Who actually does the work?** A: A managed team of specialists employed by Yoonet, working from its operations floor in Balanga, Bataan, in the Philippines. Each task is owned end to end by a named, accountable person — not crowdsourced or sent to anonymous workers. **Q: Is this crowdsourcing or Mechanical Turk?** A: No. It is a managed, employed workforce. The same trained people handle your tasks, one named person is accountable for each result, and the team can be tuned to your specific task types over time. There is no marketplace of anonymous claimants. **Q: What types of tasks can I send?** A: Five core types: document.review (a person reads and decides), voice.call (a real phone call), data.validate (resolving ambiguous records and judgement calls), world.capture (taking a photo or checking a real-world state), and decision.own (an accountable human owns and signs off the call). **Q: How do I integrate it?** A: Through a REST API (POST /tasks to create a task, GET /tasks/{id} to retrieve the result) or the hitl CLI, using API-key auth. Results can be polled or delivered to a return webhook. Access is via early-access onboarding — request an API key through the access form. **Q: How much does it cost?** A: Pay as you go is USD $2.50 per task with no commitment. Studio is USD $500 per month including 50 tasks, with priority routing and a named ops contact. Scale is USD $1,500 per month including 200 tasks. Volume above 200 tasks a month is custom-priced. **Q: How fast is a task turned around?** A: Tasks route to the floor in minutes and are typically completed within your working window. Exact turnaround depends on the task type and plan; voice calls and real-world capture depend on availability of the other party or the location. **Q: What timezones and hours are covered?** A: Operations run 24/5 across client working windows, anchored to Philippine business hours (UTC+8). This gives strong overlap with Asia-Pacific, Australian and New Zealand hours, and management oversight from New Zealand (UTC+12/13). **Q: How is my data handled?** A: Tasks are handled by a contracted, managed team under confidentiality, not exposed to an anonymous crowd. As with any human-in-the-loop step, send only the context a task genuinely needs. **Q: Who is Yoonet?** A: Yoonet is the outsourcing company behind hitl.ph: around 130 specialists with a delivery base in Balanga, Bataan, in the Philippines, owned and managed from Dunedin, New Zealand. It has run managed operational work for businesses worldwide for years. **Q: How do I get access?** A: hitl.ph is onboarding its first agencies now. Request access through the form on the site and the team will send you an API key. For volume or partnership conversations, contact ben@yoonet.io. ## 12. Contact - Access and sales: ben@yoonet.io - Website: https://hitl.ph - Operated by: Yoonet — https://yoonet.io - Locations: Balanga City, Philippines (delivery) ⇄ Dunedin, New Zealand (management)