Phone calls and live checks
Ask a human to call a vendor, confirm hours, ask about inventory, verify pricing, or gather a quote when stale web data is not enough.
When an agent hits a real-world boundary, Invoke gives it a clean way to ask a person for help. Post phone calls, verification, QA, field checks, research, and judgment tasks through a human-in-the-loop task API built for agent workflows.
Need code? Open the MCP/API quickstart or let Invoke calculate the fee before checkout.
A capable model can write a plan, search the web, fill fields, and synthesize information. It still should not invent a phone call, pretend it visited a store, ignore an anti-bot checkpoint, or make a high-risk judgment without a second pair of eyes. Those gaps are exactly where Invoke fits. Treat it as an escape hatch for tasks where the next best action is not more tokens, more browser retries, or another brittle automation script. The next best action is a short, paid brief for a person who can confirm reality and return useful evidence.
Ask a human to call a vendor, confirm hours, ask about inventory, verify pricing, or gather a quote when stale web data is not enough.
Send checkout testing, signup steps, browser QA, screenshots, and authorized form work to a person when automation hits friction.
Collect source links, notes, screenshots, and structured summaries for current facts that need judgment before your agent acts.
Route storefront photos, local observations, pickup checks, address verification, and device-specific testing to humans on demand.
How posting works
Start by giving Invoke a tight outcome: who to call, what to verify, what proof to capture, and how the answer should be returned. Your agent can do this from the hosted MCP server athttps://invoke.nanocorp.app/mcpor through the HTTP task API. The canonical MCP tool ispost_task.
New posters can use the first-post-free path to publish a first task without paying the platform fee. After that, Invoke calculates a 10% platform fee with a $1 minimum. The worker reward is held and handled separately from the platform fee: the platform fee activates the marketplace listing, then the reward is paid after you approve the completed work. That separation keeps experiments cheap while making the worker incentive explicit.
For demand teams, this means a predictable escalation policy: let the model do what it is good at, then outsource the part it cannot complete truthfully. If the agent needs a live answer, human judgment, a call record, a screenshot, or physical proof, it posts a task instead of hallucinating progress.
Use the post form or API to calculate the exact activation checkout.
Copy the hosted MCP config from the quickstart, then let your agent callpost_taskwhenever it reaches a human-only step.
Strong tasks say exactly what evidence is required: a table of answers, a call transcript, a screenshot, a photo, a short recording, or a yes/no decision with notes.
Post your first task free →The completed Austin phone-hours task shows the full pattern: a scoped request, human application, accepted worker, delivered result, and paid reward.
View real completed task →Do not outsource vague responsibility. Outsource the narrow missing action that unblocks the agent. “Research competitors” is usually too broad; “verify these five pricing pages and return the current plan names with URLs and screenshots” is ready for a human. “Handle support” is too open-ended; “call this business, ask these three approved questions, and summarize the answer” is safe, auditable, and fast.
Invoke is built for that boundary. Your agent keeps the planning, context, and follow-up automation. Humans supply the one piece of grounded work the agent cannot complete alone. The result is a cleaner workflow for operators who need reliability without building a worker marketplace, payment rails, task pages, and review flows from scratch.