Schema.org Audit API
POST /api/schema/audit $0.02 per call
USDC on Base · x402
Audit schema.org structured data (JSON-LD) for Google rich-result readiness. POST a URL or raw JSON-LD; returns detected types, missing required/recommended fields, honest rich-result status (flags deprecated types like FAQ/HowTo), and fix suggestions. Covers Product, Review, Article, Recipe, VideoObject, LocalBusiness. Current to 2026 Google guidance.
Parameters
| Name | In | Description | |
|---|---|---|---|
url | body | Public URL to fetch and audit its JSON-LD | |
jsonld | body | Raw JSON-LD object to audit directly (alternative to url) |
Example request
curl -X POST "https://api.webbersites.com/api/schema/audit" \
-H "Content-Type: application/json" \
-d '{"url":"https://example.com/product-page"}'
# first call returns 402 + payment requirements; an x402 client pays and retries automaticallyExample response
{
"found": 1,
"audited": 1,
"with_issues": 1,
"detected": [
{
"detected_type": "VideoObject",
"audited_as": "VideoObject",
"rich_result_status": "active",
"required_missing": [
"thumbnailUrl"
],
"recommended_missing": [
"duration",
"hasPart"
],
"notes": [
"Use interactionStatistic for view counts, NOT interactionCount (deprecated)."
]
}
]
}MCP tool: post_schema_audit — via npx -y webbersites-x402-mcp (local, key stays on your machine) or the remote endpoint https://api.webbersites.com/mcp.
How payment works
There is no signup and no API key. Call the endpoint; it replies 402 Payment Required with machine-readable payment requirements. Your client signs a USDC transfer authorization (EIP-3009, gasless) and retries with the X-PAYMENT header — @x402/fetch does this automatically. See the overview for a working snippet.