Home · Tools · enrich_person

enrich_personFill the gaps in a partial profile.

Often the agent already has something — an X handle, an email, half a name — and just needs the rest filled in from public sources before it can act. enrich_person takes a partial record and returns the enriched record with each new field cited to its source. Three credits. About three seconds. Use it as the second step after find_contact when you need more than handles.

Slug
enrich_person
Cost
3 credits
Latency
~3s
Rate limit
60/min

When to call this tool

Enrichment is the move whenever the agent needs more attributes than handles. Job title and seniority. Recent topics they post about. Their company's most recent funding round. Their current role start-date. The tool always cites; the agent gets to defend each enriched field downstream by linking to the source. It will also tell you when it cannot fill a field rather than guessing — that honesty is the difference between an agent that closes deals and one that gets caught hallucinating.

Compared to a typical static enrichment vendor, this tool is live: every call hits the open web fresh, so a job change from yesterday is visible today. The trade-off is latency — about three seconds per record. Bulk enrichment of 1,000+ rows should be queued and parallelised carefully against the rate limit.

Input schema

{
  "partial_profile": {
    "name": "…", "x_handle": "…", "email": "…", "company": "…"
  },
  "fields": ["role", "seniority", "topics", "company_funding"]
}

Output schema

{
  "enriched": {
    "name": { "value": "…", "source": "…" },
    "role": { "value": "…", "source": "…", "asof": "…" }
  },
  "unfilled": ["…"],
  "credits_used": 3
}

Example invocations

1. Claude Desktop

Enrich this partial: { name: "Maya P", x_handle: "@mayap" }
with role, seniority, recent topics.

2. ChatGPT custom GPT

For any "fill in the rest" request, call enrich_person.
Always show the source URL alongside each enriched field.

3. Cursor MCP

Loop enrich_person over leads.csv. Skip rows already
having "role" filled. Output enriched.csv.

4. n8n

{ "jsonrpc": "2.0", "method": "tools/call",
  "params": { "name": "enrich_person",
    "arguments": { "partial_profile": { "x_handle": "@dhh" }, "fields": ["role", "topics"] } } }

5. Raw curl

curl -X POST https://www.mentionfox.com/mcp \
  -H "Authorization: Bearer $FOXAPIS_KEY" \
  -d '{"jsonrpc":"2.0","method":"tools/call","params":{"name":"enrich_person","arguments":{"partial_profile":{"name":"Brian Chesky","company":"Airbnb"},"fields":["role","seniority"]}}}'

Sample output

{
  "enriched": {
    "role": { "value": "CEO", "source": "https://news.airbnb.com/about-us/leadership/" },
    "seniority": { "value": "founder/c-suite" }
  },
  "unfilled": [],
  "credits_used": 3
}

Credit cost & rate limits

Flat 3 credits per call regardless of fields requested. 60 per minute. For bulk enrichment over 1,000 records, contact us about a streaming endpoint.

Error codes & recovery

422 NO_ANCHORPartial record had no field strong enough to resolve. Add a name+company pair or a handle.
404 NO_PUBLIC_SIGNALSubject exists but has effectively no public footprint to enrich from.
429 RATE_LIMITEDUse the retry-after header.