Integrations & exports for your whole stack
B2B Database Network gets verified contacts into the tools you already run, four ways. Use a CSV preset to export a list mapped to the exact columns Instantly, Smartlead, lemlist, HubSpot, or Salesforce expect. Call the REST API to search and reveal from your own code. Point an AI agent at the MCP server to query the database as a tool. Or subscribe to webhooks so your systems react the instant something changes. Every path runs verification first, honors suppression, and draws from one credit pool that never expires.
Four ways to move your data
Different teams work differently. A solo founder might live in CSV exports, while an agency automates everything through the API, and an AI-native team lets an agent do the searching. All four paths share the same guarantees underneath: verification at export, suppression enforced everywhere, and a credit balance that does not expire.
| Path | Best for | What it does |
|---|---|---|
| CSV presets | Cold-email tools & CRMs | Download a list mapped to your tool's columns |
| REST API | Engineering & automation | Search, reveal, lookup, and enrich from code |
| MCP server | AI agents & assistants | Query the database as a first-class agent tool |
| Webhooks | Event-driven systems | Receive real-time pushes when data changes |
CSV presets that import without a cleanup step
The most common way to get data out is a CSV, and the most common way that goes wrong is column names. Every tool wants its fields named a certain way, and a mismatched header means a broken import or a contact with the email in the wrong column. Presets fix that. Choose your tool, and the export is mapped to that tool's exact field names, ready to import as-is.
Each preset maps our fields to the destination's expected columns. Here is what each one is tuned for.
| Preset | Type | How it maps |
|---|---|---|
| Instantly | Cold email | First/last name, email, company, plus custom variables for personalization |
| Smartlead | Cold email | Lead fields and campaign-ready custom columns for sequences |
| lemlist | Cold email | Contact fields plus the variables lemlist uses in dynamic snippets |
| HubSpot | CRM | Contact and company properties aligned to HubSpot's import schema |
| Salesforce | CRM | Lead/Contact object fields ready for the data import wizard |
| Raw CSV | Anything else | All available fields, unmapped, for custom workflows |
Before any list leaves the platform, every address is checked and you see the full verdict mix. You are charged only for valid contacts, invalids are refunded, and suppressed records are never in the file. We also document which cold-email platforms permit imported lists, so you can keep your sending compliant rather than guessing.
A note on the cold-email tools: some platforms restrict importing third-party lists. We flag where that applies so you stay on the right side of their terms.
REST API for search, reveal, and enrichment
Generate an API key the moment you sign up — no sales call and no waiting list. The REST API mirrors the app, so anything you can do by clicking, you can do in code. Search with the same filters, reveal contacts, look up a single record, enrich an existing row, and check your usage. Responses come back as predictable JSON with typed errors and clear rate-limit headers, so building against it is straightforward.
- Search — the same faceted filtering as the app, returning counts and masked previews before you spend anything.
- Reveal — spend a credit to unlock a verified email or phone for a contact; re-revealing one you already own is free.
- Lookup & enrich — resolve a single record or fill gaps in a row you already have.
- Usage — read your remaining credit balance and recent activity programmatically.
API keys are stored as a one-way hash and can be revoked instantly, and API spend draws from the same never-expiring credit balance as the app. There is no separate API invoice to reconcile at the end of the month.
Read the API documentation →MCP server for AI agents
For AI-native workflows, the Model Context Protocol (MCP) server lets assistants and agents query the database as a first-class tool. Instead of writing glue code, you point a compatible assistant — Claude, for example — at the MCP server, and it can search, reveal, and verify contacts on your behalf. This is how an AI SDR or an enrichment agent plugs into real contact data without a custom integration.
The server exposes the same operations as the app and the API, as named tools an agent can call directly.
| MCP tool | What the agent can do |
|---|---|
search_leads | Filter the database by title, company, industry, seniority, and geo |
reveal_contact | Spend a credit to unlock a verified email or phone number |
verify_email | Check an address and return its verdict and freshness |
The same rules apply to an agent as to a human: suppressed records never appear, invalids are refunded, and every reveal draws from your shared credit balance. An agent cannot reach a suppressed contact any more than you can.
Webhooks for real-time events
Polling for changes is wasteful. Webhooks flip the model: you register a URL, and we push an event to it the moment something happens. Your systems stay in sync without a scheduled job checking for updates that may not have arrived yet. Each delivery is signed so you can confirm it came from us, and you acknowledge receipt with a 2xx response.
A sample of the events you can subscribe to.
| Event | When it fires |
|---|---|
export.completed | A list export finishes and the file is ready |
credit.refunded | A credit is returned because an email verified as invalid |
contact.reverified | A re-check changes a contact's email status |
suppression.added | A record you own is suppressed after an opt-out |
Webhooks pair naturally with the API. Kick off work through the REST API, then let a webhook tell your system when it is done or when a contact's status changes, so you only act on data that is current.
A typical end-to-end workflow
Here is how the pieces fit together for a team running automated outreach. Each step uses one of the integrations above, and the whole loop runs without anyone exporting a spreadsheet by hand.
- An agent or a scheduled job calls
search_leads(MCP) or the search API to build a targeted list by persona and territory. - It reveals the contacts it needs with
reveal_contact, spending credits only on the ones it keeps. - Verification runs at reveal/export, so invalids are refunded and only deliverable addresses move forward.
- The verified list is exported with the Instantly or Smartlead preset, or pushed straight into HubSpot or Salesforce.
- A
contact.reverifiedwebhook later flags anyone whose status changes, so your sequences stay clean over time.
Frequently asked questions
Which tools do the CSV presets support?
Presets map your export to the exact column names expected by Instantly, Smartlead, lemlist, HubSpot, and Salesforce, plus a raw CSV option for everything else. Pick the preset for your tool and the file imports cleanly without a manual column-mapping step.
Do exports respect verification and suppression?
Always. Every export runs verification first, so you see the full verdict mix and are charged only for valid contacts — invalids are refunded. Suppressed and opted-out records are never included in any export, preset or raw, and exports honor your plan's daily caps.
Can AI agents query the database directly?
Yes. The Model Context Protocol (MCP) server exposes the database as first-class tools — search_leads, reveal_contact, and verify_email — so assistants and agents like Claude can search, reveal, and verify without a human in the loop. API spend draws from the same never-expiring credit pool as the app.
How do webhooks work?
Webhooks push events to a URL you control so your systems react in real time — for example when an export finishes, a credit is refunded for an invalid email, or a re-verification changes a contact's status. You verify each delivery with a signing secret and respond with a 2xx to acknowledge receipt.
Do API and exports use the same credits?
Yes. Whether you click Export in the app, call the REST API, or drive the MCP server from an agent, every reveal draws from one shared credit balance that rolls over and never expires. There is no separate API billing to reconcile.