Yes — Codex can verify email addresses and turn the clean ones into a campaign in WarmySender, all in plain language, through the same 78-tool connection Claude, ChatGPT, Cursor, Codex, OpenClaw, and Hermes Agent share. You ask in the Codex terminal. It never sends a message itself and can never raise a limit: it writes the campaign and hands it to WarmySender’s scheduler, which paces every email, LinkedIn, Instagram and WhatsApp action inside safe limits no matter who is driving. Connecting and disconnecting accounts stays in the app.
Codex is OpenAI’s coding agent and runs in your terminal, so you talk to it in the shell you already use for the rest of your pipeline. It connects with one add command and one login command; the login opens a WarmySender sign-in in your browser, so there is no key to paste. Verification is where a terminal agent earns its keep: Codex can read a list from a file, submit the batch, wait for it, and turn the safe addresses into a prospect list in one run. It spends the same allowance you have in the app, at the same pace.
Every "can" below stands on a real tool in the WarmySender connection. Every "cannot" is not a setting — there is simply nothing an agent can call that does it.
| Can / cannot | What that means for email verification |
|---|---|
| Can | Check a single address on the spot — safe to send to, risky, or not deliverable. |
| Can | Submit a whole list and follow the results as they come in. |
| Can | Check how much of your allowance is left before committing a big list. |
| Can | Stop a batch that is still running. |
| Can | Turn the confirmed addresses into a prospect list, ready to enroll. |
| Can | Build and start the campaign around the clean list in the same conversation. |
| Cannot | Send to anyone — building the campaign only hands it to WarmySender’s scheduler. |
| Cannot | Verify faster than the app or raise your allowance — it shares the same monthly allowance and pacing. |
| Cannot | Buy credits — anything touching billing stays with you in the app. |
| Cannot | Find an address you do not have — verification confirms addresses, it does not discover them. |
| Cannot | Connect or disconnect a mailbox. |
OpenAI's coding agent registers WarmySender with one command and signs in through your browser — no key to paste.
Run both lines in your terminal; the second opens your browser to sign in to WarmySender.
codex mcp add warmysender --url https://warmysender.com/mcp
codex mcp login warmysenderPrefer a key? Create one under Settings › API Keys and choose exactly which permissions it carries, including read-only. With a key, the Codex route is: Run both lines, adding the export to your shell profile so it sticks.
Both routes reach the same workspace and stay inside the same safe limits. Every agent's steps live on the AI Agents hub.
How much verification allowance do I have left this month?
Verify this list of 800 addresses and tell me when it is done.
Make a list of the addresses that came back safe to send, then build a campaign around them.
Stop the batch I started an hour ago.
Verify every address in list.csv, wait until the batch is done, and print the counts by result.
Codex never sends a message itself and can never raise a limit. Creating or launching a campaign only writes it and hands it to WarmySender's scheduler, which paces every email, LinkedIn, Instagram and WhatsApp action inside safe limits and a gradual ramp — the same protections that apply when a human clicks the buttons. Connecting and disconnecting accounts stays in the app. Account safety always wins.
Yes. Connect Codex to WarmySender and ask in plain language, in the Codex terminal — it can verify email addresses and turn the clean ones into a campaign. It never sends a message itself and can never raise a limit: it writes the campaign and hands it to WarmySender’s scheduler, which paces every email, LinkedIn, Instagram and WhatsApp action inside safe limits no matter who is driving. Connecting and disconnecting accounts stays in the app.
OpenAI's coding agent registers WarmySender with one command and signs in through your browser — no key to paste. Run both lines in your terminal; the second opens your browser to sign in to WarmySender. The command text is: codex mcp add warmysender --url https://warmysender.com/mcp codex mcp login warmysender — the server address is https://warmysender.com/mcp. The steps are on this page under "Connect Codex", and the full install hub for every agent is at /ai-agents.
No. Nothing an agent can call moves a limit — not your monthly verification allowance or the pace at which a batch is checked. Codex can read where you are against a limit and tell you when a pause lifts; WarmySender’s scheduler decides what actually goes out.
No. Connecting and disconnecting accounts stays in the app on purpose — a credential should never pass through an agent or a chat log. Connect the mailbox once in WarmySender; after that Codex can use it.
Exactly as in the app: the agent shares the same monthly allowance and credits and cannot verify any faster. You are only charged for answers — one credit per confirmed result, nothing for one that cannot be confirmed either way — and credits never expire.
No. The add command registers the server address https://warmysender.com/mcp and the login command opens a browser sign-in — nothing to paste or store. Prefer a key anyway? Create one under Settings › API Keys and use the key form on the AI Agents hub.
No. Codex only writes the campaign or the setting; once it has handed that to WarmySender, the scheduler paces every verification on its own whether or not Codex is running.
Yes. Each client registers the server and signs in on its own; they reach the same workspace and the same safe limits, and the scheduler paces every verification exactly the same whichever agent wrote the campaign.
Last updated: 2026-09-09