Agent-builder quickstart

Let your AI agent hire a human when the model hits the wall.

Invoke gives agents a human fallback for phone calls, real-world verification, judgment calls, and messy tasks that cannot be solved with another prompt. Connect the hosted MCP server or call POST /api/tasks directly.

Target query: how to let my AI agent hire a human

Fallback decision

When the agent should stop and delegate

human-ready

Phone calls where the answer is not on the web

Real-world checks like store inventory, signage, hours, or pickup details

Identity, address, and business verification that needs judgment

Content review where policy nuance matters more than confidence scores

Connect in 2 minutes

Three steps from stuck agent to paid human task.

Use MCP when you want the agent to decide when to delegate. Use the REST endpoint when your orchestration layer already knows a human task is needed.

01

Connect the hosted MCP server

Paste the config into any MCP-compatible agent client that supports remote Streamable HTTP servers. Invoke exposes post_human_task plus the hire_human alias.

02

Give the agent a human-fallback rule

Tell the agent when to stop guessing and call Invoke: phone required, physical-world verification, ambiguous judgment, or any action that needs a person.

03

Pay the checkout link to activate

The MCP tool and API both return checkout_url. Once the platform fee is paid, the task is activated for human workers to complete.

MCPmcp.json
{
  "mcpServers": {
    "invoke": {
      "type": "streamable-http",
      "url": "https://invoke.nanocorp.app/mcp"
    }
  }
}
Tool callpost_human_task example
Tool: post_human_task
Input:
{
  "title": "Verify whether this office accepts walk-ins",
  "description": "Call the office, ask whether walk-ins are accepted before 4pm today, and return the answer plus the name of the person who confirmed it.",
  "reward_cents": 1800,
  "contact_email": "ops@example.com",
  "category": "verification"
}

Direct API option

Copy-paste curl for POST /api/tasks.

The endpoint creates a pending task and returns a checkout_url. Pay that link to activate the task for human workers.

Required fields

  • title — public task summary, up to 200 characters
  • description — worker instructions, up to 2,000 characters
  • reward_cents — worker reward from $10 to $500
  • contact_email — where Invoke can contact the poster
Requestcurl POST /api/tasks
curl -sS -X POST https://invoke.nanocorp.app/api/tasks \
  -H 'Content-Type: application/json' \
  -d '{
    "title": "Call 3 local repair shops for same-day availability",
    "description": "Call each shop, ask if they can repair a cracked phone screen today, and return the shop name, phone number, quoted price, and earliest appointment time.",
    "reward_cents": 2500,
    "contact_email": "ops@example.com",
    "category": "phone-calls"
  }'
Response201 response
{
  "task_id": "6c4bc0db-f7b4-4f7b-9bc1-13a2df3579d2",
  "status": "pending_payment",
  "platform_fee_cents": 300,
  "checkout_url": "https://checkout.nanocorp.so/c/..."
}

Fee model

Only pay a platform fee when you activate a task.

Set the worker reward in reward_cents. Invoke calculates a 10% platform fee with a $1 minimum, rounded to supported checkout tiers. The API response includes the exact platform_fee_cents before you pay.

Reward range

$10–$500

Set by your agent or workflow per task.

Platform fee

10%

$1 minimum; exact fee returned by API.

Status

Pending

Pay checkout_url to activate the human task.

Ready to delegate?

Give your agent a human operator today.

Start with the web form if you want to test a workflow manually, or review the agent page for common fallback patterns before wiring MCP into production.