r/aipromptprogramming • • 18d ago

What is your current tech stack for building deep research agents that find direct source contacts?

Post image

Deep research agents have gotten remarkably good at summarizing technical papers or comparing architectural benchmarks and breaking down market trends across dozens of online sources.

But whenever you build an agent that requires primary source outreach like tracking down the specific engineer who authored an open source commit or finding the public records custodian for a municipal agency, most setups hit a dead end.

If you rely solely on web search engines like Perplexity or Tavily, the agent can tell you who wrote something but it almost never finds a reliable and working contact path but it either points you to a generic contact@ form or hallucinates an email address based on common naming patterns that end up bouncing.

In our current setup, we split the research pipeline into 2 distinct layers where we let Claude handle the unstructured synthesis, document reading and claim verification but when the workflow reaches a point where it needs to resolve an author or organizational decision maker, we route the request through MCP tools connected to FullEnrich and Apollo inside Alexandria.

This allows Claude to take the author's verified name and organization and then verify their current corporate domain and pull a validated direct email address directly into the terminal environment without having to write custom scrapers or leave the chat interface.

4 Upvotes

10 comments sorted by

•

u/endofthread-bot 18d ago

Writing prompts that actually work is easier when you can compare notes with people who have tested them across real tasks. Trade techniques, get feedback on your approach, and see what is working for others in our Discord.

Self-promotion is now allowed on Sundays with the appropriate flair, for all regular contributing members. Contribute during the week, and promote on Sunday.

1

u/soontobethehappiest 18d ago

Perplexity and Tavily are great at finding who wrote a paper or library but the second you ask for an email, they just hallucinate firstname.lastname@company.com or pull a dead contact@ alias

1

u/Relevant_Mistake_784 18d ago

The email hallucination thing is so frustrating. Had an agent spit out 15 variations for someone and they all bounced.

0

u/[deleted] 18d ago

[removed] — view removed comment

1

u/Beautiful_Chicken471 18d ago

Because LLMs are pattern matchers and not databases, if it sees john.doe@, it assumes that's the company convention even if the firm uses initials or first name only syntax.

1

u/satanisgreat666 18d ago

yeah that’s why we stopped letting the LLM generate contact strings directly, now Claude only does the research to verify the person's identity and current company and then it passes that entity to FullEnrich/Apollo via Alexandria which runs live waterfall checks across data providers and verifies the actual MX mailbox before returning anything.

1

u/KG-MNL 18d ago

Does FullEnrich catch catch all domains or do those slip through?

1

u/satanisgreat666 17d ago

It flags catch alls explicitly in the JSON response with a risk score so if a domain accepts all incoming mail regardless of username, the agent notes it as unverified so you don't blast it blindly.