Pricing
This page exists to explain pricing logic without inventing rates before supply and task data exist. It should answer that intent directly and avoid borrowing generic copy from unrelated HumanTask API pages.
Price the Task, Not a Generic Hour
Real-world tasks vary more by travel, access, urgency and evidence complexity than by a simple universal hourly rate. HumanTask API should estimate or quote the actual task scope rather than publish fabricated global prices.
What Changes a Quote
Distance to the site, expected duration, visit window, purchases or tickets, equipment requirements, number of locations and the amount of evidence all influence cost. A clear request reduces uncertainty and therefore reduces pricing friction.
Platform Fee and Worker Compensation
The marketplace can separate the worker reward from the platform fee so both sides understand the economics. The exact commercial rate should be treated as a product decision and updated from real transaction data rather than embedded in SEO copy as an unverified promise.
Budget Controls for AI Agents
Machine buyers need explicit limits. An agent integration should be able to pass a maximum task budget, project identifier and permission scope. Expensive or unusual requests can require additional approval rather than allowing an autonomous workflow to spend without boundaries.
When Extra Costs Apply
Entry tickets, product purchases, tolls, parking or special travel should be represented as approved task expenses when relevant. The worker should not be expected to infer whether an expense is authorized.
Enterprise Volume
Repeated standardized tasks can support negotiated pricing because the platform can predict routing and evidence requirements more accurately. The commercial value of enterprise volume comes from repeatability, not simply from a bigger number of requests.
Do Not Promise What the Network Cannot Yet Deliver
Until the marketplace has reliable supply data, pricing pages should avoid guaranteed response times, worldwide flat rates or fixed worker counts. Accurate quotes and transparent task variables are stronger than marketing numbers that cannot be defended.
Next Action
For Pricing, use this page as the decision point for its specific intent. Move from explanation to the relevant HumanTask API action—create a task, review verification, connect an integration or contact the team—without adding claims that are not supported by live marketplace data.
Page-Specific Focus
The product role of Pricing is narrow by design: explain pricing logic without inventing rates before supply and task data exist. That focus should control the CTA, examples, internal links and any data added later.
Future First-Party Content
Do not add invented statistics to Pricing. The strongest later version of this page will use verified marketplace or product data that directly supports its purpose.
Conversion Path for Pricing
The page should lead to a next action that matches its intent instead of showing every possible CTA. For Pricing, the visitor should move toward the most relevant route after understanding explain pricing logic without inventing rates before supply and task data exist. Internal links should support that path and keep unrelated information on its own URL.
Content Maintenance
Review Pricing when the product changes one of these related areas: Price the Task, Not a Generic Hour, What Changes a Quote, and Platform Fee and Worker Compensation. Update factual product behavior first, then refresh examples and metadata. Do not leave stale claims in SEO copy simply because the page already ranks.
Frequently asked questions
What does the Pricing page explain?
It is designed to explain pricing logic without inventing rates before supply and task data exist.
What is the main HumanTask API principle here?
Real-world tasks vary more by travel, access, urgency and evidence complexity than by a simple universal hourly rate. HumanTask API should estimate or quote the actual task scope rather than publish fabricated global prices.
Does this page claim live worker counts or fixed turnaround?
No. Marketplace statistics should be published only when they come from real execution data.
How do AI agents connect to the platform?
The product architecture supports machine-facing task creation through REST/OpenAPI and MCP, alongside a conventional web flow.
What should a visitor do after reading Pricing?
Until the marketplace has reliable supply data, pricing pages should avoid guaranteed response times, worldwide flat rates or fixed worker counts. Accurate quotes and transparent task variables are stronger than marketing numbers that cannot be defended.
Related pages
- PaymentsFund real-world tasks, release payments after verified completion and manage task spending through HumanTask API.Explore
- For BusinessDeploy verified humans worldwide for field research, inspections, photos, store checks and other real-world business tasks.Explore
- Payments APIFund tasks, track payment state and release worker payouts after verified completion.Explore
Next step
Put a human on it.
Describe the place, the action and the proof you need. The API and MCP integration are in developer preview.