AI-powered web content summarization via x402 micropayment — $0.02 per call.
What it does
The Content Summary endpoint at content.hugen.tokyo extracts and summarizes web page content using AI, returning structured results including a summary, key points, and named entities. It is part of a broader Content Intelligence API that also offers metadata extraction, link extraction, full content extraction, and content analysis — all behind x402 micropayment gates.
This specific endpoint (`/content/summary`) accepts a URL as a query parameter and returns an AI-generated summary of the page's content. It uses a dual-engine extraction system that handles JavaScript-rendered pages, so you don't need your own scraping infrastructure or LLM setup. The response includes a prose summary, a list of key points, and extracted entities with their types (e.g., organization, product). An optional `strip_query` parameter lets you remove query parameters from the target URL before processing.
Payment is handled via the x402 protocol on Base using USDC at $0.02 per request. Alternative access methods include an MCP gateway (mcp.hugen.tokyo), a free API key with $0.05 credit via the discovery service, or the `x402-pay` Python SDK for one-line access without a wallet. The API exposes a full OpenAPI 3.1 spec and Swagger docs at `/docs`.
Capabilities
Use cases
- —Summarize articles or blog posts for an AI agent's context window
- —Build a news aggregation pipeline that stores structured summaries
- —Generate key-point digests of competitor pages for research workflows
- —Extract named entities from arbitrary web pages without running your own NLP
- —Provide quick page previews in a chatbot or search assistant
Fit
Best for
- —AI agents that need concise web page summaries on demand
- —Developers who want structured summarization without hosting an LLM
- —Automated research pipelines that process many URLs
- —Applications needing entity extraction alongside summaries
Not for
- —Bulk scraping of thousands of pages (per-call pricing adds up)
- —Offline or air-gapped environments with no internet access
- —Use cases requiring full raw HTML or DOM access (use /content/extract instead)
Quick start
# Using the x402-pay Python SDK (no wallet needed)
pip install x402-pay
import x402_pay
resp = x402_pay.get(
'https://content.hugen.tokyo/content/summary?url=https://example.com'
)
print(resp.json())Example
Response
{
"summary": "The article discusses recent advances in AI technology...",
"entities": [
{
"name": "OpenAI",
"type": "org"
},
{
"name": "GPT-4",
"type": "product"
}
],
"key_points": [
"AI models are getting smaller and faster",
"Edge deployment is now practical"
]
}Endpoint
Quality
The endpoint is live (402 challenge captured), has an OpenAPI 3.1 spec, and includes a sample response in the challenge payload. However, the response schema is not formally defined in the OpenAPI spec (empty schema objects), and there are no dedicated docs pages beyond the auto-generated Swagger UI. Pricing is clear at $0.02 USDC on Base.
Warnings
- —Response schema is not formally defined in the OpenAPI spec — the 200 response schema is empty.
- —Root URL returns 404; no dedicated landing page or documentation site beyond /docs.
- —Sample response in the x402 challenge may be illustrative rather than from a real extraction.
Citations
- —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
- —Payment required is $0.02 USDC on Base per callhttps://content.hugen.tokyo/content/summary
- —Alternative access via MCP gateway at mcp.hugen.tokyo, API key via discovery.hugen.tokyo, or x402-pay Python SDKhttps://content.hugen.tokyo/content/summary
- —OpenAPI 3.1 spec available at /openapi.jsonhttps://content.hugen.tokyo/docs