Navigation Extractor API

Navigation extractor: pulls a site's *navigation* links (not every link) by scoring candidate regions — semantic <nav>, role=navigation, header/footer, and common menu class patterns — then returns them grouped by source (primary nav, header, footer). For agents mapping site structure or planning which pages to fetch. Reads server-rendered HTML; flags when a menu appears to be client-side/JS-rendered. ?url=

Parameters

Example request

curl "https://api.webbersites.com/api/seo/nav?url=https%3A%2F%2Fexample.com"
# first call returns 402 + payment requirements; an x402 client pays and retries automatically

Example response

{
    "nav_regions_found": 3,
    "primary_nav": {
        "source": "nav (main-menu)",
        "count": 5,
        "links": [
            {
                "text": "Products",
                "href": "https://example.com/products",
                "internal": true
            }
        ]
    },
    "unique_nav_links": 12
}

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.