passlisted in Coinbase#2 by calls of 2 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
- 4
- Unique payers, trailing 30 days
- 2
- Last called
- 2026-09-21 21:00 UTC
- First observed by TOLLderived
- 2026-09-19
- Pricederived
- 0.01 USDC
- Networks
- 1
How big is this endpoint among the ones like it?
No trace is drawn of this endpoint’s own volume. Its counters have changed 2 times across 80 observations, and 3 changes are the fewest this site will draw a trace through, because two points and a guess are not a series. Every observation is in the JSON.
read, a GET endpoint on tenjin.sh, appears in the Coinbase registry; TOLL's taxonomy puts it in inference.
A call to read costs 0.01 USDC on Base, as declared.
The request to read is the path parameters slug and handle.
A response from read, as declared, includes id, url, slug, tags, price, title and 2 others.
read answered the sweep of 2026-10-23 with a valid 402, as at every sweep since 2026-09-19.
Of tenjin.sh's 2 listings, read ranks 2nd by calls.
14% of the host's counted calls go to it.
Over 30 days: 4 calls, 2 payers.
read was last called 22 days before the snapshot.
Closest in price to read within inference: chat completions at api.gondola-ai.com and llm at agent402.tools.
read is priced above 14% of comparable listings in inference.
Within inference, 91% 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 6,800 other listings in inference too.
the payment options, as of 2026-10-13 14:08 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.01 USDC | exact | 0x1f64B0…8Af4e5 |
the checks, as of 2026-10-23 11:48 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-10-23 11:48 UTC | pass | 0 | daily-2026-10-23 |
| 2026-10-21 21:17 UTC | pass | 0 | daily-2026-10-21 |
| 2026-10-19 11:32 UTC | pass | 0 | daily-2026-10-19 |
| 2026-10-16 09:19 UTC | pass | 0 | daily-2026-10-16 |
| 2026-10-15 11:18 UTC | pass | 0 | daily-2026-10-15 |
| 2026-10-14 09:07 UTC | pass | 0 | daily-2026-10-14 |
| 2026-10-13 14:00 UTC | pass | 0 | daily-2026-10-13 |
| 2026-10-12 11:24 UTC | pass | 0 | daily-2026-10-12 |
| 2026-10-11 10:05 UTC | pass | 0 | daily-2026-10-11 |
| 2026-10-10 18:16 UTC | pass | 0 | daily-2026-10-10 |
| 2026-10-09 11:35 UTC | pass | 0 | daily-2026-10-09 |
| 2026-10-08 13:13 UTC | pass | 0 | daily-2026-10-08 |
| 2026-10-07 12:28 UTC | pass | 0 | daily-2026-10-07 |
| 2026-10-06 13:09 UTC | pass | 0 | daily-2026-10-06 |
| 2026-10-05 11:36 UTC | pass | 0 | daily-2026-10-05 |
| 2026-10-04 14:16 UTC | pass | 0 | daily-2026-10-04 |
| 2026-10-03 07:36 UTC | pass | 0 | daily-2026-10-03 |
| 2026-10-02 16:44 UTC | pass | 0 | daily-2026-10-02 |
| 2026-10-01 09:26 UTC | pass | 0 | daily-2026-10-01 |
| 2026-09-30 08:55 UTC | pass | 0 | daily-2026-09-30 |
| 2026-09-29 21:00 UTC | pass | 0 | daily-2026-09-29 |
| 2026-09-23 07:55 UTC | pass | 0 | daily-2026-09-23 |
| 2026-09-22 08:08 UTC | pass | 0 | daily-2026-09-22 |
| 2026-09-21 08:30 UTC | pass | 0 | daily-2026-09-21 |
| 2026-09-19 06:29 UTC | pass | 0 | daily-2026-09-19 |
| 2026-09-19 04:37 UTC | pass | 0 | new-after-daily-2026-09-19 |
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-21 21:00 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.sh/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-10-13 14:08 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.sh", snapshot of 2026-10-13 14:08 UTC. https://tollindex.com/e/tenjin-sh-api-read-handle-slug-ce23dc/at/2026-10-13T14-08Z. Accessed [access date].
BibTeX
@misc{toll-e-tenjin-sh-api-read-handle-slug-ce23dc-2026-10-13T14-08Z,
author = {TOLL},
title = {read on tenjin.sh},
howpublished = {\url{https://tollindex.com/e/tenjin-sh-api-read-handle-slug-ce23dc/at/2026-10-13T14-08Z}},
year = {2026},
month = {10},
note = {Pinned view of the snapshot of 2026-10-13 14:08 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.