Ask verified humans
ask_humansSend a decision to ID verified people before you act on it. Several people answer independently, each confirmed with Face ID, and you get back the consensus answer and how strongly they agreed. Use it for judgment calls where being wrong is costly: evals of AI output, tone and intent, whether two things match, moderation edge cases. Send refunds, payments and other money calls with route team. Write the question so a stranger can answer it from the context alone, and never include secrets or more personal data than the decision needs. Live keys use prepaid credit at $0.20 per answer (clips cost more by length), or $0.05 per internal vote with route team; test keys are free and simulated.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"question": "<question>",
"options": "<options>"
},
"name": "ask_humans"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| app | No | Which of the developer's apps this is for, like "support-agent". Default: PLURES_APP, then the default app | |
| fast | No | Paid speed for a decision that can't wait: served first to verified people and pushed at once, with a bonus for answers within a minute. $0.10 more per answer live. Not with route team | |
| team | No | The name of one of the developer's teams, like "Finance", to decide instead of the main team | |
| route | No | verifiers (default) asks ID verified people first. team sends it straight to the developer's own people, for money and account decisions and confidential or policy calls; $0.05 per internal vote live | |
| context | No | The material to judge, as plain text: the AI answer and the policy it should follow, the message, the listing | |
| options | Yes | 2 to 8 possible answers, e.g. ["Yes", "No"] | |
| category | No | A label the developer's routing rules match on, like "refunds"; the rule may choose the route and team | |
| question | Yes | What people should decide, e.g. "Is this customer upset?" | |
| audio_url | No | An https recording people listen to in full before answering, such as a call your voice agent handled. Up to 3 minutes; needs media_seconds | |
| image_url | No | An https image shown with the question | |
| sensitive | No | Set true for violent, graphic or disturbing content, so only people who opted in see it, behind a warning | |
| verifiers | No | How many people answer. Default 3; use 5 for higher stakes | |
| video_url | No | An https video (MP4) people watch in full before answering. Up to 3 minutes; needs media_seconds. Not with audio_url | |
| team_votes | No | With route team: how many people on the team vote; the majority decides | |
| instructions | No | Short guidance shown under the question | |
| wait_seconds | No | How long to wait for the answer before returning a task_id to check later. Default 45, up to 240 | |
| media_seconds | No | Length of the audio or video in seconds. Required with a clip | |
| use_precedent | No | Look in the developer's judgment graph first. When people already settled cases like this (three or more close matches with the same options, all decided the same way), it's decided by precedent at once for $0.05 live; one in ten still goes to people as an audit. Not with route team |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| kind | No | ||
| mean | No | ||
| mode | Yes | ||
| label | Yes | ||
| route | Yes | ||
| votes | Yes | ||
| answer | Yes | ||
| status | Yes | ||
| answers | Yes | ||
| reasons | No | ||
| signoff | No | ||
| task_id | Yes | ||
| agreement | Yes | ||
| contested | No | ||
| with_team | Yes | ||
| decided_by | Yes |