X (Twitter) profile qualifier and enricher
Hand any X username to this agent and get back a qualified, ICP-scored lead with a verified email and a resolved LinkedIn profile.
The outcomes on their scorecard
X profile, X recent posts, LinkedIn profile, and verified email — all behind a single agntdata credential. The agent stitches them into one ranked lead.
Email finder + mandatory verifier on every result means your downstream sequencer only ever sees deliverable addresses. `risky` is surfaced with the flag flipped; `undeliverable` is discarded silently.
Hard disqualify gates fire before any LLM scoring or enrichment. A no-link, no-bio profile costs one X API call and zero enrichment credits — the rubric never sees it.
Every lead leaves with a 0–100 `lead_score`, an `icp_match` label, and (for high-fit ones) a 3–4 sentence personalized notes block your SDRs can paste into the opener.
How the work gets done
Give the agent any X username — from a chat message, a webhook payload, or another agent's tool call — and it returns a single structured JSON result: ICP score with breakdown, hard-disqualify reason if any, the prospect's LinkedIn profile when resolvable, and a verified contact email when findable. Use it as a one-shot lookup tool, wire it into a form-fill webhook, or pair it with the X engager scraper to drain a leads table on autopilot.
This agent is the qualification + enrichment function in your stack. Hand it a handle, get a structured lead. Pair it with a scraping blueprint upstream and a CRM webhook downstream when you want the full pipeline; call it ad-hoc the rest of the time.
Your new teammate
Lead Qualifier & Enricher
Agent that takes an X username as input, fetches the profile, applies hard disqualify rules, scores against my ICP rubric, and (only for high-fit leads) resolves a LinkedIn profile and finds + verifies a contact email. Returns a single structured JSON result.
What it runs on
This hire is assembled from the public toolkit. Every piece below is a tool your own agents can call too.
How setup works
- 01
Claim the hire
One click. No questionnaire. The brief is already written from your business, and you can edit it before you build if you want to.
- 02
Your hire deploys itself
Agents, tools, schedules, memory, hand-off queues and the database schema are provisioned into your workspace automatically, then the first real run fires while you watch.
- 03
Hand it the keys it still needs
You land in chat with your hire and its findings. 1 setup tasks — connecting your outreach tools, picking where it reports — are done conversationally, whenever you want.
Other hires that pair well
LinkedIn profile qualifier and enricher
Hand any LinkedIn profile URL to this agent and get back a qualified, ICP-scored lead with a verified email and a website summary attached.
LinkedIn Hiring Lead Enricher — emails verified + buying committee inferred
Takes the partial hiring contacts a scraper produces and turns them into a sequenceable pipeline: verified emails for every lead, plus inferred buying committees for the hiring companies where LinkedIn returned no hiring team. Hourly cron. Pair upstream with a hiring-signal scraper, downstream with a sequencer.
Email Finder Waterfall — verified email from any combination of identifiers
Give it a name + a domain (or a LinkedIn URL, or any combo of identifiers) — it returns a verified professional email or a structured failure. Three-step waterfall: agntdata orchestrator → Exa deep search → verifier. Stateless primitive, called by other agents.
Every hire is assembled from the same toolkit.
Same data sources, same database, same memory, schedules and queues. Point your own agent at the MCP endpoint and wire it your way instead.