Skip to main content
Use Emailable through Corsair: one client, typed API calls, local DB sync. Create a secret API key under API in Emailable. It is sent as a Bearer token, so it never appears in a URL or request body. A test key (starts with test_) returns sample results and spends no credits; with it, addresses such as deliverable@example.com, risky@example.com or disposable@example.com return that result. verifications.verify uses one credit per address. When Emailable needs more time it answers HTTP 249; the plugin then returns pending: true, and calling again within 5 minutes costs nothing extra. batches.create verifies up to 50,000 addresses for one credit each and is marked destructive; poll batches.get until done is true. Only credits, a verification’s state, score and reason (keyed by address), and batch ids are stored. Names Emailable guesses from an address are returned but not stored. Verified addresses are kept out of events and are removed from propagated errors. What you get:
  • 4 typed API operations
  • 3 synced entities (accounts, batches, verifications) for fast .search() / .list()

Setup

1

Install

2

Add the plugin

corsair.ts
With multiTenancy: true, scope calls with corsair.withTenant(id). See Quick start for KEK + Hub keys, and Multi-tenancy for account isolation.
3

Choose authentication

4

Connect a tenant

Mint a connect link and send the tenant to it. Hub hosts the page and delivers the result to your app — see Connect / OAuth.

Example API calls

Verify one address
Verify a list of addresses
See the full list on the API page.

Query synced data

Synced entities support tenant.emailable.db.<entity>.search() and .list(): accounts, batches, verifications. See Database for filters and operators.

What’s next

API reference

Every emailable.api.* operation with input and output types.

Database

Synced entities, search filters, and operators.

Connect / OAuth

createLink, Hub delivery, and tenant connect flows.

Use with agents

Expose this plugin’s operations as MCP tools.