treg_people_enrich $0.001 per call

people.enrich — routed: best of 28 providers, own keys first. Enrich a person from an email, a LinkedIn URL or a name + company domain — treg picks the provider and names the one that served (Multi-provider (routed) · People & contact data)

For AI agents: call treg_people_enrich
POST https://toll402.dev/v1/p/treg.people.enrich
{
 "email": "…"
}
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": {
  "email": {
   "type": "string",
   "description": "identity"
  },
  "linkedin_url": {
   "type": "string",
   "description": "identity"
  },
  "linkedin_handle": {
   "type": "string",
   "description": "identity"
  },
  "domain": {
   "type": "string",
   "description": "identity"
  },
  "full_name": {
   "type": "string",
   "description": "identity"
  },
  "first_name": {
   "type": "string",
   "description": "identity"
  },
  "last_name": {
   "type": "string",
   "description": "identity"
  }
 },
 "additionalProperties": true,
 "description": "Send what you know; treg sends each provider only the fields it accepts ({email} | {linkedin_url} | {linkedin_handle} | {domain, full_name} | {domain, first_name, last_name}) and fills domain, first_name, full_name, last_name, linkedin_handle, linkedin_url from the rest. Omit a field you don't have: a url field holding something else, such as N/A, is refused (422 invalid_identity). On a miss it tr"
}

MCP

{"mcpServers":{"toll402":{"command":"npx","args":["-y","toll402-mcp"],"env":{"TOLL402_WALLET_KEY":"0x..."}}}}

All tools · OpenAPI