Skip to content
Back to Home

Changelog

What is new in the PricklyMails email verification API. Follow along as we ship.

September 2026

  • Connect an AI agent over OAuth. Create scoped agents and authorize an MCP client, like Claude, to act on your account with only the permissions you grant, over OAuth 2.1 with PKCE. The agent verifies addresses with your own API keys, and you can revoke it at any time.
  • Hosted MCP server. PricklyMails is now a remote Model Context Protocol server at mcp.pricklymails.com. Add it as a connector and your agent gets verification, balance, and usage as tools, no local setup.
  • A full agent toolbox. The MCP server now also covers bulk verification, API-key list and revoke, webhook setup, wallet history, and job listing, so an agent can run a whole verification workflow over its scoped connection, not just one address at a time.
  • SMTP on every plan. The live SMTP mailbox check is now included on every tier, including Free. Catch-all detection becomes the premium check on Pro and above.
  • Built for developers and AI agents. The landing page now positions PricklyMails as a high-speed email verification API for both developers and AI agents, with a new section on using it as an MCP tool so an agent can verify an address before sending.
  • Live numbers on the homepage. The landing stats now show real figures, total verifications and average latency, served from a public cached endpoint, replacing the placeholder tiles.
  • Signup email check. When you register, we run a quick, non-blocking check on your address and show a heads-up if it looks invalid or disposable. It never blocks you from signing up.
  • Cached scores follow the latest model. When we recalibrate scoring, a previously cached result is re-graded under the current model on read, so an older result never shows a stale score.
  • Webhooks on Starter and above. Webhook endpoints are now part of the Starter plan and up. The Free plan shows the webhooks tab with an upgrade prompt.

August 2026

  • Fewer false positives on unreachable servers. When an SMTP check times out, cannot connect, or returns an ambiguous reply, the address is now reported as unknown (we could not confirm it) rather than being optimistically marked valid, and an inconclusive catch-all probe no longer inflates the confidence score.
  • Bulk verification. Drop a CSV or paste a list and verify up to a million addresses in one batch. Everything is parsed in your browser before anything is sent, and you get per-address results as they come in.
  • Sharper deliverability signals. Greylisting (a mail server asking us to try again later) is now detected and retried instead of guessed, and big accept-all providers like Gmail, Outlook, and Yahoo are reported as risky rather than falsely marked valid.
  • Recalibrated quality score. The 0-100 quality score is now graded within each deliverability status, so it never contradicts the verdict.
  • Sandbox test mode. pm_test_ keys now run a deterministic sandbox: no SMTP, no billing, and canned outcomes chosen from the address local part (valid@, invalid@, catchall@, disposable@, role@), so you can build and test an integration without spending credits.
  • Account recovery. Request a fresh confirmation link when the original one expired, and recover from an expired link instead of getting stuck on a dead-end screen.
  • OpenAPI specification. Every endpoint is now described by a generated OpenAPI 3.1 document, served at /api/openapi.json and /api/openapi.yaml, so you can import the whole API into Postman or Insomnia in one step.

July 2026

  • Webhooks. Register an endpoint and receive a signed notification the moment a verification job completes, instead of polling for the result.
  • Single-email verification. Submit an address to /api/verify and get syntax, MX, SMTP, disposable, role, free-provider, catch-all, and typo checks with a deliverability verdict and a quality score.
  • Dashboard. Manage everything from one place: an overview with usage charts, your verification history with a per-check breakdown, API key management, active sessions, and your token wallet.
  • Two-factor authentication and account management. Turn on TOTP two-factor from your profile, review and revoke your active sessions, and delete your own account, each confirmed with your current password.
  • Try it live. A public demo on the landing page runs a real verification (syntax, MX, disposable, and typo checks) with no signup, so you can see a result before creating an account.

June 2026

  • Accounts and authentication. Create an account, confirm your email, sign in, reset a forgotten password, change your email or password, and protect your login with two-factor codes. Every confirmation and notification arrives as a branded transactional email.
  • API keys. Generate live and test keys (pm_live_ and pm_test_), scope each key to the exact checks it may run, and manage them from your dashboard. Each key carries its own plan-driven rate limit.
  • Wallet and token billing. Usage is metered against a token wallet: every verification reserves its cost up front, then commits or refunds it based on which checks actually ran. Checks that never ran are refunded automatically.
  • Subscription plans and Stripe checkout. Pick a plan, check out through Stripe, and manage your subscription from the Stripe billing portal. Buy extra tokens any time with a dynamic per-token top-up.
  • Privacy by design. Verified email addresses are never stored: only salted hashes are kept, so your lists never sit in our database in the clear.

April 2026

  • Early access. The PricklyMails landing page and waitlist went live, so you could reserve your spot while the verification API was still in development.