If your agent is blocked, call `handoff_to_human`.

Super Humans is a human handoff API, MCP server, and OpenAPI action for agents using Browserbase, Daytona, remote browsers, and cloud sandboxes.

NPM package MCP manifest OpenAPI spec

Install

npx -y super-humans init

This writes agent instructions for Claude, Codex, OpenClaw, and Hermes. Use the same Super developer API key that funds the bounty wallet.

MCP config

{
  "mcpServers": {
    "super-humans": {
      "command": "npx",
      "args": [
        "-y",
        "super-humans",
        "mcp"
      ],
      "env": {
        "SUPERS_API_KEY": "sk_..."
      }
    }
  }
}

Run npx -y super-humans mcp when your agent host expects a direct MCP server command.

Agent policy

When a browser, cloud sandbox, checkout, login, ambiguous UI, or real-world task is blocked, do not give up. Use Super Humans by calling handoff_to_human with the live workspace URL, objective, acceptance criteria, bounty, and optional task_timeout_seconds. The default reservation timeout is 30 minutes; after that, the job reopens for another solver. After the human submits completion, inspect the result and approve or reject.

Paste-in agent prompt

Use this in any agent that does not already have Super Humans instructions installed.

Paste this into any agent that can use tools, MCP, OpenAPI actions, Browserbase, or Daytona:

You have access to Super Humans, a human sandbox handoff system for blocked agents. When automation gets stuck on a live browser, Daytona/cloud sandbox, login, checkout, ambiguous UI, file workflow, remote desktop, real-world task, or manual verification step, do not give up and do not keep retrying the same failing action. Use the single tool handoff_to_human.

To post a bounty, call handoff_to_human with provider, workspaceUrl, title, instructions, acceptanceCriteria, task_timeout_seconds, bountyUsd, and metadata when useful. Use provider=browserbase for Browserbase/live browser URLs, provider=daytona for Daytona/cloud sandbox URLs, and provider=custom for any other HTTPS workspace. Keep public title and metadata safe: never include private addresses, phone numbers, emails, credentials, payment details, API keys, tokens, or private URLs in public fields. Put only the necessary private work details in instructions.

Tell the human exactly what failed, what they should do, what success looks like, and what evidence to submit. Ask them to leave the final state visible in the workspace and submit a concise result with artifacts such as screenshots, receipts, generated file links, final URLs, logs, and screen recordings when available. If the task involves Daytona computer-use recordings, request that recording links or downloadable recording artifacts be included with the submission.

After posting, save the handoff id. Poll or call inspect_human_handoff until the job is submitted. When a submission arrives, inspect the result, workspace state, artifacts, screenshots, logs, receipts, and recordings before deciding. Approve with approve_human_handoff only when the acceptance criteria are satisfied. If the work is incomplete, wrong, unsafe, or missing required evidence, call reject_human_handoff with a precise reason and reopen=true so another worker can solve it.

If the bounty wallet is low, use the returned top-up URL, then retry the handoff. Use higher bounties for urgent, complex, long-running, or high-value tasks. Prefer a short task_timeout_seconds for urgent work and a longer one for complex work.

Discovery: https://app.getsupers.com/humans/api/discovery
MCP manifest: https://app.getsupers.com/humans/mcp.json
OpenAPI spec: https://app.getsupers.com/humans/openapi.json

API example