Multi-Agent Hiring Pipelines: Who Calls Lookup, Who Calls Outreach
Multi-agent hiring pipelines: who calls lookup, who calls outreach – keep find tools separate from sequencers so empties stay empty and credits stay honest.
Multi-agent hiring stacks fail when one agent does everything: scrape, invent, email, and dial. Healthy pipelines separate who calls lookup from who calls outreach. Lookup returns contacts when the soft mesh has them. Outreach tools message only after a found contact. Empties stay empty.
Invenitor is Connecting people; a lookup API, not a sales cloud. Soft mesh coverage varies; we do not publish hit-rate percentages. MCP hub: MCP for Recruiting Agents. Copilot build: Building a Recruiting Copilot. Claude/Cursor: Claude / Cursor Agents. Docs twin: Agent-Readable Docs. Primer: What Is an MCP Server for Hiring Product Teams?. Start: /mcp.md.
Role split that keeps honesty
| Agent role | Calls | Must not |
|---|---|---|
| Sourcer / shortlist | Collects profile URLs | Invent emails |
| Lookup tool (MCP/REST) | Returns email/phone when found | Guess fills |
| Outreach / sequencer | Messages found contacts | Treat empty as found |
| Analyst | Counts found vs empty vs error | Optimize fake hit rates |
Layer clarity: Contact Lookup API vs CRM vs Sequencer. Honesty: Empty Means Not Found. Primary: One Primary Contact, Never Invented. Marketing language: When We Have Them.
Why one mega-agent is dangerous
A single agent with scrape + invent + send privileges will optimize for "completed" rows. That burns brand trust and can burn credits if billing is per-call instead of found-only. Demand Credit B style contracts – Credits, Empty Results, and Timeouts, What Is Pay-Per-Lookup Pricing?, What Are API Credits.
Shared credit pool, separate tools
Lookup agents and human desks should share one prepaid pool and one empty semantics – /pricing, 25 to 1,000 Credits. Keys: Rate Limits and Keys. OpenAPI: OpenAPI Hygiene. REST: /docs, REST Enrichment Inside a Hiring Product.
Pipeline sketch
- Sourcer agent writes URLs to a queue.
- Lookup agent calls MCP/REST find.
- Empty rows skip outreach; found rows enter sequencer with consent/process rules your company sets.
- Analyst logs found/empty/error – never invents.
WhatsApp desks: WhatsApp-First Recruiters. Night batch: Night-Shift Freelance Recruiters. Partner share: Partner Bench Sharing. Error codes: Error Codes Buyers Should Expect.
Eval set before you ship
Ten known-found URLs, ten likely-empty, two invalid. Pass only if empties stay empty and credits match found outcomes. Trust: Trust Checklist. Hub: LinkedIn or GitHub Profile URL → Contact Lookup API.
What should you do next?
Draw your agent graph. Put lookup behind /mcp.md. Forbid invent-on-empty in prompts. Sample five free finds via /docs. Size credits on /pricing.
Procurement one-liner
We run multi-agent hiring with a dedicated lookup tool – soft mesh, empty means not found, outreach only after found contacts, shared found-only credits.
Prompt fragments that forbid invention
If lookup returns empty, do not guess email or phone. Do not call outreach tools. Log empty and stop. Honesty: Empty Means Not Found. Billing: Credits, Empty Results, and Timeouts. Primer: What Are API Credits. Pay-per-lookup: What Is Pay-Per-Lookup Pricing?. Trust: Trust Checklist. Marketing: When We Have Them. Errors: Error Codes Buyers Should Expect. Hub: LinkedIn or GitHub Profile URL → Contact Lookup API. MCP family: MCP for Recruiting Agents, What Is an MCP Server for Hiring Product Teams?, Claude / Cursor Agents, Agent-Readable Docs, Building a Recruiting Copilot. Layer: Contact Lookup API vs CRM vs Sequencer. WhatsApp: WhatsApp-First Recruiters. Keys: Rate Limits and Keys. OpenAPI: OpenAPI Hygiene. Packs: 25 to 1,000 Credits. Desks: Partner Bench Sharing, Night-Shift Freelance Recruiters. Definition: What Is a Hiring Contact API?. /docs · /mcp.md · /pricing.
Observability
Dashboard tiles: found, empty, error, credits spent. Fail the build if invented fills appear in fixtures.
Questions
Who should call the lookup API in a multi-agent stack?
A dedicated lookup tool/agent via REST or MCP – not the outreach agent inventing fills.
Can outreach agents call lookup directly?
Prefer a clear boundary. If they call lookup, they must leave empties empty and never invent.
How do credits work across agents?
Share one prepaid pool with found-only rules so humans and agents reconcile the same ledger.
What belongs in /mcp.md?
Tool names, empty semantics, auth, and links to docs/pricing – see agent-readable docs.
How do we evaluate honesty?
Known-found and likely-empty fixtures; fail on invented phones/emails.
Where do builders start?
/mcp.md, /docs, building a recruiting copilot, and rate limits and keys.
Is this a sequencer product?
No. Invenitor is a lookup API – Connecting people – not a sales cloud or dialer.
More in this cluster
Building a Recruiting Copilot That Looks Up Contacts via MCP
Building a recruiting copilot that looks up contacts via MCP – wire Claude/Cursor agents to profile-URL find or burning seats.
Read
Agent-Readable Docs: Why MCP.md Matters for Contact APIs
Agent-readable docs: why MCP.md matters for contact APIs – typed tools for Claude/Cursor agents, same Credit B as REST.
Read
Claude / Cursor Agents: Calling a Contact Lookup MCP Endpoint
Claude and Cursor agents calling a contact lookup MCP endpoint: tool calls instead of scrapers – same credits as REST.
Read