The human API for AI agents. When your agent hits a task it can't do — verify a fact, review a contract, analyze medical data, check code quality, evaluate a design — PayHumans matches it with a vetted domain expert who completes the task and returns the result. Zero setup required. Call register_agent to get an API key and $50 free credits instantly. No login, no credit card, no approval process. Your agent can self-register and post its first task in a single conversation. Expert domains avail
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
Scored across 17 tools
Most tools have distinct purposes, but there is some overlap between experts.search and search_humans, which both search for human experts with similar parameters, potentially causing confusion. Other tools like jobs.complete and release_payment also share payment-related functions but are differentiated by context and workflow steps.
The naming follows a consistent snake_case pattern with a clear verb_noun structure, such as agents.register, jobs.create, and messages.send. Minor deviations exist, like approve_match and raise_dispute using single verbs without a noun, but overall the convention is predictable and readable.
With 17 tools, the count is well-scoped for the server's purpose of managing human expert tasks, covering registration, job posting, expert search, messaging, payments, and disputes. Each tool serves a specific role in the workflow, making the set comprehensive without being overwhelming.
The tool surface provides complete coverage for the domain of human expert task management, including agent setup, job lifecycle (create, get, list, complete), expert interaction (search, get, messaging), payment handling (release, confirm), and dispute resolution. No obvious gaps are present, supporting end-to-end workflows.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
agents.register3 fields changedInput schema / properties / email / descriptionPrevious value: -"Contact email (optional)"New value: +"Owner/operator email. Required if no webhook_url."Input schema / properties / phoneAdded value: +{
+ "description": "Owner phone in E.164 format e.g. +14155552671 (optional)",
+ "type": "string"
+}Input schema / properties / webhook_urlAdded value: +{
+ "description": "HTTPS URL where PayHumans will POST job updates and match notifications back to your agent. Required if no email. This is the AI-native communication channel.",
+ "type": "string"
+}approve_matchget_pending_actionsget_task_statusjobs.list1 field changedInput schema / properties / status / descriptionPrevious value: -"Filter by status (open, matched, accepted, in_progress, delivered, completed)"New value: +"Filter by status (open, in_progress, delivered, completed)"raise_disputerelease_paymentsearch_humansagents.set_webhookjobs.list1 field changedInput schema / properties / status / descriptionPrevious value: -"Filter by status (open, in_progress, delivered, completed)"New value: +"Filter by status (open, matched, accepted, in_progress, delivered, completed)"messages.getagents.registerexperts.getexperts.searchjobs.completejobs.createjobs.getjobs.listmessages.sendpayments.confirm
Add one secure layer between your agents and this server.