Normalized enrichment
Turning a supported identifier into available business fields through one TargetWise response contract.
Explore Normalized enrichmentPlain-language definitions
Use consistent language across product, developer and AI-agent workflows. These definitions explain the main product directions and boundaries.
Paginated company and contact discovery with selective record enrichment through REST API and MCP.
Core terms
Each term links to the dedicated page where its workflow and limitations are explained in depth.
Turning a supported identifier into available business fields through one TargetWise response contract.
Explore Normalized enrichmentCompleting supported professional email, business-phone or company context for a known person.
Explore Contact enrichmentRequesting available company context for a known business.
Explore Company enrichmentStarting with a business email to resolve available professional identity and company context.
Explore Reverse email lookupConnecting an agent task to retrieved external context rather than relying on model memory.
Explore Data groundingA standard way for an AI host to discover and call an external capability such as enrichment.
Explore MCPOutcome terms
Teams commonly separate a returned result from an incomplete result, uncertain identity and unavailable data. Current API and MCP docs list the implemented status names.
Whatever labels are used, uncertainty and absence should stay visible rather than being replaced with a guess.
Quality terms
Coverage asks whether the field was available. Correctness asks whether it describes the intended entity. Freshness asks whether it is current enough for the task.
Consistency asks whether software can handle the response and absence states predictably.
Delivery terms
REST lets application code make requests and control each branch. MCP lets an authorized AI host discover and invoke the capability.
Both use the same enrichment layer and require clear field scope, result handling and application controls.
Terminology check
01Is the starting identifier clear?
02Is the requested output clear?
03Is enrichment separated from validation and prospecting?
04Are uncertain and unavailable outcomes explicit?
05Are provider count and quality claims separated?
06Do production terms match the current contract?
Frequently asked questions
Consistent definitions make product selection and implementation easier.
Need another definition?
The glossary should grow from real buyer and developer questions, with links to the relevant canonical product or methodology page.