WhoztaThe right contact, straight to your agent
Give us a URL and the person you need. We'll search across the web to find the right contact — with contact details, social profiles, interests, and supporting evidence.
Every match is cross-checked before it comes back.
Whozta doesn't return a guess with a confidence score attached — it returns a person whose contact details were checked against live signals at request time.
Multi-source matching
Company sites, professional profiles, and CRM history are cross-referenced before a candidate is ranked.
Live verification
Email and phone are checked against current deliverability signals on every request — not a cached snapshot.
Confidence, not guesses
Every result carries a numeric confidence score and its sources, so your agent can decide what to do with a 77% match versus a 94% one.
Continuous refresh
Profiles are re-crawled on a rolling basis so a role change or a bounced email doesn't sit stale for months.
One resolution layer, several agent workflows.
Give an agent a reliable way to find the right human without building a separate people-search workflow for every product.
Outbound agents
Turn an ICP description into a list of named, verified contacts ready for outreach — no manual list-building step.
CRM enrichment
Backfill missing titles, emails, and org data on existing records without a bulk-export-and-reupload cycle.
Recruiting agents
Resolve a role and a company into the person who actually holds it, with a verified way to reach them.
Support routing
Identify the right internal owner for an inbound account before an agent escalates or assigns a ticket.
Use the interface that fits your agent.
Connect through MCP for agent-native tool use, or call the REST API from your own application. The same resolution model works across both interfaces.
MCP server
npx @whozta/mcp
REST API
JSON over HTTPS
TypeScript & Python SDKs
typed clients
Webhooks
verification callbacks
curl https://api.whozta.dev/v1/people/search \
-H "Authorization: Bearer $WHOZTA_API_KEY" \
-d '{
"company": "Vercel",
"title": "Head of Revenue Operations"
}'Core operations
/v1/people/search
Resolve a role + company into ranked, verified people.
/v1/people/:id
Fetch a resolved person by id, with source provenance.
/v1/companies/lookup
Normalize a company name or domain to a canonical record.
/v1/people/verify
Re-verify an email or phone against live signals.
{
"id": "per_example",
"name": "Example person",
"title": "Head of Partnerships",
"company": "Example Co.",
"email": "person@example.com",
"email_status": "verified",
"confidence": 0.94,
"sources": ["company_site", "public_profile"]
}Point your agent at Whozta.
Start with a developer account, connect your agent, and confirm the plan that fits your usage.
Choose the path that fits your workflow.
For testing an integration end to end.
- Developer access
- MCP + REST interfaces
- Community support
For agents running in production.
- Usage-based lookup credits
- Webhook verification callbacks
- Priority email support
- Overage billed per lookup
For high-volume or regulated workloads.
- Volume pricing
- SSO + audit logs
- Dedicated support channel
- Custom data retention terms
Questions, answered plainly.
How does Whozta verify an email before returning it?
Every match is checked against live deliverability signals at request time — not a cached snapshot — and returned with a confidence score and its sources rather than a bare guess.
What's the difference between the MCP server and the REST API?
Same data, two interfaces. The MCP server drops straight into an MCP-compatible agent with no glue code; the REST API is for anything that calls HTTP directly, with typed TypeScript and Python SDKs on top.
Do unused lookups roll over?
Monthly plans reset on the billing date. If you expect a usage spike, the Team plan bills overage per lookup instead of hard-capping requests.
Can I use Whozta for recruiting or people-search outside of sales?
Yes — the underlying resolution (a role and a company into a verified person) is the same whether the agent downstream is doing outbound, recruiting, or support routing.
Is there a rate limit?
Plans can use per-key rate limits to keep throughput predictable. The limit and any dedicated capacity are confirmed for your account and workload.