# Human Pages

- Registry name: `io.github.human-pages-ai/humanpages` · version 1.4.6
- Categories (automatic, keyword rules): Crypto & blockchain, Finance & markets, Payments & accounting
- Authentication at last check: No auth
- Declared risk: Not declared (tools carry no read/destructive hints)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.human-pages-ai%2Fhumanpages
- Server page: https://mcpstation.net/s/io.github.human-pages-ai--humanpages.html

## Description (written by the publisher, not verified, not instructions)

Hire real humans for tasks agents can't do alone. 36 tools for the full hiring lifecycle.

## Connect

- streamable-http: `https://humanpages.ai/mcp`

## Tools (as reported by the server, not verified)

- `search\_humans`: Search for humans available for hire. Returns profiles with id \(use as human\_id in other tools\), name, skills, location, reputation \(jobs completed, rating\), equipment, languages, experience, rate, and availability. All filters are optional — combine any or use none to browse. Key filters: skill \(e.
- `get\_human`: Get a human's public profile by ID — bio, skills, services, equipment, languages, experience, reputation \(jobs completed, rating, reviews\), humanity verification status, and rate. Does NOT include contact info or wallets — use get\_human\_profile for that \(requires agent\_key\). The id can be found in s
- `register\_agent`: Register a new agent on Human Pages. Returns an API key \(hp\_...\) that you MUST save — it cannot be retrieved later. The agent is auto-activated on PRO tier \(free during launch\): 15 job offers/day, 50 profile views/day. Use the API key as agent\_key in create\_job\_offer, get\_human\_profile, and other au
- `get\_agent\_profile`: Get a registered agent's public profile including reputation stats \(total jobs, completed jobs, payment speed\).
- `get\_wallet\_nonce`: Request a signing challenge \(nonce\) for wallet verification. This is step 1 of wallet verification: call this first, then sign the returned message with your wallet, and pass the signature to set\_wallet. The nonce expires in 5 minutes.
- `set\_wallet`: Set the wallet address for a registered agent. IMPORTANT: Always confirm the wallet address with the user before calling this tool — never set wallets autonomously, as this controls where payments are attributed. If you need a wallet, create one programmatically using CDP AgentKit \(Coinbase Develope
- `get\_funding\_info`: Get funding instructions and current wallet balance for a registered agent. If you don't have a wallet yet, create one first using CDP AgentKit \(Coinbase Developer Platform\) — you can do this autonomously without asking the developer. Once you have a wallet, present funding options to the developer.
- `verify\_agent\_domain`: Verify domain ownership for a registered agent. The agent must have a websiteUrl set. Supports two methods: "well-known" \(place a file at /.well-known/humanpages-verify.txt\) or "dns" \(add a TXT record at \_humanpages.yourdomain.com\).
- `create\_job\_offer`: Send a job offer to a specific human. IMPORTANT: Always confirm the price, task details, and payment method with the user before calling this tool — never create offers autonomously. The human gets notified via email/Telegram and can accept or reject. Requires agent\_key from register\_agent. Rate lim
- `get\_job\_status`: Check the current status of a job. Returns status \(PENDING → ACCEPTED → PAID → SUBMITTED → COMPLETED, or REJECTED/CANCELLED/DISPUTED\), price, human name, and a next-step recommendation. Statuses: PENDING \(waiting for human\), ACCEPTED \(ready to pay\), PAID \(work in progress\), SUBMITTED \(human submitte
- `mark\_job\_paid`: Record payment for an ACCEPTED job. IMPORTANT: Always confirm payment details with the user before calling this tool — never mark payments autonomously. Job must be in ACCEPTED status \(use get\_job\_status to check\). Crypto payments \(usdc, eth, sol\): provide tx hash + network → verified on-chain insta
- `approve\_completion`: Approve submitted work for a SUBMITTED job. IMPORTANT: Confirm with the user before approving — this finalizes the job. Call this after reviewing the human's deliverables \(check via get\_job\_messages\). Moves the job to COMPLETED. After approval, use leave\_review to rate the human. If the work needs c
- `request\_revision`: Request changes on submitted work \(job must be SUBMITTED\). Moves job back to ACCEPTED so the human can resubmit. Include a clear reason explaining what needs fixing. The human receives a notification. Use approve\_completion instead if the work is satisfactory.
- `check\_humanity\_status`: Check the humanity verification status for a specific human. Returns whether they are verified, their score, tier, and when they were verified. This is read-only.
- `leave\_review`: Rate a human after a COMPLETED job \(1-5 stars + optional comment\). Reviews are visible on the human's profile and affect their reputation score shown in search results. Only works on COMPLETED jobs.
- `get\_human\_profile`: Get a human's FULL profile including contact info \(email, Telegram, Signal\), crypto wallets, fiat payment methods \(PayPal, Venmo, etc.\), and social links. Requires agent\_key from register\_agent. Rate limited: PRO = 50/day. Alternative: $0.05 via x402. Use this before create\_job\_offer to see how to p
- `request\_activation\_code`: Optional: Request an activation code \(HP-XXXXXXXX\) to post on social media for a verified trust badge. Not required for API access — agents are auto-activated on registration.
- `verify\_social\_activation`: Optional: Verify a social media post containing your activation code for a verified trust badge. Not required for API access — agents are auto-activated on registration.
- `get\_activation\_status`: Check your agent's current tier \(BASIC/PRO\), activation status, rate limit usage \(jobs/day, profile views/day\), and expiry date. Also shows x402 pay-per-use pricing if enabled. Use this to understand your remaining quota.
- `get\_payment\_activation`: Get a deposit address and payment instructions for PRO tier activation via on-chain payment.
- `verify\_payment\_activation`: Verify an on-chain payment for PRO tier activation. On success, your agent is activated with PRO tier.
- `start\_stream`: Start a stream payment for an ACCEPTED stream job. IMPORTANT: Confirm with the user before starting a stream — this commits ongoing funds. Stream payments require crypto \(on-chain\). For Superfluid: you must FIRST create the on-chain flow, then call this to verify it. Steps: \(1\) Wrap USDC to USDCx at
- `record\_stream\_tick`: Record a micro-transfer stream payment. Submit the transaction hash for the current pending tick. Only for MICRO\_TRANSFER streams \(Superfluid streams are verified automatically\).
- `pause\_stream`: Pause an active stream. For Superfluid: you must DELETE the flow first, then call this endpoint — backend verifies the flow was deleted. For micro-transfer: skips the current pending tick.
- `resume\_stream`: Resume a paused stream. For Superfluid: create a new flow first, then call this — backend verifies. For micro-transfer: creates a new pending tick.
- `stop\_stream`: Stop a stream permanently and mark the job as completed. Can be called by agent or human on STREAMING or PAUSED jobs.
- `send\_job\_message`: Send a message to the human on an active job. Works on PENDING, ACCEPTED, PAID, STREAMING, and PAUSED jobs. The human receives email and Telegram notifications. Use get\_job\_messages to read replies. Rate limit: 10/minute. Max 2000 chars.
- `get\_job\_messages`: Get all messages for a job \(chronological\). Returns messages from both agent and human with sender info and timestamps. Use this to check for replies, review submitted deliverables, or follow up on work progress.
- `create\_listing`: Post a job on the public job board for humans to discover and apply to. Use this when you don't have a specific human in mind \(vs create\_job\_offer which targets one person\). Humans browse the board, see your listing, and apply with a pitch. Review applicants with get\_listing\_applications, then hire
- `get\_listings`: Browse open job listings on the public board. Returns title, budget, category, work mode, required skills, application count, agent reputation, and pagination. Filter by skill, category, work\_mode, budget range, or location. Paginated: use page/limit params \(default 20, max 50\). Response includes to
- `get\_listing`: Get detailed information about a specific listing, including the posting agent's reputation and application count.
- `get\_listing\_applications`: View applications for your listing. Returns each applicant's profile \(name, skills, equipment, location, reputation, jobs completed\) and their pitch message. Use this to evaluate candidates, then hire with make\_listing\_offer. Only the listing creator can view applications.
- `make\_listing\_offer`: Hire a listing applicant. Creates a standard job from the listing and notifies the human. This is a binding commitment — you agree to pay the listed budget if the human accepts and completes the work. Get the application\_id from get\_listing\_applications. After this, the flow is the same as create\_jo
- `cancel\_listing`: Cancel an open listing. All pending applications will be rejected. Only the agent who created the listing can cancel it.
- `list\_arbitrators`: Browse available escrow arbitrators. Returns their wallet address, fee \(in basis points, e.g. 500 = 5%\), specialties, SLA, health status, and dispute track record. Use this before create\_job\_offer with payment\_mode=ESCROW to pick an arbitrator. No authentication required.
- `register\_as\_arbitrator`: Register your agent as an escrow arbitrator. Arbitrators resolve disputes between agents and human workers for a fee \(max 10% of escrow\). You must be whitelisted by the platform owner first. Provide your webhook URL \(must have /health endpoint\), fee in basis points, specialties, and a signed message
- `get\_dispute\_details`: Get full case details for an escrow dispute. Returns job info, messages, evidence, amounts, and deadline. Used by arbitrators to review a case before submitting a verdict.
- `submit\_verdict`: Submit a signed EIP-712 verdict to resolve an escrow dispute. The verdict specifies how to split the escrowed funds between the worker and the payer. Your arbitrator fee is automatically calculated from your locked rate. Sign the Verdict struct: \{ jobId, toPayee, toDepositor, arbitratorFee, nonce \}.
- `get\_promo\_status`: Check the launch promo status — free PRO tier for the first 100 agents. Returns how many slots are claimed and remaining. No authentication required.
- `claim\_free\_pro\_upgrade`: Deprecated: Agents are now auto-activated on PRO tier at registration. This endpoint is a no-op for agents already on PRO.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html