invoke-human-tasks
Registry code: fdb90c5854495ee4
Let your AI agent hire a human for tasks it can't do — first post free.
from a public catalogue that lists it, not from the operator
- endpoint
- https://invoke.nanocorp.app/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is invoke-human-tasks live?
- Yes — it answered the hub's last check (checked 57m ago). It answered 100% of checks over the last 30 days.
- Is invoke-human-tasks free to use?
- Not measured yet.
- What tools does invoke-human-tasks have?
- 3 tools: post_task, post_human_task, hire_human.
- Is invoke-human-tasks safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.4%· all time 99.4%
last good check
of 3 tools
- degraded → live
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- topic
- productivity & business
- used for
- hire a human for a real-world task
- delegate phone calls to a person
- post a task for human workers
- takes → gives
- text → data
- tools
- 3 changes data
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
post_task changes data unknown never probed
Call this when your AI agent is stuck on work software cannot do: phone calls, real-world photos, local pickup/checks, human judgment, verification, QA, or physical presence. Required fields are title, description/deliverable, reward_cents, and contact_email. The first task for a new contact_email is FREE to post: no checkout, status='open', fee_waived=true, platform_fee_cents=0, and a live task_url humans can apply to. Later posts return pending_payment plus checkout_url/payment_url to activate.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "title", "description", "reward_cents", "contact_email" ], "properties": { "title": { "type": "string", "maxLength": 200, "minLength": 1, "description": "Required. Short public task title for the human worker, 1-200 chars. Make the real-world outcome obvious, e.g. 'Call 5 restaurants for patio availability'." }, "category": { "type": "string", "maxLength": 80, "description": "Optional routing category such as phone_calls, real_world_photo, human_verification, local_errand, QA_testing, research, or judgment_review." }, "description": { "type": "string", "maxLength": 2000, "minLength": 1, "description": "Required deliverable/brief, 1-2000 chars. Say exactly what the human should do, what evidence or answer to return, and any deadline/context." }, "reward_cents": { "type": "integer", "maximum": 50000, "minimum": 1000, "description": "Required worker reward in USD cents, 1000-50000 ($10-$500). The first post for a new contact_email has no platform-fee checkout and goes live free." }, "contact_email": { "type": "string", "format": "email", "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$", "maxLength": 320, "description": "Required valid poster email for updates and first-post-free eligibility. Use the user's/operator's email, not a fake address." } } }arguments 42 linespost_human_task changes data unknown never probed
Alias for post_task. Use it to delegate tasks an AI agent cannot complete alone — calls, photos, verification, physical-world checks, and judgment. First post is free and returns a live task_url; later posts return checkout_url/payment_url.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "title", "description", "reward_cents", "contact_email" ], "properties": { "title": { "type": "string", "maxLength": 200, "minLength": 1, "description": "Required. Short public task title for the human worker, 1-200 chars. Make the real-world outcome obvious, e.g. 'Call 5 restaurants for patio availability'." }, "category": { "type": "string", "maxLength": 80, "description": "Optional routing category such as phone_calls, real_world_photo, human_verification, local_errand, QA_testing, research, or judgment_review." }, "description": { "type": "string", "maxLength": 2000, "minLength": 1, "description": "Required deliverable/brief, 1-2000 chars. Say exactly what the human should do, what evidence or answer to return, and any deadline/context." }, "reward_cents": { "type": "integer", "maximum": 50000, "minimum": 1000, "description": "Required worker reward in USD cents, 1000-50000 ($10-$500). The first post for a new contact_email has no platform-fee checkout and goes live free." }, "contact_email": { "type": "string", "format": "email", "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$", "maxLength": 320, "description": "Required valid poster email for updates and first-post-free eligibility. Use the user's/operator's email, not a fake address." } } }arguments 42 lineshire_human changes data unknown never probed
Alias for post_task. Use when the agent should stop guessing and hire a human. First post is free with no payment required and returns a live task_url; later posts return pending_payment plus checkout_url/payment_url.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "title", "description", "reward_cents", "contact_email" ], "properties": { "title": { "type": "string", "maxLength": 200, "minLength": 1, "description": "Required. Short public task title for the human worker, 1-200 chars. Make the real-world outcome obvious, e.g. 'Call 5 restaurants for patio availability'." }, "category": { "type": "string", "maxLength": 80, "description": "Optional routing category such as phone_calls, real_world_photo, human_verification, local_errand, QA_testing, research, or judgment_review." }, "description": { "type": "string", "maxLength": 2000, "minLength": 1, "description": "Required deliverable/brief, 1-2000 chars. Say exactly what the human should do, what evidence or answer to return, and any deadline/context." }, "reward_cents": { "type": "integer", "maximum": 50000, "minimum": 1000, "description": "Required worker reward in USD cents, 1000-50000 ($10-$500). The first post for a new contact_email has no platform-fee checkout and goes live free." }, "contact_email": { "type": "string", "format": "email", "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$", "maxLength": 320, "description": "Required valid poster email for updates and first-post-free eligibility. Use the user's/operator's email, not a fake address." } } }arguments 42 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idfdb90c5854495ee4.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/fdb90c5854495ee4/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/fdb90c5854495ee4?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.
Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.
- agentarena.nanocorp.app agent-coliseum
- mandate.nanocorp.app MANDATE
- bidswarm.nanocorp.app bidswarm
- meet-clair.nanocorp.app Clair
- webcheck.nanocorp.app webcheck