x402basequality 0.72

Search Hashnode technical blog posts via x402 micropayment — returns titles, reactions, reading time, and tags.

Price
per_call
Protocol
x402
Verified
no

What it does

The `/scout/hashnode` endpoint is part of the Scout Multi-source Intelligence API hosted at scout.hugen.tokyo. It searches Hashnode's technical blogging platform via their GraphQL API and returns structured results including post title, brief description, reaction counts, reading time, and tags. The endpoint accepts a required query string parameter `q` and an optional `per_page` parameter (1–20, default 10).

Payment is handled via the x402 protocol using USDC on Base. The per-call cost is $0.005 (half a cent) for this individual source endpoint. The endpoint returned a valid 402 challenge with a sample Hashnode result during probing, confirming it is live. A broker option is also available at discovery.hugen.tokyo for callers who prefer API-key-based access without wallet integration, as well as an MCP transport at mcp.hugen.tokyo.

This endpoint is one of 19+ source-specific search endpoints offered by Scout. Other individual sources include Hacker News, GitHub, npm, PyPI, Stack Overflow, arXiv, Semantic Scholar, Dev.to, Lobsters, GitLab, X/Twitter, Product Hunt, and more. Scout also offers aggregated report endpoints (`/scout/report` for 14 free sources, `/scout/report/full` for all 18) and AI-synthesized research endpoints (`/scout/research`, `/scout/research/deep`) at higher price points.

Capabilities

hashnode-searchblog-post-searchtechnical-content-discoveryx402-micropaymentusdc-base-settlementquery-parameter-filteringreading-time-metadatareaction-count

Use cases

  • Finding technical blog posts on a specific framework or library across Hashnode
  • Monitoring community-written content and tutorials about a technology topic
  • Gathering developer sentiment and educational content for market research
  • Enriching an AI agent's knowledge base with curated technical articles
  • Comparing community coverage of competing tools or approaches

Fit

Best for

  • AI agents needing structured access to Hashnode blog content
  • Developers building multi-source technical content aggregators
  • Research workflows that need reaction counts and reading time as quality signals

Not for

  • Full-text retrieval of entire Hashnode blog posts (returns metadata/briefs only)
  • Non-technical or general-purpose blog search outside Hashnode's ecosystem
  • High-volume bulk scraping — designed for per-query micropayment model

Quick start

curl -i "https://scout.hugen.tokyo/scout/hashnode?q=react&per_page=5"
# Returns 402 with x402 payment challenge.
# Pay with x402 SDK:
# pip install x402-pay
# import x402_pay; r = x402_pay.get('https://scout.hugen.tokyo/scout/hashnode?q=react&per_page=5')

Example

Request

{
  "url": "https://scout.hugen.tokyo/scout/hashnode?q=react&per_page=5",
  "method": "GET"
}

Response

{
  "count": 1,
  "query": "react",
  "source": "hashnode",
  "results": [
    {
      "title": "React Server Components Deep Dive",
      "reactions": 180,
      "reading_time": 12
    }
  ]
}

Endpoint

Transporthttp
Protocolx402
Pay to0x29322Ea7EcB34aA6164cb2ddeB9CE650902E4f60
CurrencyUSD COIN

Quality

0.72/ 1.00

Full OpenAPI schema with parameter definitions and a live 402 challenge with sample response data. However, the response schema is not formally defined (only a sample result in the challenge), and no dedicated docs page exists. Pricing is clearly stated.

Warnings

  • No formal response schema in OpenAPI — response structure inferred from 402 challenge sample only
  • No dedicated documentation page found (/docs, /api, /README all return 404)
  • Sample response in challenge shows only 1 result with limited fields; full field set is not documented

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-22 01:24:57Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-21
Last seen2026-04-22

Agent access