Request contact data for a known professional
Use supported identity context to request available work email or business-phone fields.
Embedded waterfall contact enrichment
Add waterfall contact enrichment to your AI product.
Route requested work-email and business-phone fields across 15+ specialist sources without integrating each provider yourself. TargetWise returns one normalized result; company enrichment and reverse email lookup are available as supporting operations.
Paginated search or one selected entity, with explicit no-match handling.
Embedded product action
IllustrativeRequestAdd business context to this user taskKnown entity · product operation selected
TargetWise routeOne entity per lookup
IdentityResolved
Available contextReturned
—Unused contextIgnored by product
15+ sourcesavailable for contact waterfall routing
RESTfor deterministic product logic
MCPfor agent-host tool calls
11 toolssearch, enrich and field lookup
A retrieval capability, not an agent
Let your product ask for context without giving it an open-ended data platform.
TargetWise handles record retrieval: discover a filtered candidate page or resolve one selected person, company, field or business email.
Your application owns the user experience, selection policy, tool permissions and decision logic. TargetWise owns the record retrieval and normalized outcome.
This boundary works for research assistants, sales copilots and workflow products that need business context at a specific moment—without background scanning, automatic list enrichment or mass export.
Missing data should remain missing.A product should surface no-match, ask for a stronger identifier or continue without the field. A plausible model-generated contact value is not an enrichment result.
Product capabilities
One B2B data layer for application code and agent hosts.
Choose the interface that matches where orchestration belongs in your architecture.
Resolve a known business
Use a domain or another supported identifier to request available company context.
Use one TargetWise product action
Avoid exposing supplier credentials, retrieval logic and response mappings inside your AI product.
Keep deterministic logic in your backend
Select the operation and requested contact fields, enforce limits and handle each result state directly in application code.
Offer enrichment to an AI host
Expose a constrained capability that a host can discover, allowlist and invoke.
Use only what the feature needs
Cap search pages, select one candidate, minimize contact fields and consume only required company-profile fields.
Embedded flow
From user task to returned context in four controlled stages.
Design the product experience for matches and absence before production launch.
Collect identity context
Use the person or company information already supplied in the user’s task.
Set the requested fields
Choose one operation and, for contact enrichment, only the supported fields required by this feature.
Call REST or MCP
Route the single-entity request through the interface your architecture uses.
Present or branch
Handle matched, partial and not-found outcomes explicitly.
Product safeguards
Treat enrichment as an external data boundary in the product.
Validate user-supplied identifiers, constrain which operations and contact fields each feature can request, allowlist the company-profile fields it may consume, and keep credentials and provider details outside model-visible prompts.
Apply per-user or per-workflow call limits, log business outcomes and require additional approval before a returned field triggers a write, export or communication.
- Operation and data allowlists per feature
- One call per entity per action
- Explicit partial and no-match states
- Retry limits with backoff
- Separate approval for consequential actions
Architecture split
Keep each responsibility in the right layer
1Product — permissions and user experience
2Agent — reasoning and tool selection
3TargetWise — on-demand enrichment
4Workflow — acceptance and downstream action
Product patterns
Add business context exactly where the experience benefits.
TargetWise returns structured data; the product determines how that context helps the user.
Find or resolve the company under investigation.
Use filtered company search when needed, then add context only to the selected subject.
Complete a known contact during review.
Request the missing field while keeping CRM updates and outreach behind separate controls.
Add company context to a submitted record.
Use returned fields as inputs to the customer’s own routing or scoring logic.
Offer an enrichment action inside automation.
Let users place a one-record REST or MCP step in a broader controlled flow.
Frequently asked questions
What to know before you build.
A strong product integration keeps identity, field scope, no-match behavior and downstream actions visible and testable.
Free plan
Prototype the complete product experience—including no match.
Test real user tasks across representative records before deciding which fields, interface and controls belong in production.