passlisted in Coinbase#1 by calls of 2 on this host
0.05 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
- 3
- Last called
- 2026-08-23 23:11 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.05 USDC
- Networks
- 1
How has the volume on this endpoint moved?
At tenjin.blog, read takes GET requests, is listed in the Coinbase registry, and falls under inference by TOLL's rules.
read is priced at 0.05 USDC on Base.
Its declared inputs are the path parameters slug and handle.
read returns json; the example shows id, url, slug, tags, price, title and 2 others.
read answered the sweep of 2026-09-15 with a valid 402, as at every sweep since 2026-09-11.
Of tenjin.blog's 2 listings, read ranks 1st by calls.
60% of the host's counted calls go to it.
The registry's counters give read 3 calls and 3 unique payers over 30 days, every call from a different payer.
The last call to read came 23 days before the snapshot, 2026-08-23.
Closest in price to read within inference: check site at x402.cloudpulsepoint.com and github repo analyze at api.strale.io.
read is priced above 71% of comparable listings in inference.
Within inference, 76% of endpoints with counters have fewer calls.
The payee wallet of read appears on no other listing.
The seller's own tags are text, articles, analysis and markdown.
The price of read is declared by 100 other listings in inference too.
the payment options, as of 2026-09-15 21:20 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.05 USDC | exact | 0x7A0Fb3…6ddC0B |
the checks, as of 2026-09-15 06:45 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 06:45 UTC | pass | 0 | daily-2026-09-15 |
| 2026-09-14 06:13 UTC | pass | 0 | daily-2026-09-14 |
| 2026-09-13 06:04 UTC | pass | 0 | daily-2026-09-13 |
| 2026-09-12 08:22 UTC | pass | 0 | daily-2026-09-12 |
| 2026-09-11 13:46 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-08-23 23:11 UTC · method · live
The input and output block
{
"input": {
"type": "http",
"method": "GET",
"pathParams": {
"slug": "x402-batch-settlement-how-the-protocol-s-payment-channel-voucher-scheme-actually",
"handle": "athoughts"
},
"queryParams": {}
},
"output": {
"type": "json",
"example": {
"id": "019f5e1d-3c0e-7b8d-824f-785faafd7bea",
"url": "https://tenjin.blog/a/athoughts/x402-batch-settlement-how-the-protocol-s-payment-channel-voucher-scheme-actually",
"slug": "x402-batch-settlement-how-the-protocol-s-payment-channel-voucher-scheme-actually",
"tags": [
"x402",
"protocol",
"batch-settlement",
"payment-channels",
"metering"
],
"price": "100000",
"title": "x402 batch settlement: how the protocol's payment-channel/voucher scheme actually works",
"creator": {
"handle": "athoughts",
"displayName": "athoughts"
},
"excerpt": "A from-the-spec explainer of x402's batch-settlement scheme (a stateless unidirectional payment channel with cumulative signed vouchers) for anyone building a metered or streaming x402 service and deciding between exact and batch. Cadence knobs, the escrow deposit flow, and the facilitator-support gotcha. As-of 2026-07-13.",
"publishedAt": "2026-07-14T00:53:22.064Z"
}
}
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-09-15 21:20 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "read on tenjin.blog", snapshot of 2026-09-15 21:20 UTC. https://tollindex.com/e/tenjin-blog-api-read-handle-slug-de0843/at/2026-09-15T21-20Z. Accessed [access date].
BibTeX
@misc{toll-e-tenjin-blog-api-read-handle-slug-de0843-2026-09-15T21-20Z,
author = {TOLL},
title = {read on tenjin.blog},
howpublished = {\url{https://tollindex.com/e/tenjin-blog-api-read-handle-slug-de0843/at/2026-09-15T21-20Z}},
year = {2026},
month = {9},
note = {Pinned view of the snapshot of 2026-09-15 21:20 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.