@billionvfy

https://xitter.cf/t.co/829Kgxynex | Professional Email Verification. Verify emails in real-time with 99.9% accuracy.

 Delaware
linktr.ee/billionverify
Joined February 2026
  • Tweets80
  • Following220
  • Followers4
1Media
BillionVerify is now in Claude's official connector directory. Search "BillionVerify" in Claude, click Connect, sign in. Then just ask Claude to check your emails. No server URL to paste. No API key. claude.ai/directory/billionv…

BillionVerify - Claude

Verify email addresses before you send, right from Claude.

claude.ai
2
1
2
213
BillionVerify is now in Vercel Connect. Store your API key once. Any Vercel app or agent you link can verify emails at runtime. No key in env vars. How it works: billionverify.com/blog/billi… On Substack: billionverify.substack.com/p… Also in Claude: billionverify.com/blog/billi…
1
1
36
more replies
Shared API Keys: one key, your account, your credits. For your own signup forms, lead jobs and agents. Per-User API Keys: each of your users brings their own BillionVerify key. For products you build for other people.
1
7
Same credits as everywhere else in BillionVerify. Unknown, disposable and badly formatted addresses cost nothing. Catch-all stays catch-all. We don't file it under valid.
7
Workspaces and teams are live in BillionVerify. Give each client, brand or business its own credit balance, plan, invoices and API keys. Invite your team and set how much each team can spend. How it works: billionverify.com/blog/billi…

BillionVerify Workspaces and Teams: How They Work

Workspaces and teams are live in BillionVerify. Give each client or brand its own balance and invoices, invite your team, and set spending limits per team.

billionverify.com
1
1
17
more replies
Who it's for: · Agencies: one workspace per client, separate invoices · SDR teams: reps verify their own lists, no billing access · Several brands: one brand's busy month can't drain another's balance · Developers: one team key per app, capped
1
3
No extra charge for workspaces or teams. A definite result still uses one credit, unknown results are free.
2
In Claude Code, install the plugin. Same server, plus a skill that tells Claude which tool to use and how to report results: /plugin marketplace add BillionVerify/billionverify-claude-plugin /plugin install billionverify@billionverify
1
11
Use cases, prompts you can copy, and how to automate each one: billionverify.com/blog/billi… Connect here: claude.ai/directory/billionv…
2
8
We just shipped four major improvements to BillionVerify. Cleaner bulk verification flows. Richer async progress monitoring. Better backend status semantics. And a complete shift from legacy API-key URLs to modern remote OAuth for MCP. Here is what changed and why it matters:
1
3
158
more replies
MCP Moves to OAuth 1/ We made a significant MCP upgrade in BillionVerify. 2/ Historically, part of the setup story still reflected a legacy pattern: wrapping the MCP endpoint with `curl --stdio` and passing `?api_key=...` in the URL. 3/ That is no longer the right model for a modern remote MCP server. 4/ BillionVerify MCP is now framed the right way: a hosted remote endpoint, OAuth-based access, protected-resource discovery, and client-native authorization flow. 5/ We also cleaned up the entire public surface around it: the `/mcp` landing page, AI guides, Claude Code setup docs, multilingual docs, and FAQ copy. 6/ One important distinction is now much clearer: API keys still belong to the REST API. OAuth now defines the MCP connection model. 7/ This is not just a docs polish pass. It is a product-shape correction that makes BillionVerify easier to connect from modern MCP clients.
1
1
49
Read the full story here: billionverify.com/blog/platf…
1
43
Load more