wouldpayagain.com

https://wouldpayagain.com/api/reviews

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

Machine-readable x402 endpoint review feed (v2) from the Would Pay Again newsletter. JSON array of {feed_version, endpoint, origin, price_paid_usdc, listed_price_usdc, settlement_tx, settlement_network, latency_ms, latency_1_5, output_quality_1_5, docs_quality_1_5, would_pay_again_1_5, delivered, sample_count, request_example, verdict, tested_at}. Prices are chain-settled amounts with Basescan-checkable tx refs.

63
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% Sep 6Sep 16Sep 25Oct 5

Response time

p50 708ms · p95 841ms
0ms 400ms 800ms Sep 6Sep 16Sep 25Oct 5
Data table
Reliability history per time bucket over the last 30 days (daily).
Bucket Uptime Probes Response time
9/6/2026, 12:00:00 AM 100% 17 711ms
9/7/2026, 12:00:00 AM 100% 15 98ms
9/8/2026, 12:00:00 AM 100% 21 708ms
9/9/2026, 12:00:00 AM 100% 20 710ms
9/10/2026, 12:00:00 AM 100% 15 348ms
9/11/2026, 12:00:00 AM 100% 9 85ms
9/12/2026, 12:00:00 AM 100% 9 82ms
9/13/2026, 12:00:00 AM 100% 16 697ms
9/14/2026, 12:00:00 AM 100% 16 686ms
9/15/2026, 12:00:00 AM 100% 15 698ms
9/16/2026, 12:00:00 AM 100% 16 714ms
9/17/2026, 12:00:00 AM 100% 15 699ms
9/18/2026, 12:00:00 AM 100% 13 711ms
9/19/2026, 12:00:00 AM 100% 13 721ms
9/20/2026, 12:00:00 AM 100% 12 670ms
9/21/2026, 12:00:00 AM 100% 12 676ms
9/22/2026, 12:00:00 AM 100% 13 680ms
9/23/2026, 12:00:00 AM 100% 12 708ms
9/24/2026, 12:00:00 AM 100% 14 728ms
9/25/2026, 12:00:00 AM 100% 14 90ms
9/26/2026, 12:00:00 AM 100% 15 121ms
9/27/2026, 12:00:00 AM 100% 14 130ms
9/28/2026, 12:00:00 AM 100% 13 109ms
9/29/2026, 12:00:00 AM 100% 13 716ms
9/30/2026, 12:00:00 AM 100% 12 768ms
10/1/2026, 12:00:00 AM 100% 13 739ms
10/2/2026, 12:00:00 AM 100% 13 770ms
10/3/2026, 12:00:00 AM 100% 13 718ms
10/4/2026, 12:00:00 AM 100% 10 708ms
10/5/2026, 12:00:00 AM 100% 7 739ms
63
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
84

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
61

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

Activity
14

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
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)

95
payments (30d)
3.37
USD volume (30d)
12
paying wallets (30d)

Payments per day

last payment 10/5/2026
0 10 20 Sep 7Sep 15Sep 24Oct 5
Data table
Settled payments per day.
Day Payments Volume (USD) Paying wallets
9/7/2026 1 0.01 1
9/9/2026 1 0.01 1
9/10/2026 15 0.15 1
9/11/2026 3 0.03 1
9/12/2026 3 0.03 1
9/14/2026 1 0 1
9/15/2026 2 0.02 1
9/16/2026 1 0.01 1
9/17/2026 1 0.01 1
9/18/2026 3 0.03 1
9/19/2026 4 2.47 2
9/22/2026 12 0.12 1
9/23/2026 15 0.15 2
9/24/2026 11 0.11 2
9/25/2026 4 0.04 2
9/29/2026 2 0.02 1
10/1/2026 10 0.1 1
10/2/2026 2 0.02 1
10/4/2026 1 0.01 1
10/5/2026 3 0.03 1

Payout address changed 1 time, last on 9/12/2026

  • 0xF497…2Fb0 → 0x0828…E998 (base) · 9/12/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 4 endpoints paid at it, since payments cannot be attributed to one of them. Only payments settled on chains and facilitators we index.

Response schema 
{
  "items": {
    "properties": {
      "delivered": {
        "type": "boolean"
      },
      "docs_quality_1_5": {
        "maximum": 5,
        "minimum": 1,
        "type": "integer"
      },
      "endpoint": {
        "format": "uri",
        "type": "string"
      },
      "feed_version": {
        "type": "integer"
      },
      "latency_1_5": {
        "maximum": 5,
        "minimum": 1,
        "type": "integer"
      },
      "latency_ms": {
        "type": [
          "integer",
          "null"
        ]
      },
      "listed_price_usdc": {
        "type": "number"
      },
      "origin": {
        "format": "uri",
        "type": "string"
      },
      "output_quality_1_5": {
        "maximum": 5,
        "minimum": 1,
        "type": "integer"
      },
      "price_paid_usdc": {
        "type": "number"
      },
      "request_example": {
        "type": "object"
      },
      "sample_count": {
        "type": "integer"
      },
      "settlement_network": {
        "type": "string"
      },
      "settlement_tx": {
        "type": "string"
      },
      "tested_at": {
        "format": "date-time",
        "type": "string"
      },
      "verdict": {
        "type": "string"
      },
      "would_pay_again_1_5": {
        "maximum": 5,
        "minimum": 1,
        "type": "integer"
      }
    },
    "required": [
      "feed_version",
      "endpoint",
      "price_paid_usdc",
      "listed_price_usdc",
      "settlement_tx",
      "delivered",
      "would_pay_again_1_5"
    ],
    "type": "object"
  },
  "type": "array"
}