MillionVerifier
Verify email addresses in real time, verify whole lists in bulk and check your credits with MillionVerifier.
About
MillionVerifier ships in the w6w first-party pack. It declares 8 actions, 3 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.millionverifier- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Email · Marketing
Overview
MillionVerifier is an email verification service: it checks whether an address will actually be delivered before you send to it, so bad addresses never reach a list or a campaign.
A workflow can verify one address in real time (result and result code, quality, the detailed subresult, free-provider and role-account flags, a did-you-mean correction and the credits left), or upload a list for bulk verification, poll the file until it is finished, download the results filtered to the statuses you want, stop a file that is still running and delete it afterwards. The account’s remaining and renewing credits are readable for free.
The connection holds a MillionVerifier API key (app.millionverifier.com/api). The vendor sends it as a query parameter, which the connection adds to each request for you; the single API (api.millionverifier.com) and the bulk API (bulkapi.millionverifier.com) name that parameter differently and both are handled. Verification and bulk files spend credits; the vendor’s test key API_KEY_FOR_TEST returns random results at no cost.
Build with MillionVerifier
Three routes to the same 8 actions. The Workflow tab is generated from MillionVerifier'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.
Delete Bulk File
bulk-delete Delete an uploaded bulk file and its results. Download anything needed first.
Download Bulk Results
bulk-download Download the verification report of a bulk file, optionally filtered by result. The report is returned as text in `content`.
List Bulk Files
bulk-list-files List uploaded bulk files, optionally filtered. Pages by offset; `nextOffset` is set while more files remain.
Stop Bulk File
bulk-stop Cancel a bulk file that is in progress. Results for the addresses already verified can be downloaded shortly after.
Upload Bulk File
bulk-upload Upload a list of emails (or your own file) for bulk verification. Returns the file record; poll it with Get Bulk File until it is finished. Spends a credit per unique address.
Verify Email
verify-email Verify one email address in real time. Spends one credit. Returns the result (ok, catch_all, unknown, error, disposable, invalid), quality, subresult, free/role flags, a did-you-mean correction and the credits left.
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 MillionVerifier's real ids.
{
"manifestVersion": "2",
"name": "millionverifier-example",
"steps": [
{
"id": "bulk-download",
"uses": {
"app": "io.w6w.millionverifier",
"action": "bulk-download",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"fileId": "<fileId>",
"filter": "<filter>"
}
}
]
}Here are some of the things you can do
-
Download Bulk Results
readbulk-download -
Get Bulk File
readbulk-get-file -
List Bulk Files
searchbulk-list-files -
Stop Bulk File
performbulk-stop -
Upload Bulk File
performbulk-upload
+3 more actions available
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 MillionVerifier, 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 MillionVerifier. 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: "bulk-download",
payload: {
fileId: "<value>",
filter: "<value>",
// statuses: "<value>",
// free: "<value>",
// role: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action bulk-download --payload '{"fileId":"<value>","filter":"<value>"}'Give an AI agent MillionVerifier — without giving it MillionVerifier'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.millionverifier#bulk-download",
"input": {
"fileId": "<fileId>",
"filter": "<filter>"
}
}
}
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 MillionVerifier 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
MillionVerifier'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. MillionVerifier itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
MillionVerifier declares its own checks, so its health is a property of the app rather than something the host guesses at.
MillionVerifier platform status
API reachable
Unauthenticated GET /api/v3/credits. MillionVerifier's JSON error body (`No apikey specified`) passes: it proves the application is answering.
Credit headroom
Remaining credits from GET /api/v3/credits; down at zero.