treg_people_search $0.001 per call
people.search — routed: best of 27 providers, own keys first. Find people by a free-text description, or by company domain / title / country — one row per person in `people`, its `summary` the provider's evidence to check a brief against (Multi-provider (routed) · People & contact data)
For AI agents: call treg_people_search
POST https://toll402.dev/v1/p/treg.people.search
{
"company_domain": "…"
}Answers 402 with x402 payment requirements; pay with any x402 client (@x402/fetch, x402 for Python, toll402-client, toll402-mcp) or send a prepaid-credits key as x-toll402-key (https://toll402.dev/credits). Paid per call via x402 (USDC on Base) or with a prepaid-credits key (x-toll402-key, card at /credits); charged only on success. Start at /llms.txt or connect the MCP server:
npx -y toll402-mcp · remote https://toll402.dev/mcp.Input schema
{
"type": "object",
"properties": {
"q": {
"type": "string",
"description": "identity; describe the people in words, as a profile would: role, seniority, industry, place, audience ('B2B sales coaches on Instagram with a mostly US audience'). A semantic search over profiles answers it, so creators and influencers too"
},
"company_domain": {
"type": "string",
"description": "identity; the employer's website domain ('stripe.com'): everyone treg's providers list there; with q, the people q describes there (q 'executives')"
},
"title": {
"type": "string",
"description": "identity; a job title ('Head of Tax'); with company_domain, that role at that company"
},
"full_name": {
"type": "string",
"description": "identity; one person's name, to find their profile"
},
"country": {
"type": "string",
"description": "filter; ISO country code, where the provider supports it"
},
"location": {
"type": "string",
"description": "filter; free-text place ('London, United Kingdom', 'Greater Phoenix') passed through to providers that take one; finer than country, never normalised"
},
"limit": {
"type": "integer",
"description": "filter; default 10; rows to return — THE price dial: most providers bill per row. For a list you will check against a brief, ask for more than you will keep (25 to keep 15): some rows will not fit it. With a free-text q a short answer goes "
},
"keywords": {
"type": "array",
"description": "filter; skills, topics or domain terms the person must match ('microservices', 'match analysis') — the SUBSTANCE of most briefs; a provider with no keyword field answers a looser question and ranks below one that has it"
}
},
"additionalProperties": true,
"description": "Send what you know; treg sends each provider only the fields it accepts ({q} | {company_domain} | {company_domain, title} | {title} | {full_name}). On a miss it tries the next provider, cheapest first. Options are X-Treg-Route-* headers, never body fields. The answer is {output, raw, _treg}; X-Treg-Served-By names the provider."
}
MCP
{"mcpServers":{"toll402":{"command":"npx","args":["-y","toll402-mcp"],"env":{"TOLL402_WALLET_KEY":"0x..."}}}}