Hire and pay real humans for real-world tasks an AI cannot do itself — on-the-ground photos/video, local verification, price/inventory checks, errands, and physical-world data — paid per task in USDC...
Use this skill when the user (or you, autonomously) needs something done in the physical world: a photo or video from a specific place, verifying a location/business exists, checking a live price or whether an item is in stock, attending or observing something locally, or any task that requires a human's eyes, hands, or presence. Payment is non-custodial USDC on Base via x402 — money goes wallet-to-wallet; human.menu never holds funds.
@humanmenu/mcp (install: npx -y @humanmenu/mcp). It needs:HUMAN_MENU_API_KEY — a human.menu AI client key (free at https://human.menu).HUMAN_MENU_MAX_AUTOPAY_USDC — a safety cap (e.g. "1.00") on automatic payments.@humanmenu/agent-pay CLI installed locally with a funded Base wallet (USDC + a little ETH for gas).doctor (or the check_status / wallet_status tools) to confirm the key is valid and the
wallet is funded before posting paid work.create_task: a clear title, description, price_usdc
(canonical decimal string, min "0.01"), and deliverable_type:text — written answer. acceptance: { text_max_chars }.file — photo/scan/recording. acceptance: { extensions, min_bytes, max_bytes?, mime_types? }.url — a link. acceptance optional: { allowed_domains, blocked_domains, require_ssl, max_length }.
Keep instructions specific and verifiable; tasks that are illegal, deceptive, or invade privacy
are rejected by the content policy.check_inbox (one call: ready deliverables, unanswered
questions, expiring tasks, reputation/credit alerts — each with a suggested action). If a tool
for that isn't available, fall back to list_tasks + list_questions.answer_question (task_id, question_id, body). Good answers
produce good deliverables.unlock_and_pay once a deliverable is ready. It handles the x402 payment
from the local wallet automatically, refuses anything above the autopay cap, and returns the
deliverable plus the on-chain transaction hash. Use dry_run: true to preview the cost first.Before paying, check the submitter's reputation (returned with the deliverable metadata):
deliverables_paid, rejection_rate, reports_against, meets_task_filters. You can also set
reputation filters when creating a task to only accept experienced workers.