wouldpayagain.com
https://wouldpayagain.com/api/issue/1Shares a payout wallet with 1 other endpoint — its adoption is attributed from that shared wallet's traffic, not earned exclusively.
Would Pay Again, Issue #3 — full content as JSON {title, web_url, html, markdown}.
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 |
|---|---|---|---|
| 8/14/2026, 1:00:00 PM | 0% | 1 | — |
| 8/15/2026, 1:00:00 PM | 0% | 1 | — |
| 8/16/2026, 1:00:00 PM | 0% | 1 | — |
| 8/17/2026, 1:00:00 PM | 0% | 1 | — |
| 8/18/2026, 1:00:00 PM | 0% | 1 | — |
| 8/19/2026, 1:00:00 PM | 0% | 1 | — |
| 8/20/2026, 1:00:00 PM | 0% | 1 | — |
- Availability
- 0
- Latency
- not yet measured
- Security
- 100
- Transparency
- 36
- Activity
- 3
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 58% — 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
- Porkbun LLC
- Domain registered
- 2026-07-18
- 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)
Payments per day
last payment 8/10/2026Data table
| Day | Payments | Volume (USD) | Paying wallets |
|---|---|---|---|
| 7/24/2026 | 2 | 0 | 2 |
| 7/27/2026 | 1 | 0.05 | 1 |
| 7/31/2026 | 1 | 0 | 1 |
| 8/5/2026 | 8 | 0.18 | 1 |
| 8/8/2026 | 1 | 0.2 | 1 |
| 8/10/2026 | 3 | 1.2 | 1 |
Payout address changed 20 times, last on 8/21/2026
- 0x2284…4BFB → 0xF497…2Fb0 (base) · 8/21/2026
- 0xF497…2Fb0 → 0x2284…4BFB (base) · 8/21/2026
- 0x2284…4BFB → 0xF497…2Fb0 (base) · 8/21/2026
- 0xF497…2Fb0 → 0x2284…4BFB (base) · 8/21/2026
- 0x2284…4BFB → 0xF497…2Fb0 (base) · 8/20/2026
- 0xF497…2Fb0 → 0x2284…4BFB (base) · 8/20/2026
- 0x2284…4BFB → 0xF497…2Fb0 (base) · 8/20/2026
- 0xF497…2Fb0 → 0x2284…4BFB (base) · 8/20/2026
- 0x2284…4BFB → 0xF497…2Fb0 (base) · 8/19/2026
- 0xF497…2Fb0 → 0x2284…4BFB (base) · 8/19/2026
- 0x2284…4BFB → 0xF497…2Fb0 (base) · 8/19/2026
- 0xF497…2Fb0 → 0x2284…4BFB (base) · 8/19/2026
- 0x2284…4BFB → 0xF497…2Fb0 (base) · 8/18/2026
- 0xF497…2Fb0 → 0x2284…4BFB (base) · 8/18/2026
- 0x2284…4BFB → 0xF497…2Fb0 (base) · 8/18/2026
- 0xF497…2Fb0 → 0x2284…4BFB (base) · 8/18/2026
- 0x2284…4BFB → 0xF497…2Fb0 (base) · 8/17/2026
- 0xF497…2Fb0 → 0x2284…4BFB (base) · 8/17/2026
- 0x2284…4BFB → 0xF497…2Fb0 (base) · 8/17/2026
- 0xF497…2Fb0 → 0x2284…4BFB (base) · 8/17/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 6 endpoints paid at it, since payments cannot be attributed to one of them. Only payments settled on chains and facilitators we index.
Linked by wallet — likely same operator
On-chain agent identity and the x402 endpoint that shares its settlement wallet.