paywall.wickedapi.com

https://paywall.wickedapi.com/wickedapi/weather

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

Demo weather - current conditions for New York City

66
reliability

Reliability & health

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

Uptime

100.0% avg
0% 50% 100% Thu 8 PMSun 8 AMTue 9 PM

Response time

p50 349ms · p95 352ms
0ms 200ms 400ms Thu 8 PMSun 8 AMTue 9 PM
Data table
Reliability history per time bucket over the last 7 days (hourly).
Bucket Uptime Probes Response time
11/12/2026, 8:00:00 PM 100% 1 341ms
11/15/2026, 8:00:00 AM 100% 1 352ms
11/17/2026, 9:00:00 PM 100% 1 349ms
66
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
98

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
67

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

Activity
9

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
Cloudflare, Inc.
Domain registered
2026-06-15
Hosting network
CLOUD-FSN1
Hosting country
DE

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)

167
payments (30d)
0.6
USD volume (30d)
26
paying wallets (30d)

Payments per day

last payment 11/18/2026
0 15 30 Oct 21Oct 29Nov 9Nov 18
Data table
Settled payments per day.
Day Payments Volume (USD) Paying wallets
10/21/2026 6 0.02 2
10/22/2026 8 0.05 4
10/23/2026 4 0.05 2
10/24/2026 9 0.04 1
10/25/2026 19 0.02 4
10/27/2026 1 0 1
10/28/2026 2 0.01 1
10/29/2026 7 0.01 7
10/30/2026 9 0.01 4
11/1/2026 7 0.01 2
11/2/2026 1 0.01 1
11/4/2026 5 0.01 4
11/6/2026 10 0.1 1
11/7/2026 1 0.02 1
11/8/2026 1 0 1
11/9/2026 1 0 1
11/11/2026 14 0.04 3
11/12/2026 21 0.03 6
11/13/2026 10 0.02 4
11/14/2026 10 0.02 4
11/16/2026 9 0.02 1
11/17/2026 1 0 1
11/18/2026 11 0.11 2

Payout address changed 1 time, last on 10/16/2026

  • 0xB71C…A9f6 → 0x63Eb…C8A4 (base) · 10/16/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 30 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.

Response schema
{
  "properties": {
    "current": {
      "properties": {
        "temperature_2m": {
          "type": "number"
        },
        "time": {
          "type": "string"
        },
        "weather_code": {
          "type": "integer"
        },
        "wind_speed_10m": {
          "type": "number"
        }
      },
      "type": "object"
    },
    "current_units": {
      "additionalProperties": {
        "type": "string"
      },
      "type": "object"
    },
    "latitude": {
      "type": "number"
    },
    "longitude": {
      "type": "number"
    },
    "timezone": {
      "type": "string"
    }
  },
  "required": [
    "latitude",
    "longitude",
    "current"
  ],
  "type": "object"
}