Contact usTry for free

Plain-language definitions

The B2B enrichment terms worth defining clearly.

Use consistent language across product, developer and AI-agent workflows. These definitions explain the main product directions and boundaries.

TargetWiseProspecting + enrichment

Paginated company and contact discovery with selective record enrichment through REST API and MCP.

Seven focused operations
REST API + MCP delivery
Evaluation before production

Core terms

Start with the concepts that define the product.

Each term links to the dedicated page where its workflow and limitations are explained in depth.

Method

Normalized enrichment

Turning a supported identifier into available business fields through one TargetWise response contract.

Explore Normalized enrichment
Person

Contact enrichment

Completing supported professional email, business-phone or company context for a known person.

Explore Contact enrichment
Direction

Reverse email lookup

Starting with a business email to resolve available professional identity and company context.

Explore Reverse email lookup
Agents

Data grounding

Connecting an agent task to retrieved external context rather than relying on model memory.

Explore Data grounding
Protocol

MCP

A standard way for an AI host to discover and call an external capability such as enrichment.

Explore MCP

Outcome terms

Returned, partial, unresolved and unavailable are different ideas.

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.

  • Returned
  • Partial
  • Needs review
  • Unavailable

Quality terms

Coverage, correctness, freshness and consistency measure different things.

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.

  • Availability is not accuracy
  • Provider count is not verification
  • Freshness depends on purpose and timing

Delivery terms

REST and MCP are interfaces, not different data products.

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.

  • REST for code-owned orchestration
  • MCP for host-discovered tools
  • No bulk CSV workflow

Terminology check

Use these questions before choosing or implementing a workflow.

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

Clear answers before you continue.

Consistent definitions make product selection and implementation easier.

Need another definition?

Tell us which enrichment term is still unclear.

The glossary should grow from real buyer and developer questions, with links to the relevant canonical product or methodology page.

Suggest a glossary term