weather.hugen.tokyo/weather/current

caution grade B Hugen Weather API Base manual submission confidence 0.42
https://weather.hugen.tokyo/weather/current?city=Tokyo

As of 2026-08-02, weather.hugen.tokyo/weather/current on Base held a flawless 100.0% uptime across 27 reliability checks since first seen 2026-08-01 (1 day). Responses came back slow at 1811 ms average from a single EU vantage point (so this includes network distance to the endpoint) and it has held its advertised price steady at $0.0100. Its x402-trust grade is B (score 71.0 from a moderate sample, tracked for 1 day), but confidence is still limited, so treat the grade as provisional rather than a green light.

Advertised descriptionInstant structured weather by city name or coordinates -- no separate geocoding step, no API key registration, no rate limits. Current conditions and 1-7 day forecasts. $0.01 per request, x402/USDC on Base. Independently reported ~21,800 transactions and 242 distinct buyers per third-party x402 market analysis.(Provider-supplied: an unverified claim, not checked by us. The trust grade above is our independent measurement.)
Cached snapshot, computed 14 hours ago (refreshed at least every 24h). This is the full-density trust score computed from every probe, same as the paid API... but it may be up to 24 hours old. For a guaranteed-current answer it re-probes the endpoint live at the moment you ask, adds a confidence band, the full component breakdown, structured risk flags and on-chain settlement proof:
Browser wallet payment, no code required — agents use POST /v1/x402-trust or the x402_trust_score MCP tool.
30-day uptime
100.0%
Avg latency (EU)
1811 ms
slow · from EU vantage
Confidence
0.42
full-density score
Advertised price
$0.01
USDC
Price stability
Stable
last 30 days
Probes (30d)
27
full record · up to 48/day

Latency is measured from a single EU vantage point; includes network round-trip distance to the endpoint; a geographically distant endpoint reads slower even when its server is fast, so it is only lightly weighted in the score.

↑ 10 better alternatives available

10 better-scored (some cheaper) endpoints serving a semantically similar purpose exist.

We don't reveal which ones here. The ranked list (resource URLs, exact scores, prices & similarity, etc...) is one paid call away — purchase it right here with a browser wallet, no code required:

A wallet payment page opens first; approve the USDC payment and the ranked JSON list loads right in your browser. Agents use the x402_find_alternatives MCP tool or POST /v1/similar directly.

Full observation record ▾
Trust gradeB (score 71.0)
Recommendationcaution
Confidence0.42 — full-density (every probe in the 30-day window)
30-day uptime100.0%
Avg latency (EU vantage)1811 ms
Probes (30d)27
Advertised price$0.01 USDC
Price stability (30d)stable
Networkeip155:8453
First seen2026-08-01
Last probed2026-08-02
Statuslisted
Snapshot computed2026-08-02 08:34 UTC
This is the free cached snapshot. Here's what the paid API adds.
  • Live probe at decision time:
    We re-check the endpoint the moment you ask (timestamped) and compute the score from all scores up until this moment, instead of this cached snapshot that may be up to 24h old.
  • Confidence band, full component breakdown & structured risk flags:
    Exactly why the score is what it is, machine-readable.
  • On-chain settlement proof:
    Real USDC volume & distinct-payer count for the payTo wallet: is anyone actually paying it?
  • 90-day raw history:
    Every listing/price/payTo change and probe result (via POST /v1/x402-history), up to 90 days back.
  • The ranked better-scored alternatives:
    The resource URLs, scores & prices we don't reveal above (via POST /v1/similar), if there are better alternatives available.
  • Change & liveness alerts:
    Get notified on payTo/price changes, spec regressions or downtime (via POST /v1/watch-endpoint-30d). Connect up to 10 Discord / Slack webhooks or poll regularly with bearer auth. Increases probe-density to every 5 minutes instead of the usual 30 for the watched endpoint.

... Simply give your agents the tools to do all of that for you, with a simple command
$npx -y x402-trust-mcp

Prefer HTTP? Call POST /v1/x402-trust directly (pay-per-call over x402, from $0.005).