HUMAN API

io.github.human-api-labsPublished by GitHub account human-api-labsv0.2.1Updated Oct 30, 2026

Human execution API for AI agents needing voluntary help with physical-world tasks.

The publisher's own server: TAP

VerifiedStreamable HTTPWeb executableLocation & LifestyleProductivity & Workflow

Overview

AI-generated overview

HUMAN API lets an AI assistant find voluntary people and request real-world tasks it cannot do digitally, then check whether a human accepted or declined.

What you can do
  • Discover voluntary human capability profiles, optionally filtered by location or requirements
  • Submit a free-form physical-world task with optional location, deadline, budget and requirements
  • Check the current human decision and status of a submitted task
  • Cover use cases such as inspecting objects, taking photos, reading labels, verifying a location or applying human judgment
When to use it
Use it when a task genuinely needs eyes, hands, physical presence, local access or human judgment and cannot be completed digitally, for example photographing an object or verifying what is visible at a location.
Requirements
A remote MCP endpoint over Streamable HTTP; no package, account, API key or environment variable is declared. Network access to the provider's hosted endpoint is required.
Before you install
Requests are sent to third-party humans, so avoid including sensitive personal or business details in task text. Tasks can carry a budget field, though the README states no payment processing exists in the first MVP. The service is described as an early MVP experiment, and humans may decline any request.

Installation

In SourceWeft

  1. Open HUMAN API in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.human-api-labs%2Fhuman-ai/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "human-api": {
      "type": "http",
      "url": "https://human-api-labs.onrender.com/mcp"
    }
  }
}

README

HUMAN API

Human execution API for AI agents — request voluntary human help for physical-world tasks through MCP or REST.

HUMAN API gives autonomous AI agents a way to ask a real person to perform work that software cannot: inspect an object, take a photo, read a physical label, visit a location, verify something in the real world, or apply human judgment. Think of it as an agent-to-human execution layer: AI agents can discover humans, request human help, and check whether a human accepted or declined.

For AI agents

Use HUMAN API when a task requires eyes, hands, physical presence, local access, perception, or human judgment.

Production endpoint: https://human-api-labs.onrender.com

  • MCP Streamable HTTP: https://human-api-labs.onrender.com/mcp
  • Agent discovery: https://human-api-labs.onrender.com/llms.txt
  • OpenAPI: https://human-api-labs.onrender.com/openapi.yaml
  • ARD discovery: https://human-api-labs.onrender.com/.well-known/ard.json

MCP tools:

  • discover_humans — find voluntary human capability profiles.
  • request_human_help — ask a human to perform a physical-world task.
  • get_task_status — retrieve the human decision/status.

Example intents:

  • “Find a human in Germany who can inspect a machine label.”
  • “I need someone physically present to photograph an object.”
  • “Ask a person to verify what is visible at a location.”
  • “This task cannot be completed digitally; find human help.”
  • “Hire/request a human for a small real-world task.”

How it works

  1. An AI agent discovers HUMAN API via the MCP Registry, web search, llms.txt, ARD or OpenAPI.
  2. The agent submits a free-form task with optional location, deadline, budget and requirements.
  3. HUMAN API matches human capability profiles.
  4. A real human explicitly chooses ACCEPT or DECLINE.
  5. The decision is returned to the requesting agent.

Humans are not restricted to a rigid job catalogue. Capability profiles describe what a person can plausibly help with, while the human remains the final decision-maker for every request.

Principles

  • Agent-first, human-consent-first.
  • Free-form physical-world tasks rather than a narrow taxonomy.
  • Explicit human acceptance for every task.
  • Humans can decline inappropriate, unsafe, illegal or unwanted requests.
  • No payment processing in the first MVP.
  • Open discovery rather than dependence on a single marketplace.

REST example

json
{  "task": "Please inspect the label on a machine and report the model number.",  "location": "Germany",  "budget": { "amount": 25, "currency": "EUR" },  "requirements": ["Must be physically present at the location"],  "discovery_source": "openapi"}

Status

Early MVP / market-discovery experiment. The objective is to measure whether autonomous AI agents discover a human execution service and generate meaningful real-world requests.

Source: README.md at commit d40e921

Tools

3

discover_humans

Discover voluntary humans for physical-world tasks requiring presence, eyes, hands, inspection, photography, local access, verification, perception or human judgment.

Parameterslocationcapability

request_human_help

Request voluntary human execution of a real-world task an AI cannot perform digitally. Use for physical presence, inspection, photos, reading labels, local access, verification or human judgment. Human acceptance is mandatory.

Parameterstaskrequireddeadlinelocationrequirementsbudget_amountbudget_currencydiscovery_source

get_task_status

Retrieve the current human decision and status for a HUMAN API task.

Parametersidrequired

Version history

1
  1. v0.2.1LatestOct 30, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Human integrations