Receive a sign-up code or magic link and use it
Two or three companies' docs show a full fit.
What counts as done
The code or link is returned as a field by one blocking or pushed call, with no public URL needed, and the inbox is not one the target site blocks as disposable.
Measured, for our own tests: the code or link is returned within 60 seconds of arrival. No docs we read state these figures, so they don't count against a listing here.
How agents ask for it: sign up for this service and confirm the email
, get the 2FA code from the email
, wait for the verification link
, test our sign-up flow end to end
Does the job 2
The docs show it meets the test above, and nothing we read says otherwise.
| Listing | Why |
|---|---|
| mails.ai Agent Email D Mails.ai | received.wait blocks until a matching email arrives (filtered by sender and has: code) and every received message lists its codes and links as fields; the documented example waits 50 seconds, inside the 60-second bar. source |
| MailSlurp B Pettman OÜ | WaitForLatestEmail blocks for a set timeout (examples use 60 seconds) and getEmailCodes returns the codes as fields; a26 found the long-poll waiting minutes. The 2024 early timeout (a25) is closed, and the July 2026 NXDOMAIN outage (a24) is resolved. source |
Does the job, with a limit 9
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| AgentMail API + MCP BB AgentMail, Inc. | WebSocket events push new mail with no public URL, but there is no blocking wait call and no code or link fields, so the agent parses extracted_text itself; mail arrives on agentmail.to unless a custom domain is set. source |
| Cherami C Abderrahmane Gourragui (sole operator, Quebec) | No blocking wait call and no code or link fields; the guide tells the agent to poll on a schedule with a page budget or use a webhook, which needs a public URL. Addresses are on the shared cherami.to domain only. source |
| Hostinger Agentic Mail C Hostinger International Limited | It is an ordinary mailbox on the owner's domain, so sites don't see a disposable domain, but there is no wait call or code field, and push is webhook-only, needing a public URL. source |
| Inbound C EXON ENTERPRISE LLC | Addresses sit on the owner's own domain, and the email.received webhook carries parsed text and attachment URLs, but there is no wait call or code field, and push needs a public webhook URL. source |
| InboxAPI D Sitka Capital Pty Ltd | Reading and search tools return incoming mail, but there is no wait call, push or code field, so the agent polls get_email_count, and addresses are subdomains of inboxapi.ai rather than a custom domain. source |
| Lumbox B Cyphen Innovations Private Limited | GET /inboxes/{id}/otp blocks up to 120 seconds and returns code, all_codes and links as fields, with 408 on timeout, meeting the 60-second bar. On Free the address is on Lumbox's shared domain, whose standing on disposable lists wasn't checked; custom domains start at Starter. source |
| Mailows C DW Technology LLC | Mail can land on the owner's own domain, but there is no wait call or code field, the webhook needs a public URL, and reading a message marks it read with no undo. source |
| Postfleet E Postfleet | Schema extraction can pull a code into fields when the comprehension quota allows (100 a month on Free), but there is no wait call or push other than a webhook, which needs a public URL. source |
| Robotomail B Tiny Bot Labs Limited | SSE events arrive as mail lands, with no public URL needed, but there is no blocking wait call or code field, and Free discards mail from anyone but the owner, so a sign-up code never arrives below Solo. source |
What stops agents finishing
- shared or disposable domain refused by the target site
- wait call times out before a slow email arrives
- webhook-only delivery with no public endpoint
Around it
Before: browser.multi-step-form, agent-inboxes.fleet-provisioning. After: browser.signed-in-task, secrets.store-credential.
Where this comes from
Weight 22 of 100 in Agent inbox APIs: 8 of 31 accounts: 2FA and sign-up codes (a02, a03, a13, a30), e2e tests of email paths (a06, a25, a26) and create-then-use timing (a20)
The same as data: /api/v1/use-cases/agent-inboxes.verification-code.json, or the MCP tool get_use_case with id agent-inboxes.verification-code. Other jobs in this category: /api/v1/niches?category=agent-inboxes.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.