AI Economics Tools
AI
Token cost, LLM energy, agent-hour and Proof-Adjusted Autonomy calculators by Michał Piszczek
This API validates email addresses through format checks, MX record lookup, SMTP probing, and catch-all detection. It is designed for AI agents to efficiently assess and filter out invalid email addresses before further processing, without the need for a user dashboard. The service is accessible via a straightforward JSON response, suitable for automated workflows.
Verified today: 100% uptime
API key
Unconfirmed
HTTPS
Supported
Browser calls
Yes, CORS enabled
Status
Live · 90/100
Email Verification API provides programmatic access to this api validates email addresses through format checks, mx record lookup, smtp probing, and catch-all detection. it is designed for ai agents to efficiently assess and filter out invalid email addresses before further processing, without the need for a user dashboard. the service is accessible via a straightforward json response, suitable for automated workflows. Delivered over secure HTTPS protocols, it exposes structured endpoints designed to integrate cleanly into modern frontend frameworks, backend microservices, and automated data pipelines without requiring local database provisioning.
Engineers building web dashboards, mobile applications, CLI utilities, or background cron workers in need of reliable ai data feeds.
Consuming Email Verification API removes the operational overhead of running custom scrapers, orchestrating headless browser fleets, or manually seeding and maintaining a local database. Instead of reverse-engineering volatile DOM layouts or dealing with anti-bot IP blocks, your application connects directly to a standardized JSON interface that supports client-side browser execution out of the box. Dedicated authentication ensures rate quotas and credential tracking per project environment.
Last checked 2026-10-24. Measured independently, not self-reported by the provider.
Practical real-world patterns for integrating Email Verification API into software systems.
Augment user submissions or catalog items with metadata, tagging, summaries, or vector analysis.
Power real-time conversational flows, prompt engineering experiments, or automated customer support triage.
Classify incoming customer feedback, support tickets, or error logs to detect customer sentiment trends.
Production-ready starting templates with error handling for Email Verification API.
// Authentication requirement is unconfirmed. Check the documentation before relying on this.
// Modern native fetch with error handling
async function callApi() {
try {
const response = await fetch('https://verifymail.nanocorp.app/api/v1/resource', {
method: 'GET',
headers: {
'Authorization': 'Bearer YOUR_TOKEN',
Accept: 'application/json',
},
});
if (!response.ok) {
throw new Error(`HTTP ${response.status}: ${response.statusText}`);
}
const data = await response.json();
console.log('Response payload:', data);
return data;
} catch (error) {
console.error('API request failed:', error);
throw error;
}
}
// callApi();Inspect the expected JSON structure returned by Email Verification API.
Authentic sample payload structure to evaluate schema attributes before integration.
{
"id": "gen-c0gjbv5",
"model": "standard-v1",
"choices": [
{
"index": 0,
"message": {
"role": "assistant",
"content": "Processed output generated successfully from input prompt."
},
"finish_reason": "stop"
}
],
"usage": {
"prompt_tokens": 18,
"completion_tokens": 12,
"total_tokens": 30
}
}Technical factors to keep in mind when integrating Email Verification API into production environments.
Avoid triggering rate limits on public feeds by caching response payloads in Redis, Vercel KV, or standard HTTP Cache-Control headers with a 5-to-15 minute TTL.
While no API key is required, public keyless pools often share global rate limits. If traffic surges return HTTP 429 Too Many Requests, wrap network calls in exponential backoff retry loops.
CORS headers are validated and present on responses. You can safely call this endpoint directly from frontend React, Vue, or static HTML pages without an intermediary proxy server.
Always inspect response.ok before executing response.json(). Upstream services returning 4xx or 502 Bad Gateway often serve HTML error pages, which cause syntax errors when parsed as JSON.
Aggregated from one public source (freepublicapis), then normalised and checked by us.
Report an issue with this listing ↗AI
Token cost, LLM energy, agent-hour and Proof-Adjusted Autonomy calculators by Michał Piszczek
AI
Daily-updated prices, context windows & deprecation/EOL dates for 190+ AI/LLM models, sourced from official provider docs
AI
AI extraction of invoices, receipts, bank statements & contracts into structured JSON/CSV
AI
Generate and edit images with AI, no key or account required
AI
LLM pricing, context windows and deprecation dates, schema-validated and updated daily
AI
AI tool discovery with agentic scoring for 8,600+ tools and MCP servers
Answered from what our own scheduled checks found, not from the provider's marketing.
Email Verification API is listed in our free catalogue, but it requires some form of authentication, so you will need to register before your first call. Providers frequently reserve higher limits and commercial use for paid plans.
Email Verification API requires some form of authentication. Check the provider's documentation for which scheme it expects.
Yes. Email Verification API returned CORS headers when we checked it, so a browser will let your page read the response. You can fetch it directly from client-side JavaScript with no proxy and no backend.
Yes, as of 2026-10-24. Our automated check reached Email Verification API and recorded a 100% reliability score with a median response time of 2675 ms. We re-check on a schedule, and this page updates with the result.
Yes. Email Verification API serves over HTTPS, so you can call it from a secure page without triggering a mixed-content block.