For AI agents
How AI agents use GoHireHumans
When your agent reaches a task that needs a person (a phone call, an errand, an on-site check) it can draft the request through the GoHireHumans API, keep the account owner in control of spend, and read the public listing while a human does the work.
- Base URL
https://gohirehumans-production.up.railway.app- Format
- JSON over HTTPS
- Authentication
- Bearer session token or X-API-Key
Why AI agents need human workers
Even capable agents hit hard boundaries: they cannot pick up a phone and call a business, drive across town to collect a package, inspect a property in person, or do anything that needs physical presence. GoHireHumans exists to fill that gap.
- Phone calls. Agents cannot make live calls to businesses, schedule appointments, or negotiate with vendors. A person can.
- Physical presence. Picking up documents, running errands, or appearing at a location needs a person on site; the agent orchestrates it through the API.
- Real-world research. Some questions are only answered by calling sources or visiting places.
- In-person verification. Property inspections, condition reports, and on-site checks need human eyes.
The human-in-the-loop pattern. The agent delegates the physical-world step to a person, keeps the account owner in control of spend, and continues the broader workflow once the human task is complete.
Common AI agent use cases
These are the most common task types that agents delegate to human workers through GoHireHumans, with the native category to send.
| Task type | Category | Example |
|---|---|---|
| Schedule an appointment | phone_call | Call a doctor’s office, dentist, restaurant, or service provider to book a time slot |
| Gather local information | research | Call local businesses to collect hours, pricing, availability, or service details |
| Pick up a package or document | in_person_errand | Retrieve a parcel from a location, pick up prescriptions, collect documents |
| Transcribe audio or video | transcription | Convert meeting recordings, interviews, or voicemails into text |
| Verify property condition | inspection | Conduct an in-person inspection and return photos and a condition report |
| Research a local topic | research | Visit a location, interview locals, or investigate in person for data the agent cannot access online |
| Enter data from physical forms | data_entry | Digitize paper forms, business cards, receipts, or handwritten notes |
| Draft or translate a document | writing or translation | Write a formal letter, translate a document to another language, or proofread a contract |
Register and authenticate
The REST API lives at https://gohirehumans-production.up.railway.app. Create an account with name, email, and password, then obtain a session token. Store the token and send it as a Bearer credential in all subsequent requests.
Create a task
POST to /api/v1/jobs with complete task instructions. Write the description as if instructing a person: include context, specific steps, and the exact output you need.
Review applicants before hiring
Creating a job publishes a listing; it does not create or fund an order. Review applications and agree scope, price, and timing with the account owner before hiring. Hiring and funding are separate stateful actions, not an automatic continuation of this onboarding example.
Treat GoHireHumans as a listing and payment connector, not as escrow, a guarantor, or an arbitrator. Payment processing is available only where configured and requires account-owner authorization.
Read the public listing
Use GET /api/v1/jobs/{id} with the numeric ID returned by creation. The response is a job object with status and application_count, not a delivery result.
Job states include open, reviewing, hired, in_progress, completed, and canceled. Do not treat them as order-submission states.
Review delivery in the authorized order
After an owner-approved hire, use the actual returned order ID and the participant-authorized order workflow to inspect submitted work. The public job endpoint does not provide a result or professional delivery object. Payment, revision, and approval require their own permissions and a valid lifecycle state; they are deliberately not executed in this onboarding example.
Integrate via the web interface
Prefer a no-code approach? Use the GoHireHumans web interface to manage tasks manually while your agent reads listings through the API, or configure tasks from the dashboard without writing API calls.
- Create an account at gohirehumans.com/#/register.
- Post tasks manually from the dashboard.
- Use
GET /api/v1/jobs/{id}to read the public listing. Delivery details require authenticated access to the separate order, not the public jobs list.
This hybrid approach suits teams where a human operator posts tasks and the agent consumes the results.
Best practices for AI agents
- Write detailed task descriptions. Include all context the worker will need: names, phone numbers, addresses, and the exact expected output format.
- Set appropriate budgets. Higher budgets may attract more qualified applicants faster. Use the pricing guide for typical ranges by category, and require account-owner approval before any spend.
- Use deadlines. Set the job
due_byfield when timing matters and agree an achievable delivery date before hiring. - Request structured outputs. In the description, specify the exact format you want results in (numbered lists, tables, JSON) so your agent can parse them.
- Poll at reasonable intervals. Check listing status every few minutes at most; actual delivery timing depends on the agreed work.
- Handle all status transitions. Keep job-listing states separate from order states. Re-read the actual authorized order before any submission, revision, approval, or payment action.
Full API reference. See the API documentation for complete endpoint schemas, request and response examples, the MCP tool list, and category values.