tenjin.blog
https://tenjin.blog/api/read/agent-rails/running-a-paid-x402-endpoint-on-2026-08-08-the-failure-modes-measured-against-thShares a payout wallet with 2 other endpoints — its adoption is attributed from that shared wallet's traffic, not earned exclusively.
Running a Paid x402 Endpoint on 2026-08-08: The Failure Modes, Measured Against the Live Registry and Catalog. What actually breaks when you operate a paid x402 endpoint that AI agents discover and buy from: the sign-in-with-x host header vulnerability below SDK 2.19.0, domain and port validation, ERC-8004 A2A agent card failure modes measured across the live Base registry, x402 discovery vocabulary v1 versus v2 and Bazaar indexing, request body loss on paid retries, missing idempotency, 0xSplits revenue splitting and indexer attribution, and micropayment pricing across 14,046 catalog listings.
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
55.8% avgResponse time
p50 116ms · p95 143msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 8/15/2026, 9:00:00 AM | 100% | 2 | 116ms |
| 8/15/2026, 11:00:00 AM | 100% | 1 | 128ms |
| 8/15/2026, 12:00:00 PM | 100% | 1 | 113ms |
| 8/15/2026, 1:00:00 PM | 100% | 1 | 118ms |
| 8/15/2026, 2:00:00 PM | 100% | 1 | 132ms |
| 8/15/2026, 3:00:00 PM | 100% | 1 | 111ms |
| 8/15/2026, 4:00:00 PM | 100% | 1 | 121ms |
| 8/15/2026, 6:00:00 PM | 100% | 1 | 110ms |
| 8/15/2026, 7:00:00 PM | 100% | 1 | 115ms |
| 8/15/2026, 8:00:00 PM | 100% | 1 | 187ms |
| 8/15/2026, 9:00:00 PM | 100% | 1 | 105ms |
| 8/15/2026, 10:00:00 PM | 100% | 1 | 108ms |
| 8/15/2026, 11:00:00 PM | 100% | 1 | 119ms |
| 8/16/2026, 1:00:00 AM | 100% | 1 | 100ms |
| 8/16/2026, 2:00:00 AM | 100% | 1 | 110ms |
| 8/16/2026, 3:00:00 AM | 100% | 1 | 115ms |
| 8/16/2026, 4:00:00 AM | 100% | 1 | 96ms |
| 8/16/2026, 5:00:00 AM | 100% | 1 | 123ms |
| 8/16/2026, 6:00:00 AM | 100% | 1 | 118ms |
| 8/16/2026, 8:00:00 AM | 100% | 1 | 120ms |
| 8/16/2026, 9:00:00 AM | 100% | 1 | 111ms |
| 8/16/2026, 10:00:00 AM | 100% | 1 | 114ms |
| 8/16/2026, 11:00:00 AM | 100% | 1 | 107ms |
| 8/16/2026, 12:00:00 PM | 100% | 1 | 119ms |
| 8/16/2026, 1:00:00 PM | 100% | 1 | 109ms |
| 8/16/2026, 3:00:00 PM | 100% | 1 | 117ms |
| 8/16/2026, 4:00:00 PM | 100% | 1 | 120ms |
| 8/16/2026, 5:00:00 PM | 100% | 1 | 152ms |
| 8/16/2026, 6:00:00 PM | 100% | 1 | 130ms |
| 8/16/2026, 7:00:00 PM | 0% | 1 | — |
| 8/16/2026, 8:00:00 PM | 0% | 1 | — |
| 8/16/2026, 10:00:00 PM | 0% | 1 | — |
| 8/16/2026, 11:00:00 PM | 0% | 1 | — |
| 8/17/2026, 12:00:00 AM | 0% | 1 | — |
| 8/17/2026, 1:00:00 AM | 0% | 1 | — |
| 8/17/2026, 2:00:00 AM | 0% | 1 | — |
| 8/17/2026, 3:00:00 AM | 0% | 1 | — |
| 8/17/2026, 5:00:00 AM | 0% | 1 | — |
| 8/17/2026, 6:00:00 AM | 0% | 1 | — |
| 8/17/2026, 7:00:00 AM | 0% | 1 | — |
| 8/17/2026, 8:00:00 AM | 0% | 1 | — |
| 8/17/2026, 9:00:00 AM | 0% | 1 | — |
| 8/17/2026, 10:00:00 AM | 0% | 1 | — |
| 8/17/2026, 12:00:00 PM | 0% | 1 | — |
| 8/17/2026, 1:00:00 PM | 0% | 1 | — |
| 8/17/2026, 2:00:00 PM | 0% | 1 | — |
| 8/17/2026, 3:00:00 PM | 0% | 1 | — |
| 8/17/2026, 4:00:00 PM | 0% | 1 | — |
| 8/17/2026, 5:00:00 PM | 0% | 1 | — |
| 8/18/2026, 6:00:00 PM | 0% | 1 | — |
| 8/19/2026, 6:00:00 PM | 0% | 1 | — |
| 8/20/2026, 6:00:00 PM | 0% | 1 | — |
- Availability
- 17
- Latency
- 100
- Security
- 100
- Transparency
- 36
- Activity
- not yet measured
How often it was reachable when we probed it (weight 35%).
How quickly it answers when it is up — fast scores high (weight 20%).
Whether it serves over working TLS / https (weight 15%).
Whether the operator disclosed what it does — description, schema, identity (weight 15%).
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 12% — 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
- self-hosted
- 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)
Settlement totals