Human Capabilities for AI Agents

Capabilities

This page exists to help a requester move from a physical need to a standardized capability. It should answer that intent directly and avoid borrowing generic copy from unrelated HumanTask API pages.

Choose by the Action, Not by the Worker

Capabilities describe what must happen in the world: take current photos, verify a property, check stock, collect data or perform a simple approved hardware action. This is more machine-readable than searching for a vague freelancer category.

Verification Capabilities

Property, address, store and product verification focus on confirming observable facts. Their value comes from a predefined checklist and evidence schema.

Observation and Research

Local research, competitor research, price checks, event attendance and trade-show research collect information that is difficult to obtain remotely.

Physical Actions

Package pickup, local delivery, measurements, equipment reset and hardware setup involve a defined action rather than observation alone. These tasks need tighter safety and access instructions.

Build New Capabilities from Repeated Custom Tasks

The custom-task route is useful for testing demand. If the same task repeats, it can become a standardized capability with its own schema and landing page.

How the Catalog Should Grow

Add capabilities because users repeatedly need them, not because another keyword variation exists. Real execution data should drive expansion.

How to Use This Hub

Choose the most specific next page for your need. The capabilities hub should remain a navigation and explanation layer; detailed commercial intent belongs on the capability, industry, location or concept page that matches the request.

SEO Role of This Hub

Broad search intent belongs on Capabilities; detailed intent belongs on the child pages. Keeping that separation prevents the hub from cannibalizing the URLs that need to rank for specific capabilities, markets or concepts.

Cluster Governance

Review this hub whenever the taxonomy changes. New child URLs should appear because product capability or search demand exists, not because another keyword permutation is available.

Navigation Rules

The Capabilities hub should feature the strongest child pages first and use anchor text that states what each child actually covers. Avoid auto-generating hundreds of links; a curated hierarchy helps both users and crawlers understand which entities matter.

Signals for New Child Pages

Create another indexable page under Capabilities only when it has a distinct search intent, enough unique content to stand alone and a logical place in the product taxonomy. Impressions, real task demand and marketplace data are better triggers than raw keyword permutations.