# IAasks > Human actions for AI agents, with human review before execution. Official origin: https://iaasks.com Contact: contact@iaasks.com Official MCP registry name: com.iaasks/agenthands MCP endpoint (Streamable HTTP, OAuth): https://agenthands-pilot.yacestarcrypto.chatgpt.site/mcp MCP Server Card: https://iaasks.com/mcp/server-card AI Catalog: https://iaasks.com/.well-known/ai-catalog.json - [Documentation](https://iaasks.com/agents) - [OpenAPI](https://iaasks.com/openapi.json) - [Capabilities](https://iaasks.com/api/capabilities) - [UCP discovery profile](https://iaasks.com/.well-known/ucp) - [Mission capability schema](https://iaasks.com/ucp/schemas/human-action.json) - [MCP server](https://agenthands-pilot.yacestarcrypto.chatgpt.site/mcp) - [AI Catalog](https://iaasks.com/.well-known/ai-catalog.json) - [MCP Server Card](https://iaasks.com/mcp/server-card) - [Payment methods](https://iaasks.com/api/payments) - [Payment page](https://iaasks.com/payer) ## Workflow GET /api/capabilities to discover services. GET /.well-known/ucp for a machine-readable UCP profile advertising the IAasks REST and MCP services and human-action capability. Connect to https://agenthands-pilot.yacestarcrypto.chatgpt.site/mcp using MCP 2026-07-28 through the authenticated IAasks Site connector. Available tools: iaasks_discover_capabilities, iaasks_create_mission and iaasks_get_mission_status. MCP and REST use the same mission records and human-review lifecycle. Agents without that connector can use the public REST API without an account. POST /api/missions with application/json: requester_name, email, mission_type, description (20–4000 characters). Optional: location, budget, deadline, source. Supported types: field_verification, human_call, app_testing, real_world_data, other. Indicative pilot pricing: human_call from EUR 20, app_testing from EUR 30, field_verification from EUR 60; typical mission range EUR 20–300. Final scope, timing and price require human review and agreement before execution. A pseudonymous agent name is accepted; a valid contact email is required. 201 returns id, status, tracking_token, tracking_url, status_endpoint and created_at. Preserve tracking_token privately. GET /api/missions/{id} with Authorization: Bearer returns status, public_update and timestamps (Unix milliseconds). Use the private tracking_url in a browser. Do not publish tokens or private links. Human review and agreement on scope, price and conditions precede execution. Submission does not initiate payment or guarantee acceptance. Card payment in EUR is available through the official myPOS Payment Tag at https://mypos.com/@YaStar. Enter the agreed amount and use `IAasks – MISSION_ID` as the payment reason. The legal merchant displayed by myPOS is BLUE GOLD CONTROL, the operator of IAasks. Bitcoin payment is available only after IAasks confirms the mission reference and the agreed BTC amount. Discover the current network, address and warnings with GET /api/payments. Never infer or modify a payment address. Confirm it from the endpoint immediately before payment. For another cryptocurrency, first email contact@iaasks.com with the requested asset, network, mission reference and agreed amount. Wait for IAasks to return a compatible wallet address. Never send another asset or network to the published Bitcoin address. Voluntary contributions to support IAasks development are accepted on the payment page. They do not purchase a service, priority or tax receipt. Paris and Île-de-France field pilot; remote work subject to feasibility and availability. Statuses: created, reviewed, assigned, in_progress, delivered, validated, rejected, cancelled. For safe retries, generate a cryptographically random UUID v4 once per mission and send it in Idempotency-Key. Reuse the same key and normalized field values for retries: HTTP 200 with replayed:true returns the original id and private receipt. Different content with the same key returns 409. Protection lasts while the request is retained. Keep this key private like the tracking token. Without the header, do not automatically resubmit after an ambiguous network failure. No webhooks are provided.