_ registry / a2a JSONRPC · checked 18h ago

Japan Weather API

https://weather.agentic-jp.com

Registry code: c2589cbcaed1c735

api record

Japan Meteorological Agency forecasts, overviews, and weather warnings for every JP region, with city-name aliases. Pay-per-call HTTP API using the x402 payment protocol (USDC on Base / Polygon / Solana) — no API key or signup. NOTE: this origin serves plain HTTP+x402, not the A2A JSON-RPC protocol; use the machine-readable interfaces below.

endpoint
https://weather.agentic-jp.com/
protocol
JSONRPC ·0.2
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is Japan Weather API live?
Yes — it answered the hub's last check (checked 18h ago). It answered 100% of checks over the last 30 days.
Is Japan Weather API free to use?
Yes — the hub reached it with no key and no payment.
What tools does Japan Weather API have?
2 tools: weather forecast, weather warnings.
Is Japan Weather API safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.5%

90 days 98.3%· all time 98.8%

latency
850ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 474 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
weather & environment forecast
used for
  • get a japan weather forecast
  • check japan weather warnings
takes → gives
text → data
tools
2 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address also stands behind 6 other origins: the chain figures are the gateway's, not this listing's alone. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
25

distinct

settlements
92

last 2026-11-10

received on chain
0.27 USDC

shared-payto

inferred, not observed

Access was read off the card rather than seen on the wire: inferred from the card: it declares no security schemes; the endpoint did not answer the protocol directly

_ what it can do 2 tools
2 never probed 0 of 2 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • weather-forecast reads unknown never probed
  • weather-warnings reads unknown never probed
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your agent card — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id c2589cbcaed1c735.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/c2589cbcaed1c735/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/c2589cbcaed1c735/badge.svg)](https://brick.blue/agent/c2589cbcaed1c735?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
68%

How much of the published card is filled in. Not a judgement of the agent — a measure of what it told the world about itself.

spec deviations
4

Places where the published card departs from the specification. Recorded rather than hidden, and counted against every agent the same way.

  • defaultInputModes missing (REQUIRED)
  • defaultOutputModes missing (REQUIRED)
  • skills[0].tags missing (REQUIRED)
  • skills[1].tags missing (REQUIRED)
_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on agentic-jp.com 7 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.