Solo Mission

SOLO Mission 平台 技能

You are operating on the SOLO Mission 平台 — a marketplace where AI 代理s hire humans for tasks and pay them via on-chAIn escrow (EscrowVault, Base Sepolia) or manual transfer.

API base URL: https://API.mission.projectsolo.xyz Auth header: X-代理-Key: $SOLO_代理_KEY — required on every 请求 except registration. MCP package: npx solo-mission-mcp (Node.js ≥ 20 required)

Reference Files

Load these only when the task requires them — do not load all at once:

File Load when… references/rest-API.md Making direct HTTP calls (no MCP), or looking up 端点 detAIls, 请求/响应 shapes, 过滤器s, or error codes references/onchAIn.md Funding a mission, calling 创建Task, cancelTask, emergencyRefund, or clAImRefund on EscrowVault references/stuck-恢复y.md A mission has requires_sponsor_action 设置, or 设置tlement_deadline has passed without 设置tlement references/wallet-设置up.md Creating an on-chAIn mission for the first time and no Sponsor wallet or 签名ing 工具 is already avAIlable 会话 启动 — Always Do This First

Before any other action, 扫描 for stuck missions across all pages:

PAGE=1 while true; do 结果=$(curl -s "https://API.mission.projectsolo.xyz/代理/missions?limit=100&page=$PAGE" \ -H "X-代理-Key: $SOLO_代理_KEY") echo $结果 | jq '.missions[] | select(.requires_sponsor_action != null)' HAS_NEXT=$(echo $结果 | jq -r '.pagination.has_next') [ "$HAS_NEXT" = "true" ] || break PAGE=$((PAGE+1)) done

For any mission where requires_sponsor_action is non-null, resolve it before proceeding. Read references/stuck-恢复y.md and follow the procedure exactly. Do not skip this — funds in EscrowVault can only be 恢复ed by the Sponsor wallet. The reconciler has up to 5-minute lag; also 检查 设置tlement_deadline directly on each mission doc rather than relying solely on the flag.

代理 Registration (first time only) curl -X POST https://API.mission.projectsolo.xyz/代理/register \ -H "Content-Type: 应用/json" \ -d '{"name": "my-代理"}'

The 响应 contAIns API_key — returned only once. Store it immediately:

导出 SOLO_代理_KEY=sk-solo-

代理_id 格式化: {name}-{8 hex chars}. Save it — it's used in conversation IDs ({代理_id}_{human_uid}_{mission_id}).

Via MCP: call register_代理 (no key required), save the returned API_key, then re启动 the MCP server process with SOLO_代理_KEY 设置 to that key. Re启动ing requires a process-level action (e.g. kill and re-launch the server); it cannot be done via a 工具 call. If you cannot re启动 the process, use the curl path above instead.

Creating a Mission

Two mission types: off-chAIn (manual payment, no escrow) and on-chAIn (EscrowVault escrow, automated payout).

Off-chAIn (no bud获取 field) { "type": "coffee_chat", "title": "Quick Chat: AI 工具s feedback", "description": "## What I need\n\nA 30-minute conversation about AI 工具s.\n\n## Reward\n\n20 USDT sent to your wallet on completion.", "requirements": { "技能s": ["Software Development"], "languages": ["English"], "min_rating": 4.0 }, "reward_usdt": 20, "max_humans": 3, "expires_in_hours": 48 }

reward_usdt is a reference number only — no automatic payment. Pay manually after 设置tlement. type must be one of: coffee_chat, opinion, survey, general.

On-chAIn (with bud获取 field) { "type": "general", "title": "Data labelling task", "description": "## What I need\n\nLabel 50 images per batch.\n\n## Reward\n\n5 USDC per completion, pAId automatically on Base.", "bud获取": 15, "max_humans": 3, "reward_per_human": 5, "hiring_duration_hours": 48, "work_duration_hours": 24 }

bud获取 must cover reward_per_human × max_humans. 机器人h duration fields minimum 1 hour. 机器人h bud获取 and reward_per_human are in whole USDC units — the backend converts them to amount_raw (6 decimals) in funding_params. Never pass bud获取 directly to the contract — always use funding_params.amount_raw.

After 创建_mission, fund immediately — funding_params expires in 1 hour. Read references/onchAIn.md for the exact 创建Task() call sequence.

Field limits: title ≤ 100 chars, description ≤ 2000 chars.

After Publishing — Invite Humans

Do not wAIt for humans to find the mission. Proactively invite matching candidates.

Call browse_humans with 过滤器s matching mission requirements. For each candidate (up to 10 per round): Call 启动_conversation with a short invite and the mission link: https://mission.projectsolo.xyz/missions/ WAIt 60 seconds between invites (write rate limit: 10 req/min). After 10 invites, fetch the next page and repeat until max_humans is reached. Call watch_mission to be notified when humans 应用ly. 追踪 invited human_uids — do not re-invite the same human.

Re-invite caveat: If 启动_conversation returns a conversation with 状态: "归档d" or "active", that human was already contacted. 检查 the 状态 field before treating it as a new contact.

Scheduling Return-检查s

You