AI agents & MCP
Verify-before-send for AI agents — API + MCP
Autonomous agents that enrich leads, draft outreach, or write to a CRM need a deterministic email check before they act. Verifly exposes the same pay-as-you-go verify API over REST and MCP (https://verifly.email/mcp) so agents can self-register, inspect credits, and gate every send on deliverable results.
curl -X GET "https://verifly.email/api/v1/verify?email={{email}}" \
-H "Authorization: Bearer vf_your_api_key"Real-time SMTP mailbox checks
Single, batch, and async bulk verification
Disposable, role account, and catch-all detection
Pay-as-you-go credits with no subscription lock-in
Search fit
Built for AI agent email verification
Use Verifly when you need a simple API, predictable pricing, and clean JSON results before emails hit your product, CRM, or campaign tool.
Where Verifly sits in an agent loop
A safe outbound agent loop: collect or enrich email → Verifly verify (MCP tool or HTTP) → if deliverable, draft/send or write CRM; else log and skip or escalate. Without that gate, agents happily spam undeliverable guesses and burn domain reputation overnight.
Connect MCP at https://verifly.email/mcp with your vf_ key (or follow self-register flows documented for agents). REST remains available for any framework that prefers raw HTTP. Credits are prepaid and never expire — ideal for bursty agent workloads.
MCP + self-register + verify-before-send
Point your MCP-capable client at https://verifly.email/mcp. Tools typically cover single verify, batch verify, and credit balance. Agents that can create accounts should store the returned API key securely and call verify before any send or CRM write. Prefer batch when cleaning lists; prefer single when gating one lead at a time.
- Obtain a vf_ API key (dashboard signup or agent self-register path).
- Add Verifly MCP (https://verifly.email/mcp) or call REST with Bearer auth.
- In the agent graph: verify → branch on result before send/CRM.
- Monitor credits; buy a pack when trial volume is proven.
curl -X POST "https://verifly.email/api/v1/verify/batch" \
-H "Authorization: Bearer vf_your_api_key" \
-H "Content-Type: application/json" \
-d '{"emails":["alex@acme.com","a.smith@acme.com","asmith@acme.io"]}'Why agent builders prefer pay-as-you-go
Agent workloads spike when a cron or user triggers a crawl. Monthly verifier seats waste money between spikes. Verifly packs sit idle at zero cost until the agent runs again.
Questions about MCP or agent onboarding: hello@veriflyemail.com — only Verifly contact route.
FAQ
Frequently asked questions
Where is the Verifly MCP server?
https://verifly.email/mcp — connect with your vf_ API key from any MCP-compatible client.
Can agents create their own API keys?
Self-register / signup flows exist for automation-friendly onboarding. Store keys as secrets; never embed them in public prompts or repos.
Should every agent send call verify first?
Yes for cold or enriched addresses. Skip only when the address was verified recently and stored with a trusted timestamp in your own system.
How do I handle risky / catch-all in agents?
Default to skip on fresh domains. Allowlist risky only when a human policy or warmed domain says so. Surface the flag in your tool response so the planner can decide.
Does this work with LangChain / CrewAI / custom graphs?
Any stack that can HTTP GET/POST with a Bearer header works. MCP is optional convenience; REST is the source of truth.
Who do I contact for agent / MCP support?
Email hello@veriflyemail.com — partnerships and support only go through that address.
Ready to wire this?
Start free with 100 credits, mint a vf_ API key, and paste the recipe above. Buy a pack only when you need more — credits never expire.