mr-river3.makar52nn2016.workers.dev
https://mr-river3.makar52nn2016.workers.dev/api/uuidRandom UUID v4 — idempotency keys and x402 requestKeys on demand; canonical low-cost target for testing x402 stacks
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
0.0% avgResponse time
Data table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 11/12/2026, 8:00:00 AM | 0% | 1 | — |
| 11/14/2026, 8:00:00 PM | 0% | 1 | — |
| 11/16/2026, 9:00:00 PM | 0% | 1 | — |
- Availability
- 43
- Latency
- not yet measured
- Security
- 100
- Transparency
- 31
- Activity
- 8
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 14% — 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
- CloudFlare, Inc.
- Domain registered
- 2019-02-08
- Hosting network
- CLOUDFLARENET
- 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)
Payments per day
last payment 11/9/2026Data table
| Day | Payments | Volume (USD) | Paying wallets |
|---|---|---|---|
| 10/20/2026 | 92 | 0.15 | 3 |
| 10/21/2026 | 2 | 0 | 1 |
| 10/22/2026 | 2 | 0 | 1 |
| 10/23/2026 | 1 | 0 | 1 |
| 10/24/2026 | 52 | 0.13 | 3 |
| 10/25/2026 | 28 | 2.26 | 2 |
| 10/26/2026 | 117 | 9.05 | 3 |
| 10/27/2026 | 124 | 9.59 | 4 |
| 10/28/2026 | 70 | 0.09 | 13 |
| 10/29/2026 | 813 | 9.74 | 8 |
| 10/30/2026 | 34 | 0.2 | 1 |
| 10/31/2026 | 42 | 0.04 | 4 |
| 11/1/2026 | 118 | 1.48 | 14 |
| 11/2/2026 | 85 | 0.85 | 14 |
| 11/3/2026 | 168 | 0.74 | 13 |
| 11/5/2026 | 30 | 1.32 | 12 |
| 11/6/2026 | 30 | 0.87 | 9 |
| 11/7/2026 | 20 | 0.62 | 8 |
| 11/8/2026 | 4 | 0.4 | 2 |
| 11/9/2026 | 2 | 0.11 | 2 |
Payout address changed 20 times, last on 11/11/2026
- 0x46f3…d411 → 0x48D1…2d67 (base) · 11/11/2026
- 0x48D1…2d67 → 0x46f3…d411 (base) · 11/11/2026
- 0x46f3…d411 → 0x48D1…2d67 (base) · 11/10/2026
- 0x48D1…2d67 → 0x46f3…d411 (base) · 11/10/2026
- 0x46f3…d411 → 0x48D1…2d67 (base) · 11/10/2026
- 0x48D1…2d67 → 0x46f3…d411 (base) · 11/10/2026
- 0x46f3…d411 → 0x48D1…2d67 (base) · 11/9/2026
- 0xf47b…512E → 0x46f3…d411 (base) · 11/6/2026
- 0x46f3…d411 → 0xf47b…512E (base) · 11/6/2026
- 0xf47b…512E → 0x46f3…d411 (base) · 11/6/2026
- 0x46f3…d411 → 0xf47b…512E (base) · 11/5/2026
- 0xf47b…512E → 0x46f3…d411 (base) · 11/5/2026
- 0x46f3…d411 → 0xf47b…512E (base) · 11/5/2026
- 0xf47b…512E → 0x46f3…d411 (base) · 11/5/2026
- 0x46f3…d411 → 0xf47b…512E (base) · 11/4/2026
- 0xf47b…512E → 0x46f3…d411 (base) · 11/4/2026
- 0x46f3…d411 → 0xf47b…512E (base) · 11/4/2026
- 0xf47b…512E → 0x46f3…d411 (base) · 11/4/2026
- 0x46f3…d411 → 0xf47b…512E (base) · 11/3/2026
- 0xf47b…512E → 0x46f3…d411 (base) · 11/3/2026
A changed payout address is worth a second look — it can be routine, but it is also how a hijacked listing redirects funds.
This payout wallet is shared: figures cover all 124 endpoints paid at it, since payments cannot be attributed to one of them. Only payments settled on chains and facilitators we index.
Response schema
{
"properties": {
"uuid": {
"type": "string"
},
"version": {
"type": "string"
}
},
"type": "object"
}