Extract all internal and external links from any web page for $0.01 per call via x402.
What it does
The `/content/links` endpoint is part of the Content Intelligence API hosted at content.hugen.tokyo. It accepts a URL as a query parameter and returns a structured JSON response listing all internal and external links found on that page, along with counts for each category. The endpoint uses a dual-engine extraction system capable of handling JavaScript-rendered pages, so it works on modern SPAs and server-rendered sites alike.
This is an x402-gated GET endpoint priced at $0.01 USDC per call on the Base network. No API key or account signup is required — callers pay per request using the x402 payment protocol. Alternative access methods are also available: an MCP gateway at mcp.hugen.tokyo, a free API key with $0.05 credit via discovery.hugen.tokyo, or the `x402-pay` Python SDK for one-line access without a wallet.
The `/content/links` endpoint is one of five paid endpoints in the API suite, which also includes `/content/metadata`, `/content/extract`, `/content/summary`, and `/content/analyze`. The response schema is not formally documented in the OpenAPI spec, but the x402 challenge includes a sample response showing `internal` and `external` arrays of URL strings plus `internal_count` and `external_count` integer fields.
Capabilities
Use cases
- —SEO auditing — enumerate all internal and external links on a page to check for broken links or link structure
- —Competitive analysis — discover what external sites a competitor links to
- —Web crawling — seed a crawler by extracting all links from a starting URL
- —Content verification — check that a page links to expected resources
- —Knowledge graph construction — map relationships between pages via their hyperlinks
Fit
Best for
- —Agents that need structured link data from arbitrary URLs without running a headless browser
- —SEO tools requiring per-page link inventories
- —Automated web crawlers that need a reliable link extraction step
Not for
- —Bulk crawling thousands of pages (per-call pricing adds up quickly)
- —Extracting page content or summaries (use the sibling /content/extract or /content/summary endpoints instead)
Quick start
# Using the x402-pay Python SDK
pip install x402-pay
import x402_pay
response = x402_pay.get(
'https://content.hugen.tokyo/content/links?url=https://example.com'
)
print(response.json())Example
Response
{
"external": [
"https://twitter.com/example",
"https://github.com/example"
],
"internal": [
"https://example.com/about",
"https://example.com/contact"
],
"external_count": 2,
"internal_count": 2
}Endpoint
Quality
The endpoint is live (402 challenge captured) with a clear OpenAPI spec and sample response embedded in the challenge. However, the response schema is not formally defined in the OpenAPI spec (empty schema object), dedicated docs pages return 404, and there are no detailed usage examples or rate limit information.
Warnings
- —Response schema is not formally defined in the OpenAPI spec — the sample response is inferred from the x402 challenge payload
- —No dedicated documentation pages found (pricing, README, API pages all return 404)
- —No rate limit or usage quota information available
Citations
- —The API is described as 'Extract, summarize, and analyze web content in one call. Dual-engine extraction handles JS-rendered pages.'https://content.hugen.tokyo/docs
- —The /content/links endpoint accepts a required 'url' query parameter (string, max 4096 chars)https://content.hugen.tokyo/openapi.json
- —The endpoint is priced at $0.01 USDC on Base per callhttps://content.hugen.tokyo/content/links
- —Alternative access via MCP gateway, API key, or x402-pay SDKhttps://content.hugen.tokyo/content/links
- —Sample response shows internal/external arrays and countshttps://content.hugen.tokyo/content/links