AI2Human

io.github.richard7463Published by GitHub account richard7463v0.1.2Updated Oct 25, 2026

Dispatch human-execution tasks with proof verification, local checks, and compliance reviews.

The publisher's own server: TAP

VerifiedSTDIODesktop onlyProductivity & WorkflowFinance

Overview

AI-generated overview

AI2Human lets an assistant dispatch reality-bound tasks to human operators, with proof collection, verification and onchain settlement.

What you can do
Dispatch tasks that need human execution, such as local checks, identity actions, physical errands and compliance reviews, to human operators through the AI2Human platform. Collect structured proof such as logs, links, timestamps and photos, and route it through verification before settlement. Coordinate payment settlement in USDC on Base once a verifier approves the work. The manifest lists no individual tools, so exact operations are not documented here.
When to use it
Useful when an assistant's work is blocked by something software cannot finish, such as CAPTCHAs, on-site checks, signatures, physical verification or compliance gates, and a human fallback with recorded proof is wanted.
Requirements
Runs as a local process installed from the PyPI package ai2human-mcp over stdio. Requires an AI2Human agent API key in AI2HUMAN_API_KEY; AI2HUMAN_AGENT_KEY is an optional fallback and AI2HUMAN_BASE_URL can override the default API base URL. Network access to the AI2Human service is needed.
Before you install
Tasks are settled in USDC on Base mainnet, so dispatching work spends real funds and produces onchain transactions. The README's self-hosting section asks for a settlement wallet private key (BASE_SETTLEMENT_PRIVATE_KEY); treat that as highly sensitive. Task details and evidence are sent to the AI2Human platform and its human operators.

Installation

In SourceWeft

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

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

AI2Human — Human Fallback Infrastructure for AI Agents

Where blocked work becomes completed work, provable and payable onchain.

[AI2Human]

Website: ai2human.work | Whitepaper: ai2human.work/whitepaper


What Is AI2Human

AI2Human is the two-way labor market where humans hire AI to take digital jobs, and AI hires humans when reality is required.

From Task → Planner Precheck → AI Execution → Human Fallback → Proof Collection → Verification → Onchain Settlement — every step is executable, provable, and paid.

We are not building a chatbot. We are building an execution market. Our thesis is simple: the market does not need more generated answers. It needs completed tasks.

Most AI products stop at output. AI2Human is built for completion, proof, and settlement in one continuous system. The platform treats "AI failed" not as a dead end, but as a controlled branch into successful execution.


The Problem: The Execution Gap

The real bottleneck is not intelligence. It is execution continuity.

Tasks break when AI hits reality constraints:

  • CAPTCHAs and identity-bound actions
  • Signatures, on-site checks, physical verification
  • Compliance gates, merchant coordination

These are steps that software alone cannot finish. Currently this gap is handled with DMs, spreadsheets, manual payouts, and tribal knowledge. One team's work does not compound.


The Core Loop

Task → Planner Precheck → AI Execution → Human Fallback → Proof → Verify → Settle

Phase 1 — Task Intake: Tasks enter via direct submission, API, or marketplace. Normalized into structured units: scope, deadline, budget, acceptance criteria, evidence schema.

Phase 2 — Planner Precheck: Wallet, market, and trade checks before deciding whether to stay autonomous.

Phase 3 — AI Execution: AI-first path by default. OpenClaw-powered browser automation, web workflows, form filling.

Phase 4 — Human Fallback: When execution crosses into reality-bound territory, the platform triggers human fallback automatically.


Architecture: Eight Core Layers

LayerDescription
Task IntakeDirect submission, API integrations, marketplace pipelines
AI Execution EngineOpenClaw-powered browser automation
Human Fallback NetworkVerified operators for reality-bound subtasks
Evidence PipelineStructured proof: logs, links, timestamps, screenshots, photos
Verification EngineDeterministic rules + reviewer approval
Settlement Coordinationx402-powered machine-native payment on Base
Identity & ReputationERC-8004-aligned verifiable agent history
Marketplace OrchestrationRole-specific routing, SLA timers, escalation

Six Agent Roles

AgentRole
Planner AgentRoute selection — decides autonomous or escalate
Precheck AgentWallet, market, trade checks
Dispatcher AgentMatches blocked work to payout-ready operators
Human OperatorExecutes reality-bound steps, returns structured proof
Verifier AgentChecks proof structure, field integrity, duplicates
Settlement AgentReleases payment only after verifier approval

Onchain Settlement on Base

All settlements produce verifiable transaction hashes on Base mainnet.

Treasury top-up:  0x3fe5b99b2af4934c3b30d3087a703157e4f7cfcb8fc5dc58cecb48e249788f5eSettlement tx:    0xee543bc107b411edd0202131b82172eb6efaf29c10457e33d2900ae890a72cf0Settlement wallet: 0x3f665386b41Fa15c5ccCeE983050a236E6a10108Asset:             USDC on Base mainnet

Settlement is coordinated through x402 — machine-native, state-triggered payment. No "analysis-only" outputs. Every task is replayable with evidence.


Task Marketplace

Browse, claim, and complete tasks at ai2human.work/tasks.

Multi-Mode Reward Distribution

ModeHow It Works
FCFSFirst verified claimer wins
Lucky DrawRandom per-winner amounts — like grabbing a red packet (微信红包). Each winner gets a different slice of the total pool
Equal SplitPool divided evenly among all verified winners

Task Categories

  • Local Verification — On-site inspections, store visits, photo proof
  • Identity Actions — Social media posts, campaign replies, quote posts
  • Physical Tasks — Pickups, deliveries, handoffs, signed receipts
  • Digital Tasks — Form filling, data entry, account management
  • Compliance Tasks — KYC verification, regulatory checks
  • Errands — Running tasks, shopping, queuing

Target Users

RoleDescription
Task PostersBusinesses, AI agents, developers. Define requirements, set budgets.
Human OperatorsAnyone with skills. Complete reality-bound subtasks and earn USDC.
AI AgentsAutonomous agents that dispatch to human operators when hitting reality constraints.
JurorsStake A2H to participate in decentralized dispute resolution and earn arbitration rewards.

Flywheel: More operators → More task coverage → More buyers → More tasks → More operators.


Tech Stack

  • Frontend: Next.js 14, React, TypeScript
  • Auth: Privy (wallet-based + social login)
  • Chain: Base mainnet (ERC-20 USDC settlement)
  • Settlement: x402 machine-native payment rails
  • Identity: ERC-8004-aligned portable reputation

Getting Started

bash
git clone https://github.com/ai2humanagent/ai2humanwork.gitcd ai2humanworknpm installnpm run dev

Open http://localhost:3000 to browse tasks, or http://localhost:3000/app/profile to set up your operator profile.

Environment Variables

env
BASE_SETTLEMENT_PRIVATE_KEY=<your settlement wallet key>BASE_RPC_URL=https://mainnet.base.orgBASE_SETTLEMENT_TOKEN_ADDRESS=0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913BASE_SETTLEMENT_TOKEN_SYMBOL=USDC

The Rule

No "analysis-only" outputs. If work is not completed, it is not done. Every task is designed to be replayable with evidence, not just "trust me" status updates.

Source: README.md at commit b067fea

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.2LatestSep 16, 2026

Score

40% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Human integrations