Extract metadata (title, author, OG tags, word count) from any URL via a single GET call, paid per-request with x402.
What it does
The Content Metadata endpoint at content.hugen.tokyo extracts structured metadata from any web page given its URL. It returns fields such as title, author, publication date, Open Graph tags, canonical URL, language, word count, and estimated reading time. The endpoint is part of a broader Content Intelligence API that also offers link extraction, full content extraction, AI-powered summarization, and content analysis — each as a separate paid endpoint.
This specific endpoint (`/content/metadata`) accepts a GET request with a required `url` query parameter (max 4096 characters). Payment is handled via the x402 protocol at $0.01 USDC per call on the Base network. The API describes itself as using a "dual-engine extraction" system that handles JavaScript-rendered pages. No API key or scraping library setup is required for direct x402 usage, though alternative access methods exist including an MCP gateway, API keys with free trial credit, and a Python SDK (`x402-pay`).
The endpoint is live and returns a 402 payment challenge with a sample response showing the expected output structure. Response schemas in the OpenAPI spec are empty (untyped), so the exact field set is inferred from the sample response in the x402 challenge. Documentation is available at the `/docs` path as a standard Swagger/OpenAPI UI.
Capabilities
Use cases
- —Extracting Open Graph tags and metadata for link previews in chat or social apps
- —Gathering structured article metadata (author, date, word count) for content aggregation pipelines
- —Enriching bookmarks or saved links with title, language, and reading time estimates
- —Automated content cataloging for research or archival workflows
- —Agent-driven web research where structured page info is needed before full extraction
Fit
Best for
- —Agents needing quick structured metadata from arbitrary URLs without running a scraper
- —Applications that need OG tags, canonical URLs, and reading time in a single call
- —x402-native workflows where per-call micropayments are preferred over subscriptions
Not for
- —Full page content extraction (use the /content/extract endpoint instead)
- —Bulk scraping thousands of pages at low cost — per-call pricing adds up
- —Offline or non-URL content analysis
Quick start
# Using the x402-pay Python SDK
pip install x402-pay
import x402_pay
result = x402_pay.get(
'https://content.hugen.tokyo/content/metadata?url=https://example.com'
)
print(result.json())Example
Response
{
"date": "2025-01-15",
"title": "Example Article Title",
"author": "John Smith",
"og_tags": {
"image": "https://example.com/img.jpg",
"title": "Example Article",
"description": "A sample article"
},
"language": "en",
"word_count": 1250,
"canonical_url": "https://example.com/article",
"reading_time_minutes": 5
}Endpoint
Quality
The endpoint is live (402 challenge captured) with a clear OpenAPI spec and sample response. However, the response schema in the OpenAPI spec is empty/untyped — the output structure is only inferred from the sample in the x402 challenge. No dedicated documentation page or pricing page exists beyond the Swagger UI.
Warnings
- —Response schema is untyped in the OpenAPI spec; field set inferred from x402 challenge sample only
- —No dedicated pricing or documentation pages found (404 on /pricing, /README, /api)
- —Root URL returns 404; docs only available at /docs
Citations
- —The API describes itself as: Extract, summarize, and analyze web content in one call. Dual-engine extraction handles JS-rendered pages.https://content.hugen.tokyo/docs
- —The /content/metadata endpoint requires a url query parameter with max length 4096https://content.hugen.tokyo/docs
- —Payment is $0.01 USDC on Base per call via x402https://content.hugen.tokyo/content/metadata
- —Alternative access via MCP gateway, API keys, or x402-pay Python SDKhttps://content.hugen.tokyo/content/metadata