Outbound lead generation when the agent builds the list

Most outbound stacks are two products glued together: something that finds contacts and something that checks whether those addresses still work. The glue is a spreadsheet, and the spreadsheet is where the money leaks. When an agent is doing the prospecting, that leak gets wider, because nothing in a CSV tells the agent which rows have gone stale.

TAPAC removes the second step by folding it into the first: POST /v1/contacts/search returns people and the SMTP verdict for each address in the same response.

The pipeline, in three calls

# 1. build + verify in one request
curl -X POST https://tapacapi.com/v1/contacts/search \
  -H "Authorization: Bearer $TAPAC_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"industry":"b2b saas","job_titles":["head of growth","vp sales"],
       "company_size":"11-200","location":"germany","source":"website","limit":25}'

# 2. re-check addresses you already own
curl -X POST https://tapacapi.com/v1/contacts/verify \
  -H "Authorization: Bearer $TAPAC_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"emails":["a@example.com","b@example.com"]}'

Every returned contact carries name, title, company, the source it was found in (website, telegram, discord) and its verification status. Nothing is stored between calls, so there is no decaying list to maintain.

Why "verify later" costs more than it saves

For a human, a bounce report is a feedback signal. For an agent, it is invisible: the tool returned 200, so the agent moves on. Making verification part of the search response is the only version an autonomous loop can act on.

Where the contacts come from

Public web pages, Telegram and Discord communities — the places people actually announce what they do. Community-sourced leads convert about 30% better than cold outreach (McKinsey, 2025), and personalised openers get 3.2x higher open rates (HubSpot, 2025). None of that helps if half the addresses are dead, which is why the verification is in the same call rather than bolted on.

What it costs, and what it does not do

Pay-per-use: 100 free searches, then $0.10–0.50 per verified contact. No seat licence, so adding agents to the loop costs nothing extra. There is no CRM, no sequence engine and no inbox here — TAPAC answers one question: who should we contact, and is that mailbox real right now.

Use it from an agent

npx -y @tapacapi/mcp

or point an MCP-capable client at the hosted endpoint https://tapacapi.com/mcp with an Authorization: Bearer <key> header. Two tools: tapac_find_contacts and tapac_status. A JS client is on npm as @tapacapi/sdk.

Where to go next

← Back to TAPAC