Metadata Extraction API
GET /api/seo/metadata $0.01 per call
USDC on Base · x402
Raw metadata extractor: the complete, unopinionated head inventory of a page — title, charset, lang, canonical, all meta tags grouped by family (OpenGraph, Twitter, Dublin Core, named, http-equiv, itemprop), every link relation, and JSON-LD returned as parsed objects. For agents doing their own processing (head-check audits the same data; this just dumps it). ?url=
Parameters
| Name | In | Description | |
|---|---|---|---|
url | query | required | Public URL to extract metadata from |
Example request
curl "https://api.webbersites.com/api/seo/metadata?url=https%3A%2F%2Fexample.com"
# first call returns 402 + payment requirements; an x402 client pays and retries automaticallyExample response
{
"title": "Example",
"charset": "utf-8",
"lang": "en",
"counts": {
"meta_tags": 18,
"og": 5,
"twitter": 4,
"links": 9,
"jsonld_blocks": 1
},
"opengraph": {
"title": "Example",
"image": "https://example.com/og.png"
},
"links": {
"canonical": [
"https://example.com/"
],
"icon": [
{
"href": "/favicon.ico",
"sizes": "32x32"
}
]
},
"jsonld": [
{
"@type": "Organization"
}
]
}MCP tool: get_seo_metadata — 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.