passlisted in Coinbase#3 by calls of 5 on this host
0.01 USDC
per call, as the listing declares it on eip155:
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- 100% / 100% / 100%
- Calls, trailing 30 days
- 3
- Unique payers, trailing 30 days
- 2
- Last called
- 2026-09-15 07:24 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.01 USDC
- Networks
- 2
How has the volume on this endpoint moved?
content.hugen.tokyo serves content metadata, a GET endpoint that TOLL places in scraping, listed in the Coinbase registry.
A call to content metadata costs 0.01 USDC on Base, as declared.
content metadata takes the query parameter url.
Across Base and Solana it declares 2 ways to pay, to 2 different wallets.
content metadata returns json; the example shows date, title, author, og_tags, language, word_count and 2 others.
content metadata answered the sweep of 2026-09-15 with a valid 402, as at every sweep since 2026-09-11.
content metadata is one of 5 listed endpoints on content.hugen.tokyo, tied 3rd by calls with 1 other among them.
content metadata takes 18% of the calls counted across content.hugen.tokyo.
Over 30 days: 3 calls, 2 payers.
content metadata was last called on the day of the snapshot.
Closest in price to content metadata within scraping: firecrawl scrape at vaaya.ai and extract at schemasure.com.
Among comparable prices in scraping, content metadata sits above 30% of them.
Across scraping, 612 endpoints carry counters and content metadata out-counts 59% of them.
Its payee wallet receives for 69 listed endpoints across 12 hosts.
The seller's tags on content metadata are web, extract, summary and ai, and its label is "content-extraction".
The price of content metadata is declared by 192 other listings in scraping too.
the payment options, as of 2026-09-15 16:57 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.01 USDC | exact | 0x29322E…2E4f60 |
| Coinbase | solana: | USDC | 0.01 USDC | exact | 4du4Afkj…boaS5Z |
the checks, as of 2026-09-15 03:54 UTC · method · pinnableendpoint answered HTTP 402
No named check failed.
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-09-15 03:54 UTC | pass | 0 | daily-2026-09-15 |
| 2026-09-14 03:53 UTC | pass | 0 | daily-2026-09-14 |
| 2026-09-13 03:53 UTC | pass | 0 | daily-2026-09-13 |
| 2026-09-12 06:08 UTC | pass | 0 | daily-2026-09-12 |
| 2026-09-11 09:32 UTC | pass | 0 | daily-2026-09-11 |
Presence in a registry, not liveness of the service (method). Newest first.
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-09-15 07:24 UTC · method · live
The input and output block
{
"input": {
"type": "http",
"method": "GET",
"queryParams": {
"url": "https://example.com/article"
}
},
"output": {
"type": "json",
"example": {
"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
}
}
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-09-15 16:57 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "content metadata on content.hugen.tokyo", snapshot of 2026-09-15 16:57 UTC. https://tollindex.com/e/content-hugen-tokyo-content-metadata-0953f1/at/2026-09-15T16-57Z. Accessed [access date].
BibTeX
@misc{toll-e-content-hugen-tokyo-content-metadata-0953f1-2026-09-15T16-57Z,
author = {TOLL},
title = {content metadata on content.hugen.tokyo},
howpublished = {\url{https://tollindex.com/e/content-hugen-tokyo-content-metadata-0953f1/at/2026-09-15T16-57Z}},
year = {2026},
month = {9},
note = {Pinned view of the snapshot of 2026-09-15 16:57 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.