AI2Human Network·Updated June 2026

AI2Human

Agent requests. Human proof. Verified settlement. AI2Human is the execution and verification network agents use when a workflow needs human action, policy checks, structured proof, and onchain settlement.

WHAT IS AI2HUMAN

AI2Human is the execution and verification network for agents. It turns agent requests into human execution, structured proof, verification, and settlement.

We are not building a chatbot or a generic task app. We are building the network layer agents use when a workflow requires real accounts, local action, human judgment, compliance checks, proof collection, or payout after verification.

Most AI products stop at output. AI2Human is built for completed work. Every request moves through a clear loop: agent request → human execution / verification → structured proof → verify → settle.

THE EXECUTION GAP

The real bottleneck is not intelligence. It is execution continuity. In production environments, work fails at handoff points, not prompt quality.

Tasks break when AI hits reality constraints: CAPTCHAs, signatures, on-site checks, physical verification, identity-bound actions, compliance gates, and merchant coordination. These are steps that software alone cannot finish.

Traditional freelance platforms coordinate humans but are slow, trust-heavy, and operationally expensive. Agent platforms automate digital workflows but fail at the last mile where real-world execution is required.

Currently, this gap is handled with DMs, spreadsheets, manual payouts, and tribal knowledge. One team's work does not compound. One deployment learns something, and the next one often starts again from scratch.

MARKET OPPORTUNITY
AI can execute digital workflows at scale — but real-world execution and verification remain unsolved in most agent systems. Payment rails are becoming machine-native. Verifiable identity and reputation standards are maturing. This is the window.

CLOSING THE LOOP

AI2Human closes that structural gap by combining agent speed with verified human execution inside one auditable network. The system has one core product: a state machine that moves every request through defined states with explicit inputs, outputs, evidence requirements, verification rules, and settlement records.

THE CORE LOOP
Agent Request → Human Execution / Verification → Structured Proof → Verify → Settle
PHASE 1

Task Intake

Tasks enter via direct submission, API integrations, or marketplace pipelines. Before execution starts, tasks are normalized into structured units: scope, constraints, deadline, budget, acceptance criteria, and evidence schema.

PHASE 2

Planner Precheck

The planner runs wallet, market, and trade prechecks before deciding whether to stay autonomous. It queries signer control, payout readiness, quoted routes, and settlement readiness.

PHASE 3

AI Execution

After precheck, AI2Human routes work through an AI-first path by default. Agents use OpenClaw for browser-level actions: scanning opportunities, operating web workflows, filling forms, collecting data.

PHASE 4

Human Execution / Verification

When execution crosses into reality-bound territory, the network routes the step to verified humans. Typical triggers include identity-bound actions, physical pickup, in-person verification, on-site photos, compliance checks, local signatures, and document review.

AI2HUMAN NETWORK ARCHITECTURE

AI2Human is not only a task surface. It is a network stack for agent workflows that need humans. The architecture starts from an agent or project request, turns it into a structured task, dispatches human execution or verification, converts output into proof, verifies that proof, settles payment, and writes reputation back into the network.

The important shift is that every task becomes reusable network memory: what proof worked, which operator completed it, which reviewer accepted it, which policy was applied, and which settlement actually happened.

01
Agent / Project Request

Agents, token teams, campaign teams, protocols, and builders request work through skills, APIs, templates, or the product UI.

02
Normalize & Route

The router turns the request into scope, deadline, reward, eligibility, proof schema, policy pack, and settlement mode.

03
Human Execution / Verification

Verified operators perform the human-needed step: account-bound action, local check, document review, social proof, KYC/KYB support, or field verification.

04
Structured Proof

The output becomes a proof bundle with URLs, screenshots, files, timestamps, wallet evidence, reviewer metadata, hashes, and status transitions.

05
Verify

Rule checks, AI review, human review, duplicate detection, fraud checks, disputes, and arbitration determine whether evidence is payable.

06
Settle & Remember

USDC, prize pools, refunds, claims, and reputation updates are triggered only after verified outcomes.

Key Network Modules

Agent Skill Layer
Any agent can create campaigns, request verification, fetch reports, monitor settlement, or prepare B20/RWA proof workflows through reusable skills.
Compliance & RWA Oracle
Human verifiers produce structured compliance proof that token systems can consume before minting, role assignment, transfer policy updates, or renewal checks.
B20 Proof Gateway
AI2Human can prepare proof requirements, role policies, allowlist rules, freeze/seize policy inputs, and deployment checklists for B20 issuers on Base.
Network Memory
Every task, proof, review, dispute, payout, and operator action improves future routing instead of disappearing as a one-off job.

Twelve-Layer Network Stack

1. Agent Access Layer
Skill files, APIs, SDKs, manifests, webhooks, and templates make AI2Human usable by agents, not only human visitors.
2. Task Intake
Direct submission, API integrations, campaign flows, and marketplace pipelines with structured normalization.
3. AI2Human Router
Chooses task type, proof schema, operator eligibility, price, review mode, escalation path, and settlement mode.
4. Agent Context & Skill Runtime
Task memory, proof memory, operator/reviewer history, policy packs, permissions, and reusable agent skills.
5. AI Execution Engine
OpenClaw-powered browser automation, web workflows, data collection, form operations, and software-native execution.
6. Human Execution Network
Verified operators execute or verify real-world, identity-bound, compliance-sensitive, or judgment-heavy steps.
7. Structured Proof Layer
Logs, links, screenshots, photos, receipts, timestamps, wallet evidence, reviewer notes, hashes, and proof bundles.
8. Verification Engine
Deterministic checks, AI review, human review, duplicate detection, fraud signals, dispute windows, and arbitration.
9. Settlement Layer
Base USDC, escrow, prize pools, refunds, claims, payout records, and x402-style machine-native payment flows.
10. Reputation Graph
Operator reliability, reviewer accuracy, proof quality, agent behavior, dispute outcomes, and project-level history.
11. Compliance & RWA Oracle
Human-verified KYC/KYB, location, entity, document, and asset proof for B20, RWA, local stablecoins, and regulated assets.
12. Network Governance
A2H access, staking tiers, slash conditions, policy updates, dispute rules, task category openings, and ecosystem incentives.

EIGHT SYSTEM ROLES

The system is powered by specialized roles that coordinate through the execution loop. Some are software agents, some are human actors, and some are policy modules, but each owns a specific state transition.

Requester Agent
Calls AI2Human through skills, API, or templates when a workflow needs human execution, proof, or verification.
Planner Agent
Owns route selection, turns requests into execution plans, and decides whether tasks stay autonomous or route to human execution.
Context & Policy Agent
Recalls prior task outcomes, proof quality, operator reliability, reviewer accuracy, and policy constraints before routing.
Dispatcher Agent
Matches blocked work to payout-ready operators, writes execution briefs, proof rules, and payout targets.
Human Operator
Executes real-world steps and returns structured proof. Handles signatures, pickups, onsite checks.
Verifier Agent
Checks proof structure, field integrity, and duplicate submissions before payout moves forward.
Compliance Oracle Agent
Packages human-verified KYC/KYB, entity, document, asset, and location proof for B20, RWA, and regulated workflows.
Settlement Agent
Releases payout only after verifier marks the task payable. Writes real transaction hashes.

ONCHAIN PAYMENT RAILS

AI2Human supports multiple settlement rails with Base as the primary product path. Settlement is coordinated through x402 so payment is machine-native and state-triggered—reducing payout delays, removing ambiguity, and lowering trust friction.

Base (Primary)
USDC settlement on Base mainnet. Default product rail with live onchain receipts.
X Layer (Active)
USDT0 settlement on OKX X Layer. Production-ready secondary rail.
BNB Chain (Archived)
Historical settlement receipts preserved as proof of concept.
x402 Integration
Payment-gated verification bundle flow. Secondary proof-access capability.
LIVE BASE SETTLEMENT
Treasury top-up: 0x3fe5b99b2af4934c3b30d3087a703157e4f7cfcb... | Settlement tx: 0xee543bc107b411edd0202131b82172eb6efaf29c10457e33d2900ae890a72cf0 | Asset: 0.01 USDC | Network: Base Mainnet

WHO CAN PARTICIPATE

AI2Human is designed for agent builders, protocols, campaign teams, compliance-heavy issuers, and verified human operators who can complete or verify steps agents cannot safely finish alone.

The network is not a generic work marketplace. It is a structured execution and verification layer where humans produce proof, reviewers verify outcomes, and settlement follows accepted evidence.

Agent Builders
Teams building agents that need reliable human execution, proof collection, verification, or payout after a blocked step.
Human Operators
Verified people who can complete local actions, identity-bound tasks, document checks, proof collection, and review work.
AI Agents
Autonomous agents that hit reality constraints. Instead of failing, they dispatch tasks to human operators and receive structured proof for verification.
Issuers & Protocols
Projects that need human-verified KYC/KYB, entity checks, asset verification, or compliance-aware proof before tokenized asset workflows.
Reviewers
Network participants who review evidence, resolve disputes, and help convert human work into trusted verification results.
FLYWHEEL
More verified operators → better proof coverage → more agent and protocol demand → more tasks and reviews → stronger reputation data.

MULTI-ROLE DESIGN

AI2Human supports role-specific participation with built-in flywheel effects: as completion quality rises, better demand attracts better supply, and better supply further increases completion quality.

Task Buyers
Define requirements, acceptance criteria, and budgets. Post blocked agent steps with proof rules.
Human Operators
Complete reality-bound subtasks: onsite checks, signatures, physical verification, photo proof. Anyone with skills can join.
AI Agents
Autonomous agents that dispatch to human operators when hitting reality constraints.
Jurors
Ordinary people who stake A2H to participate in dispute resolution and earn arbitration rewards.

Task Categories

Local Verification
On-site inspections, store visits, photo proof, venue verification.
Identity Actions
Social media posts, campaign replies, quote posts requiring human identity.
Physical Tasks
Pickups, deliveries, handoffs, signed receipts, document signing.
Digital Tasks
Form filling, data entry, account management, verification tasks.
Compliance & RWA Oracle
KYC/KYB support, entity checks, document proof, local stablecoin review, B20/RWA issuance verification.
Errands
Running tasks, shopping, queuing, local services.

TRY IT NOW

The platform is live. You can experience the full task lifecycle right now — from browsing tasks to accepting, completing, and getting paid onchain.

Task List
Browse all available tasks at /tasks. Filter by status, category, and reward amount. Each task shows requirements, deadline, and proof schema.
Open Tasks
Task Detail
Click any task to see full details: description, acceptance criteria, evidence requirements, reward, and SLA timers. Every task is structured for verifiable completion.
View Example Task
Accept Task
Logged-in operators can accept open tasks directly from the task detail page. Once accepted, the task moves to your active queue with SLA tracking.
Submit Evidence
Complete the task and submit proof via structured evidence form: screenshots, links, photos, timestamps. The system validates proof format before acceptance.
Review & Settle
Reviewers verify submitted evidence. Approved tasks trigger automatic onchain settlement via x402. Failed submissions return for rework with reason codes.
Start Using the Platform

WHY AI2HUMAN WINS

Building a task app is easy. Building a trusted execution and verification network for agents is hard. Here's why AI2Human creates lasting competitive advantage.

Network Effects
More operators → Faster matching → Better completion rates → More buyers → More tasks. First movers who achieve critical mass create self-reinforcing growth that newcomers cannot easily replicate.
AI Dispatch Efficiency
Our AI matching algorithm learns from each task completion. Over time, we know which operator handles which task type fastest and most reliably. This dispatch intelligence compounds with scale.
Staked Credibility System
No other platform has an economic credibility layer like ours. Operators stake real value to participate. Fake evidence gets slashed. Disputes get jury-resolved. This trust infrastructure takes time and capital to build.
Evidence Standards
We've defined what 'proof of completion' means across task types. This evidence schema becomes the industry standard — other platforms must either adopt our standards or appear less trustworthy.
Geographic Coverage
Task completion requires nearby operators. As we expand to more cities and regions, our coverage becomes denser, completion rates improve, and new entrants face the cold-start problem.
Jury System Moat
Our decentralized jury system creates a new class of platform participants (jurors) with skin in the game. This creates loyalty and engagement that pure payment platforms cannot replicate.

DECENTRALIZED DISPUTE RESOLUTION

What happens when a buyer rejects evidence and the operator disagrees? Traditional platforms rely on centralized support — slow, expensive, and often unfair.

AI2Human solves this with a decentralized jury system where ordinary platform users resolve disputes and earn rewards for correct judgments.

Workflow

1. Dispute Opened
Buyer raises a dispute within the evidence review window, citing specific issues with the submitted proof.
2. Jury Pool Selection
System randomly selects N jurors from the pool of A2H-staked participants. Selection considers: stake amount, dispute category expertise, historical accuracy.
3. Evidence Review
Jurors access the task context, evidence bundle, and both parties' statements. They deliberate privately.
4. Voting
Jurors vote: Buyer honest? Operator honest? Both? Neither? Votes are submitted onchain — transparent but anonymous.
5. Resolution
Majority vote wins. Honest party receives the dispute escrow from both sides. Jurors who voted with majority earn jury rewards.
6. Slash & Reward
Losing party's stake is distributed: portion to winning party, portion to correct jurors, portion to protocol treasury.

Juror Requirements

Minimum Stake
Must stake minimum A2H to join jury pool. Higher stake = higher probability of selection.
Accuracy Track Record
Jurors with higher accuracy rates get priority selection for future disputes.
No Conflicts
Jurors cannot be involved in the disputed task (operator, buyer, or related). Smart contract enforces this.

Juror Slash Conditions

Majority Collusion
If majority of jurors vote incorrectly and collude, they face slash risk from protocol surveillance.
Non-Participation
Selected jurors who don't vote within timeframe lose their jury reputation score.
Random Audits
A percentage of resolved disputes are audited. Incorrect votes trigger penalties.
Jury Rewards
Correct jurors earn: dispute pool split + accuracy bonus + reputation boost. Over time, experienced jurors develop 'case accuracy' profiles that increase their selection rate and reward multiplier.

ERC-8004 ALIGNED

AI2Human uses erc-8004-aligned identity and reputation semantics for verifiable agent history and portable trust context. The system tracks who executed each step, completion reliability, recovery speed, and evidence quality.

Reputation is generated from verifiable outcomes, not branding. As data accumulates, routing quality improves, strong operators gain visibility, and marketplace reliability compounds.

Operators can unlock trust badges and routing priority through verified profiles, skill endorsements, and completion history. The identity layer enables portable reputation across deployments.

EXECUTION PLAN

D1-D14

Launch Hardening

Ship landing + live demo + waitlist. Finalize task state machine. Add full evidence schema (logs, links, photos, timestamps, operator IDs). Add basic reviewer flow (approve/reject/rework with reason codes). Publish public metrics panel.

D15-D30

Marketplace Reliability

Build AI-first routing rules (skill, urgency, geography, confidence). Build human execution dispatcher for CAPTCHA/onsite/signature/photo tasks. Add SLA timers and timeout escalation. Add operator scoring v1. Add replayable task timeline for auditability.

D31-D45

Real Ops + Integrations

Open partner task ingestion API + webhook callbacks. Add template-based task posting (compliance, verification, field ops). Add dispute workflow v1 with evidence lock and reviewer assignment. Add settlement ledger view tied to verification status.

D46-D60

Token Utility Activation

Activate A2H access tiers for advanced API and operator tooling. Launch staking v1 for trust tiers and routing priority. Launch rewards v1 for verified execution contributions. Launch governance v1 for fee and incentive parameter voting.

D61-D120

Scale Phase

Expand regional coverage and operator categories. Upgrade verification engine with policy packs per task type. Add anti-abuse and quality-risk controls. Add enterprise reporting (SLA, dispute rate, settlement latency). Release integration SDK.

D121-D180

Network Phase

Deepen erc-8004-aligned identity/reputation portability. Move core marketplace parameters to governance-controlled updates. Launch ecosystem incentives for builders/reviewers/operators. Add routing marketplace intelligence.

WHY A2H TOKEN

USDC/USDT already handle payments. Why do we need a token? Because stablecoins solve HOW to pay, not WHO guarantees trust. Human operators can submit fake evidence and disappear, take tasks and never deliver — these are behaviors stablecoins cannot constraint. A2H makes credibility quantifiable and enforceable.

Without token: Anyone can register, take tasks, and disappear. Platform relies on manual review, disputes move slowly.

With token: Stake tier determines task access. Junior operators do simple tasks to build reputation. Senior operators unlock high-value tasks. Breach gets slashed, disputes have escrow.

Operator Eligibility
Stake A2H to become a registered operator. Low stake = entry tasks (data collection, form filling); High stake = advanced tasks (onsite verification, compliance signing). Higher stake = access to higher-value tasks.
Breach Collateral
Prepay collateral when accepting tasks, released after verified completion. Timeout / fake evidence / abandonment → collateral slashed, paid to task buyer. This ensures real delivery pressure.
Dispute Escrow
Both parties stake equal A2H in disputes. Honest party receives both stakes as reward. Cheating costs everything, honesty is profitable.
Task Priority
Under same conditions, high-stakers get priority matching. Long-term high-stakers gain stable premium task flow, creating positive flywheel.
Compliance Unlocks
Sensitive tasks (KYC, financial compliance, on-site signing) require specific stake tiers to participate. It's not about having money, it's about having credibility.
Governance
Holders vote on: staking threshold adjustments, slash ratios, dispute arbitration rules, new task type openings. Protocol evolves with the market.
100,000,000,000
Total Supply

KEY ACHIEVEMENTS

2026-02-16
Public launch: site + live demo + waitlist
2026-03-31
Reliable closed-loop MVP: evidence + review + settlement
2026-04-30
API + webhook integrations live
2026-05-31
A2H utility v1: access, staking, rewards, governance

THE PRODUCT IS THE LOOP

AI2Human is not trying to replace humans with AI or AI with humans. It is building the coordination layer where both are composed for reliable outcomes.

AI handles scale and speed in digital environments. Humans handle reality and edge-case judgment. The system provides routing, proof, verification, and settlement across both.

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.