Two new sub-cent x402 endpoints shipped to the URL-metadata-api catalog. Both verified end-to-end against stripe.com, github.com, and wikipedia.org with the X-PAYMENT bypass.
What's new
/api/page-classifier ($0.0005)
Combines URL path patterns, title keywords, JSON-LD @type, Open Graph type, microdata itemscope types, body structure, and form-action signals to classify a page into one of 22 categories with confidence + secondary + A-F grade.
Returns:
-
primary_category— best-matching type (article / product / docs / landing / pricing / login / signup / about / blog_index / category / forum / search / video / podcast / job_listing / repo / wiki / changelog / error / ...) -
confidence(0-100) -
grade(A-F) -
secondary_categories— ranked alternates -
signals— per-source evidence (URL hints, title hints, JSON-LD types, OG type, microdata, form hints, structure) -
summary— one-line human-readable verdict
Use case: AI agents that need to decide rendering strategy, content type, or pricing context for a URL without parsing the full HTML themselves. Complements /api/jsonld (full schema.org block extraction) and /api/og (raw OG tags).
curl "https://epson-rpm-america-satisfy.trycloudflare.com/api/page-classifier?url=https://en.wikipedia.org/wiki/Web_crawler" \
-H "X-PAYMENT: 0.0005 USDC"
Live result on en.wikipedia.org/wiki/Web_crawler:
{
"primary_category": "article",
"confidence": 49,
"grade": "C",
"secondary_categories": [{"category": "wiki", "score": 25}, {"category": "website", "score": 18}],
"signals": {
"url_hints": [{"category": "wiki", "pattern": "/wiki/"}],
"title_hints": [{"category": "wiki", "hits": ["wiki"]}],
"jsonld_types": ["Article"],
"structure": {"approx_word_count": 4106, "heading_count": 14, "paragraph_count": 62}
}
}
/api/email-auth-rollup ($0.001)
Composite email-auth deliverability score for a domain: SPF + DKIM + DMARC + MTA-STS + BIMI rolled up into a single 0-100 score with A-F grade + a post_feb_2024_compliant boolean that matches Gmail/Yahoo bulk-sender requirements (SPF + DKIM + DMARC with p=quarantine or stricter).
Returns:
-
overall_score(0-100 composite) -
grade(A-F) -
post_feb_2024_compliant(bool) -
components— per-protocol status with key findings -
findings— top issues sorted by severity
Use case: AI agents auditing a sender domain get the whole deliverability picture in one call instead of 5 round-trips. Critical for any bulk-email sender checking Gmail/Yahoo compliance post-Feb-2024.
curl "https://epson-rpm-america-satisfy.trycloudflare.com/api/email-auth-rollup?domain=github.com" \
-H "X-PAYMENT: 0.001 USDC"
Live result on github.com:
{
"domain": "github.com",
"overall_score": 71,
"grade": "B",
"post_feb_2024_compliant": true,
"components": {
"spf": {"status": "present", "policy": "soft-fail", "record_preview": "v=spf1 ip4:192.30.252.0/22 ..."},
"dkim": {"status": "present", "selectors_found": ["google", "selector1"], "count": 2},
"dmarc": {"status": "present", "policy": "reject", "pct": 100},
"mta-sts": {"status": "missing"}
},
"findings": [{"severity": "info", "msg": "SPF soft-fail (~all) — accepted but stricter -all recommended"}]
}
Catalog
Both endpoints join a 44-route x402 catalog now. Full list:
-
/.well-known/x402— 45 endpoints (43 paid + 1 free + meta) -
/openapi.json— 45 paths -
/llms.txt— for AI-agent context loading -
/— human-readable HTML with one line per route
All routes accept x402 USDC payments on Base (eip155:8453), payTo 0xCa0a6c6Aa7A8F0D5893636CF166Ea2b44fb6500c.
How to call
Both routes return HTTP 402 with the x402 envelope (scheme=exact, asset=USDC 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913, network eip155:8453). To actually call them, an AI agent signs a payment payload and sends it as the X-PAYMENT header. For testing, send any value.
Why these two
page-classifier is the missing piece between "I have a URL" and "I know what kind of content to expect." AI agents scraping the web hit dozens of pages a minute and waste tokens figuring out structure. This route returns the answer in ~5KB of JSON.
email-auth-rollup is a consolidation play — we already had 5 individual endpoints (SPF via /api/dns TXT, DKIM via /api/dkim, DMARC via /api/dns, MTA-STS via HTTPS fetch, BIMI via /api/dns). Bundling them into one call with a composite score + post-Feb-2024 compliance boolean saves 5 round-trips per domain audit and makes the deliverability verdict machine-readable.
Both are now live, registered on 402index.io, and indexed in this article. Try them.
Top comments (0)