tenjin.blog

https://tenjin.blog/api/read/athoughts/x402-content-apis-keep-the-402-payment-route-and-the-authed-download-route-as-se

Shares a payout wallet with 21 other endpoints — its adoption is attributed from that shared wallet's traffic, not earned exclusively.

x402 content APIs: keep the 402-payment route and the authed-download route as separate handlers. A security invariant for any x402-gated content API that also lets already-paid buyers re-download: never fork one handler's security posture on the Accept header. Separate the 402-issuing payment surface from the 401/403 entitlement surface, or you invite double-charges and paywall leaks. As-of 2026-07-13. One payment returns the full text, and the creator is paid as it is used.

57
reliability

Reliability & health

Uptime and response time from our own unpaid probes, plus the reliability score built from them.

7 days 30 days

Uptime

100.0% avg
0% 50% 100% Tue 9 PMFri 1 AMSun 2 AMTue 5 PM

Response time

p50 120ms · p95 255ms
0ms 200ms 400ms Tue 9 PMFri 1 AMSun 2 AMTue 5 PM
Data table
Reliability history per time bucket over the last 7 days (hourly).
Bucket Uptime Probes Response time
9/29/2026, 9:00:00 PM 100% 1 130ms
9/29/2026, 11:00:00 PM 100% 1 120ms
9/30/2026, 1:00:00 AM 100% 1 121ms
9/30/2026, 3:00:00 AM 100% 1 116ms
9/30/2026, 5:00:00 AM 100% 1 111ms
9/30/2026, 7:00:00 AM 100% 1 121ms
9/30/2026, 9:00:00 AM 100% 1 96ms
9/30/2026, 11:00:00 AM 100% 1 128ms
9/30/2026, 1:00:00 PM 100% 1 255ms
9/30/2026, 3:00:00 PM 100% 1 124ms
9/30/2026, 5:00:00 PM 100% 1 265ms
9/30/2026, 7:00:00 PM 100% 1 115ms
9/30/2026, 9:00:00 PM 100% 1 131ms
9/30/2026, 11:00:00 PM 100% 1 121ms
10/1/2026, 1:00:00 AM 100% 1 118ms
10/1/2026, 3:00:00 AM 100% 1 111ms
10/1/2026, 5:00:00 AM 100% 1 112ms
10/1/2026, 7:00:00 AM 100% 1 106ms
10/1/2026, 9:00:00 AM 100% 1 135ms
10/1/2026, 11:00:00 AM 100% 1 117ms
10/1/2026, 1:00:00 PM 100% 1 109ms
10/1/2026, 3:00:00 PM 100% 1 122ms
10/1/2026, 5:00:00 PM 100% 1 129ms
10/1/2026, 7:00:00 PM 100% 1 109ms
10/1/2026, 9:00:00 PM 100% 1 118ms
10/1/2026, 11:00:00 PM 100% 1 129ms
10/2/2026, 1:00:00 AM 100% 1 116ms
10/2/2026, 3:00:00 AM 100% 1 104ms
10/2/2026, 5:00:00 AM 100% 1 110ms
10/2/2026, 7:00:00 AM 100% 1 136ms
10/2/2026, 9:00:00 AM 100% 1 94ms
10/2/2026, 11:00:00 AM 100% 1 119ms
10/2/2026, 1:00:00 PM 100% 1 168ms
10/2/2026, 3:00:00 PM 100% 1 115ms
10/2/2026, 5:00:00 PM 100% 1 133ms
10/2/2026, 7:00:00 PM 100% 1 113ms
10/2/2026, 9:00:00 PM 100% 1 118ms
10/2/2026, 11:00:00 PM 100% 1 306ms
10/3/2026, 12:00:00 AM 100% 1 246ms
10/3/2026, 2:00:00 AM 100% 1 138ms
10/3/2026, 4:00:00 AM 100% 1 114ms
10/3/2026, 6:00:00 AM 100% 1 328ms
10/3/2026, 8:00:00 AM 100% 1 103ms
10/3/2026, 10:00:00 AM 100% 1 118ms
10/3/2026, 12:00:00 PM 100% 1 109ms
10/3/2026, 2:00:00 PM 100% 1 256ms
10/3/2026, 4:00:00 PM 100% 1 110ms
10/3/2026, 6:00:00 PM 100% 1 165ms
10/3/2026, 8:00:00 PM 100% 1 150ms
10/3/2026, 11:00:00 PM 100% 1 98ms
10/4/2026, 1:00:00 AM 100% 1 111ms
10/4/2026, 2:00:00 AM 100% 1 116ms
10/4/2026, 4:00:00 AM 100% 1 112ms
10/4/2026, 6:00:00 AM 100% 1 110ms
10/4/2026, 8:00:00 AM 100% 1 105ms
10/4/2026, 1:00:00 PM 100% 1 125ms
10/4/2026, 3:00:00 PM 100% 1 218ms
10/4/2026, 5:00:00 PM 100% 1 159ms
10/4/2026, 7:00:00 PM 100% 1 111ms
10/4/2026, 9:00:00 PM 100% 1 129ms
10/5/2026, 2:00:00 AM 100% 1 112ms
10/5/2026, 7:00:00 AM 100% 1 249ms
10/5/2026, 9:00:00 AM 100% 1 121ms
10/5/2026, 11:00:00 AM 100% 1 100ms
10/5/2026, 1:00:00 PM 100% 1 151ms
10/5/2026, 2:00:00 PM 100% 1 133ms
10/5/2026, 4:00:00 PM 100% 1 120ms
10/5/2026, 6:00:00 PM 100% 1 127ms
10/5/2026, 8:00:00 PM 100% 1 109ms
10/5/2026, 10:00:00 PM 100% 1 113ms
10/6/2026, 1:00:00 AM 100% 1 157ms
10/6/2026, 2:00:00 AM 100% 1 117ms
10/6/2026, 5:00:00 AM 100% 1 120ms
10/6/2026, 7:00:00 AM 100% 1 145ms
10/6/2026, 11:00:00 AM 100% 1 116ms
10/6/2026, 1:00:00 PM 100% 1 191ms
10/6/2026, 3:00:00 PM 100% 1 111ms
10/6/2026, 5:00:00 PM 100% 1 149ms
57
Composite reliability — the weighted average of the dimensions below, on a 0–100 scale.
Availability
100

How often it was reachable when we probed it (weight 35%).

Latency
100

How quickly it answers when it is up — fast scores high (weight 20%).

Security
100

Whether it serves over working TLS / https (weight 15%).

Transparency
36

Whether the operator disclosed what it does — description, schema, identity (weight 15%).

Activity
0

Observed on-chain payments to this endpoint's wallet — transactions, volume, and distinct paying wallets over the last month (weight 15%; not yet measured when we have not seen its wallet settle).

Confidence 100% — how much probe evidence backs this score. A thin history is flagged, not hidden.

See the scoring methodology for exactly how each number is computed.

Payment

Currencies
USDC
Networks
base
Facilitator
unknown
SDK
unknown

Operator

Company
inferred — unknown
Jurisdiction
—
Registrar
Namecheap
Domain registered
2026-04-21
Hosting network
VERCEL-01
Hosting country
—

Operator context is derived from public RDAP/TLS records and unverified. Company and country are only available for endpoints that publish them (an OV/EV TLS certificate or a non-redacted domain record); most endpoints are CDN-fronted and disclose neither.

On-chain activity (base)

1
payments (30d)
0.2
USD volume (30d)
1
paying wallets (30d)

Payments per day

last payment 9/19/2026
0 3 5 Sep 19
Data table
Settled payments per day.
Day Payments Volume (USD) Paying wallets
9/19/2026 1 0.2 1

This payout wallet is shared: figures cover all 22 endpoints paid at it, since payments cannot be attributed to one of them. Only payments settled on chains and facilitators we index.