Question 1

Does email validation verify that a mailbox exists?

Accepted Answer

No. GET /validate-email?email=hello@example.com checks address syntax and matches the domain against a built-in list of known disposable email services. It does not send email, contact an SMTP server, check MX records, or guarantee deliverability. A syntactically invalid address is returned as a successful HTTP 200 result with validSyntax=false. An omitted or empty email parameter returns HTTP 400.

Question 2

Which SEO fields are extracted and what are the limits?

Accepted Answer

GET /extract-seo?url=https%3A%2F%2Fexample.com reads the HTML returned by a public HTTP or HTTPS page and returns its title, meta description, og:title and og:image. Missing fields are null; relative image URLs are resolved against the final page URL. JavaScript is not executed. The request has an 8-second timeout, follows at most 3 redirects and scans at most 256 KiB of HTML, so tags beyond that limit may be absent. URLs containing credentials, custom ports, IP literals, local hostnames or the service itself are rejected.

Question 3

Are SEO results cached, and how do I request fresh metadata?

Accepted Answer

Eligible successful SEO results may be reused for up to 5 minutes; target cache policies, response age, redirects and cache availability can shorten or prevent reuse. Set fresh=true to bypass both cache reads and writes. It does not invalidate or refresh an existing cache entry. Omit fresh or use fresh=false to allow caching. Only exact true and false are accepted; invalid values or duplicate fresh parameters return HTTP 400 (INVALID_PARAMETER). X-SEO-Cache reports HIT, MISS or BYPASS; X-SEO-Cache-Age is the whole-second age for HIT and 0 otherwise. Errors, no-store/private/no-cache responses, responses setting cookies or declaring Vary: *, and recognized sensitive URL parameters are not cached. Do not submit secrets or private URLs. Client responses remain Cache-Control: no-store. Authentication and marketplace request quotas still apply to cache hits. Reading stops early when the complete non-empty title and all three supported meta values are available; otherwise the normal 256 KiB and 8-second limits apply. Performance depends on the target site, network and cache availability; no fixed speed-up is guaranteed.

Question 4

Can AI agents call this API through MCP?

Accepted Answer

Yes. Connect an HTTP-compatible MCP client to https://mcp.jojapi.com/email-and-seo-metadata-extraction-api and configure Authorization: Bearer YOUR_JOJ_API_KEY as a connection header. Select a plan before executing calls. The documented endpoints become tools for email syntax validation and page metadata extraction, using the same subscription and quotas as HTTP requests. Use the MCP server and OpenAPI spec links on the listing for current schemas. Email validation does not verify deliverability; SEO extraction does not render JavaScript.

Email Validation and SEO Metadata Extraction

Frequently Asked Questions