Find contact fields beyond one provider
Route requested work-email and business-phone fields across eligible specialist sources for the known professional.
Waterfall contact data for agent systems
Add waterfall contact enrichment to AI agents.
TargetWise routes each requested work-email or business-phone field through eligible specialist sources and returns one normalized outcome. Company enrichment and reverse email lookup are also available through REST API or MCP.
Built for filtered discovery and selective enrichment, not bulk list building.
Illustrative agent enrichment call
IllustrativeRequestFind a work email for this known professionalProfessional profile supplied · work email requested
TargetWise routeOne entity per lookup
Person + companyResolved
Work emailReturned
—Business phoneNot requested
15+ sourcesavailable for contact waterfall routing
REST + MCPtwo controlled delivery paths
11 toolssearch · enrich · field lookup
25maximum candidates per search page
A tool, not another agent
Give the agent structured company and contact data for the task at hand.
TargetWise can discover a small candidate set, then retrieve selected contact or company fields through a separate operation.
The calling application decides when enrichment is allowed, which identifiers may be sent and which returned fields it will consume. For contact requests, TargetWise routes each field across eligible specialist sources and returns one normalized outcome. Company enrichment and reverse email lookup remain separate supporting operations.
This separation keeps reasoning and retrieval distinct. The agent can explain or act on a returned field, while deterministic workflow logic controls call limits, acceptance rules and downstream writes.
No-match is a valid grounded result.If the requested field is not found, stop cleanly, ask for a stronger identifier or route the task to review. A missing field should never become a model-generated guess.
The agent-facing surface
Small enough to control. Useful enough to complete the task.
Keep data access focused on the entity and fields the current workflow actually requires.
Resolve one known business
Use a company domain or another supported identifier to request available company information.
Use seven exact metered tools
Allowlist only the search, enrichment or field-lookup operation the current task needs without exposing supplier tools or schemas.
Request only documented fields
Keep every call limited to the supported fields required for the current task and avoid unnecessary data collection.
Expose enrichment as an agent tool
Use MCP when an AI host should discover and invoke the capability within your application’s tool permissions.
Keep deterministic calls in application logic
Use REST for explicit orchestration, branching, retries and logging outside the model’s reasoning loop.
A controlled request path
From task context to a clear enrichment outcome.
The agent never needs direct access to the underlying supplier account.
Define the scope
Start with company filters, known domains or a supported entity identifier.
Select the operation
Search for candidates or choose one enrichment or lookup tool for the current decision.
Call one TargetWise tool
TargetWise checks the supplied identifiers, retrieves available data and returns a structured field outcome.
Handle the result
Use returned context or keep unavailable fields unresolved.
Guardrails belong in the workflow
Let the model reason; keep data controls explicit.
A reliable agent workflow defines what can be called, when it can be called and what must happen after each possible outcome. Enrichment is one controlled step inside that system.
Use the model to interpret the task and summarize returned context. Use application logic for field allowlists, call limits, retries, merge rules, audit records and approval before consequential actions.
- Set call limits for each workflow
- Require new identity evidence before rerunning an unresolved request
- No CRM write or outreach action inside the enrichment tool
- Human review before uncertain or consequential downstream use
Recommended branch model
Every request ends in an actionable state
1Data returned — apply field-level acceptance rules
2Some data returned — use only returned fields
3Unavailable — stop or request better identity context
4Operational error — follow the documented recovery path
Agent workflow patterns
Add context at the moment the agent needs it.
TargetWise supplies structured data to the workflow. Your product remains in control of decisions and actions.
Add company context to one incoming record.
Resolve the business already associated with a signup before routing or qualification logic runs.
Prepare context for a known account or attendee.
Request relevant contact or company fields when a brief is generated, not through a background database scan.
Fill one missing field during review.
Enrich the record currently open or assigned while preserving your own merge and approval rules.
Let a user-authorized copilot request B2B context.
Offer a narrow enrichment capability inside a product without turning the agent into a list-building platform.
Frequently asked questions
What to know before you build.
TargetWise provides the enrichment capability; the surrounding agent system keeps permissions, acceptance and actions under application control.
Free plan
Test agent enrichment on tasks you already understand.
Use representative records to evaluate where structured B2B context improves your workflow and where no-match handling matters.