ZeroBounce
Validate email addresses in real time or in batch, and check credit balance and API usage, via the ZeroBounce v2 API.
About
ZeroBounce ships in the w6w first-party pack. It declares 4 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.zerobounce- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Email · Marketing
Overview
ZeroBounce validates email addresses in real time — checking a single address synchronously (or several at once, in one batch call) and returning a deliverability status (valid, invalid, catch-all, unknown, spamtrap, abuse, do_not_mail) plus trust signals like domain age, MX records, free/disposable/role-based detection, and best-effort name/gender/geolocation hints.
Beyond validation, this app covers account visibility: current credit balance and a date-ranged usage report broken down by result status, so a workflow can check headroom before a bulk run.
A fit for gating a signup flow on a real-looking address, cleaning a list before a send, or filtering risky addresses (spam traps, disposables, role-based mailboxes) out of a marketing list before they cost deliverability.
ZeroBounce’s Email Finder, Domain Search, A.I. Scoring, Activity Data and List Evaluator products, and the CSV-file bulk-upload flow (Send File / File Status / Get File / Delete File on a separate bulkapi.zerobounce.net host), are deliberately out of scope for this app — see the README.
Build with ZeroBounce
Three routes to the same 4 actions. The Workflow tab is generated from ZeroBounce's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Validate Email
validate-email Check a single email address's deliverability and identify risky addresses.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying ZeroBounce's real ids.
{
"manifestVersion": "2",
"name": "zerobounce-example",
"steps": [
{
"id": "get-api-usage",
"uses": {
"app": "io.w6w.zerobounce",
"action": "get-api-usage",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"startDate": "<startDate>",
"endDate": "<endDate>"
}
}
]
}Here are some of the things you can do
-
Get API Usage
readget-api-usage -
Get Credits
readget-credits -
Validate Email Batch
performvalidate-batch -
Validate Email
readvalidate-email
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for ZeroBounce, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to ZeroBounce. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "get-api-usage",
payload: {
startDate: "<value>",
endDate: "<value>",
// region: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action get-api-usage --payload '{"startDate":"<value>","endDate":"<value>"}'Give an AI agent ZeroBounce — without giving it ZeroBounce's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.zerobounce#get-api-usage",
"input": {
"startDate": "<startDate>",
"endDate": "<endDate>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's ZeroBounce connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
ZeroBounce's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. ZeroBounce itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
ZeroBounce declares its own checks, so its health is a property of the app rather than something the host guesses at.
ZeroBounce platform status
Atlassian Statuspage rollup for status.zerobounce.net, scoped to the API/API-US/API-EU components matching this app's three regional hosts. Unauthenticated and unsigned.
Validation credit balance
Remaining validation credits, read from GET /v2/getcredits.