enrich

Fiber AI Enrich

Reveal work emails, phone numbers, and detailed profiles for companies and individuals.

When to Use

• User wants work emails or phone numbers for a specific person
• User provides a LinkedIn URL and wants contact details
• User wants to enrich a company profile (full details, tech stack, funding, etc.)
• User says "enrich", "reveal", "get email", "get phone", "find contact info", "look up contact"

Do Not Use When

• User wants to search for companies or people they haven't identified yet — use /fiber:search instead
• User wants to enrich more than 5 contacts at once — use /fiber:audience instead
• User wants to write code for enrichment — use /fiber:sdk-ts or /fiber:sdk-py instead

How to Execute

Individual Contact Enrichment — routing policy

Fiber exposes three tiers for single-profile contact reveal. Pick by latency vs cost. All tiers work on standard self-serve API keys — no enterprise gate or demo call required. Every response includes chargeInfo with the exact credits charged so agents can track cost programmatically.

1. Standard (default): syncQuickContactReveal — POST /v1/contact-details/single. Balanced speed and cost. Start here.
2. Premium (fastest, most expensive): syncTurboContactEnrichment — POST /v1/contact-details/turbo/sync. Use when absolute latency matters.
3. Async waterfall (highest coverage): triggerExhaustiveContactEnrichment — POST /v1/contact-details/exhaustive/start. Returns a taskId; poll with pollExhaustiveContactEnrichmentResult (GET /v1/contact-details/exhaustive/poll). Use as a fallback when both sync tiers return nothing.

Via Core MCP:

1. Call get_endpoint_details_full("syncQuickContactReveal") to get the exact parameter schema.
2. Call call_operation("syncQuickContactReveal", {"body": {"apiKey": "...", "linkedinUrl": "...", "enrichmentType": {...}}}).

Via V2 MCP (if available as a generated tool):

• Look for syncQuickContactReveal_tool — it may be available depending on the server's tool generation priority.