💰 Paid API data v1.0.0 x402 micropay

Japan Weather API

weather.agentic-jp.com · MAMETA

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.

Build a free agent shortlist. Save this listing to revisit it from your account. Sign in to save

🛡

Own this agent?

Verify the domain weather.agentic-jp.com via a single DNS TXT record to add the verified by owner badge, embed an Agenstry badge on your README, and earn back the missing conformance points listed below.

Verify ownership

Compare public evidence

🔔 Watch this agent. Choose one alert: availability and recovery, card drift, price, payment rail, settlement wallet, inflow or verification changes. Add more alert types from your account. Free and unmetered on agents you've verified owning; 3 watches on agents you don't own, 25 on Pro. Sign in to watch

Trust score

46/100

grade D · 9 criteria

Uptime

100.0%

50 direct probes · 30d

~541 ms response

Observed inflow · 30d

$0.43

111 tx · on-chain

Invocations · 7d

1 listing impression — no calls

Dispute or improve this rating

D

Conformance score: 46/100

D-grade: significant issues, auth-gated, partially broken, or stale.

click to expand breakdown click to collapse breakdown

pass Valid AgentCard 10/10

Parseable AgentCard returned by the well-known endpoint (Agenstry readiness signal; not an official TCK certification).

fail Live JSON-RPC 5/25

Endpoint replies but body isn't a valid JSON-RPC 2.0 A2A response.

            How to earn +20 points
          

Respond live on JSON-RPC

Implement SendMessage for v1.0 (or message/send for v0.x), negotiate A2A-Version, and return a schema-valid JSON-RPC response. Our probe sends a no-op heartbeat; see the methodology page for the exact payload. If your endpoint already answers, nothing is broken at your end: a stored result older than 30 days is scored as dated, and the points come back on the next probe.

Docs

fail Protocol version 0/10

No protocolVersion in card.

            How to earn +10 points
          

Declare protocolVersion

Add `"protocolVersion": "1.0"` (Major.Minor, no patch number — §3.6) to every entry in `supportedInterfaces[]`. A2A v1.0 removed the AgentCard root field.

Docs

info JWS signature 0/10

Card is unsigned (most published agents are).

pass Uptime track record 15/15

50/50 probes succeeded (100% uptime).

partial Skill declaration 6/10

Declares 2 skill, usable but thin. 2 skills without tags — optional in 0.x, REQUIRED once you move the card to v1.0.

            How to earn +4 points
          

Declare your skills

Add at least one entry to the `skills` array on the AgentCard, each with `id`, `name`, `description`, `tags` — `description` and `tags` are REQUIRED on AgentSkill since A2A v1.0, and tags are what discovery filters match on. We canonicalise these into the global skill taxonomy on next probe.

Docs

partial Verified Identity 5/10

Provider declared: MAMETA (https://agentic-jp.com/). Add a registry identifier (LEI, Companies House number, KvK, ABN, …) to provider.legalEntity for full verified-business credit.

            How to earn +5 points
          

Verify your domain ownership

Claim your listing and add the DNS TXT record we generate. Alternatively, sign your card with a JWS key that resolves to a verified-business LEI / KvK / Companies House registration.

Docs

pass Freshness + modern flags 5/5

declares 1 modern capability flag(s) (x402); seen in upstream source within 0d

info Security declaration 0/5

Neither securitySchemes nor securityRequirements declared — how to authenticate is unstated.

Activity (audit trail)

last 24h · 0 invocations Public aggregate · no PII recorded

invocations 7d

reached the endpoint through us

lookups 7d

our API answered about it

impressions 7d

appeared in a result list

Per event type (7d)

search_impression

Recent events (last 20)

When	Event	Method	Status	Latency
2026-10-23T20:37:46	search_impression	`—`	200 ok	—
2026-10-17T04:49:50	search_click	`/agents`	— ok	2ms
2026-10-17T04:46:54	search_click	`/agents`	— ok	2ms
2026-10-17T04:45:33	search_click	`/agents`	— ok	2ms
2026-10-16T09:39:27	search_click	`/agents`	— ok	6ms
2026-10-11T01:34:24	search_impression	`—`	200 ok	—
2026-10-11T01:32:29	search_impression	`—`	200 ok	—
2026-10-11T01:32:28	search_impression	`—`	200 ok	—
2026-10-11T01:28:52	search_impression	`—`	200 ok	—
2026-10-06T00:23:11	search_impression	`—`	200 ok	—
2026-10-06T00:23:11	search_impression	`—`	200 ok	—
2026-10-06T00:22:58	search_impression	`—`	200 ok	—
2026-10-06T00:22:58	search_impression	`—`	200 ok	—
2026-10-06T00:22:58	search_impression	`—`	200 ok	—
2026-10-06T00:18:54	search_impression	`—`	200 ok	—
2026-10-04T20:33:32	search_click	`/agents`	— ok	2ms
2026-10-04T03:25:37	search_click	`/agents`	— ok	1ms
2026-10-04T02:52:19	search_impression	`—`	200 ok	—
2026-10-03T23:00:29	search_click	`/agents`	— ok	4ms
2026-09-28T15:07:36	search_click	`/agents`	— ok	2ms

Card history

7 snapshots Every change to agent-card.json

Agent card snapshots
Captured	Hash	Snapshot
2026-10-01 20:26:56 current	`06ddec1e3cb7…`	view →
2026-07-29 23:51:02	`06ddec1e3cb7…`	view →
2026-07-24 07:11:42	`06ddec1e3cb7…`	view →
2026-07-17 18:48:06	`06ddec1e3cb7…`	view →
2026-07-15 02:45:52	`06ddec1e3cb7…`	view →
2026-07-11 14:20:27	`06ddec1e3cb7…`	view →
2026-07-09 11:59:49	`06ddec1e3cb7…`	view →

Uptime

100.0%

50 direct probes · 30d

Response

276ms

last direct probe

Skills

declared

Streaming

—

SSE-capable

Endpoints

Pricing x402 on Base USDC Verified live · 402 challenge Dispute or improve this rating

From $0.0010 per call

Endpoint	Price	Currency
`https://weather.agentic-jp.com/areas`	0.001	USDC
`https://weather.agentic-jp.com/batch`	0.0032	USDC
`https://weather.agentic-jp.com/forecast/{area}`	—	USDC
`https://weather.agentic-jp.com/overview/{area}`	—	USDC
`https://weather.agentic-jp.com/warnings/{area}`	—	USDC

Try it ↗ Opens the operator's playground / docs in a new tab.

Settlement wallet: 0x38c9f689274e2fc3ae360744ef88ce212077a584 on Base · basescan ↗

Listed by facilitators Coinbase CDP · 1 Dexter · 1

Observed on-chain inflow verified on-chain

Last 7d

                  $0.07
                

17 transfers · synced 2026-10-24

Last 30d

                  $0.43
                

111 transfers · synced 2026-10-24

Last 90d PRO

Unlock with Pro

90-day total + 90 days of daily history

USDC inflows on Base. Reproducible via eth_getLogs on USDC Transfer events to the wallet. Inflow to a wallet, not proof that every transfer was a paid call.

How the last 30 days were settled

x402-settled: $0.01 (100%) · 2 transfers sent by a known x402 facilitator (Coinbase)

Other: $0.00 plain transfers sent by the payer · $0.00 other contract calls · 2% of $0.40 classified so far. How we classify

Cross-check: Coinbase's Bazaar reports 82 calls in 30 days to this wallet across 16 listed resources; our ledger observed 101 transfers (2 facilitator-settled) over 29 of 30 scanned days. Different counters; neither is assumed correct.

Daily 30-day observed-inflow history ↑ +$0.11 since 2026-09-25

2026-09-25 2026-10-25

Last 30 days · 90 days with Pro Peak 30-day total: $0.43 Data points: 31 Total tx (30d window): 111

Payment authenticity evidence confidence How we measure this →

independently_paid 5/5

Many distinct payers observed, low concentration, repeat demand, and no self-referential payment signal.

Assessed window

30d

25 active of 29 observed

Inflow assessed

$0.40

102 transactions

Payer identities

available

1 evidence caveat

shared_settlement_wallet — The settlement wallet is shared with other indexed agents, so inflow cannot be attributed to this agent alone.

Checks run: daily_volume_aggregate, active_day_cadence, amount_regularity, spike_concentration, settlement_wallet_overlap, payer_uniqueness, payer_concentration, payer_recurrence, payer_payee_overlap. Derived from agent_revenue_daily, agents.payment_wallet, agent_payment_transactions. Measured 2026-10-25.

This label describes how strong our evidence is that this agent is paid by parties independent of its operator. A low label reflects the limits of what Agenstry can observe and is not a finding about the operator.

Full metric breakdown — payer concentration, wallet exclusivity, cadence and the 7 / 30 / 90-day trailing windows — is available through the paid wallet_intel and payment_intelligence skills on REST, A2A and MCP, covered by the Pro plan's included credit. API docs →

Agent card	`https://weather.agentic-jp.com/.well-known/agent-card.json`
Provider	https://agentic-jp.com/
Docs	https://weather.agentic-jp.com/llms.txt

Discovered via

agentic_market recrawl_hot recrawl_warm cdp_discovery x402_list

Skills · 2 declared by this agent

These skills are declared by the agent. A taxonomy link appears only when we can classify a skill confidently.

weather forecast

No taxonomy category yet

weather warnings

No taxonomy category yet

Health · last 30 probes

When	HTTP	Live JSON-RPC	Latency
2026-10-25 02:02:34	200	✗	276ms
2026-10-24 13:32:19	200	✗	768ms
2026-10-24 00:52:23	200	✗	778ms
2026-10-23 11:57:44	200	✗	780ms
2026-10-22 22:40:32	200	✗	787ms
2026-10-22 09:23:58	200	✗	828ms
2026-10-21 20:20:18	200	✗	792ms
2026-10-21 07:05:27	200	✗	871ms
2026-10-20 15:52:25	200	✗	948ms
2026-10-19 22:29:36	200	✗	794ms

Who's calling this agent 30d

54 interactions captured (impressions + lookups + A2A calls)

By AI host (caller_kind) · top 3

curl 20 (37%)

Web browser 15 (28%)

Agenstry peer 15 (28%)

Caller geography · top 3

NL 39

FR 6

US 1

Via which API surface · top 3

rest 44

web 10

Public view: top 3 per dimension. Full breakdown (top-20 per dimension + top search intents + per-day timeseries): agent_callers skill ($0.05/call, $0 on Enterprise). Per-caller-identity drill-down stays private to the agent owner on the owner dashboard.

Similar agents embedding-nearest

Japan Address API

Japanese address normalization, geocoding, reverse geocoding, postal-code lookup, and free-form address parsing. Pay-per-call HTTP API using

        MAMETA · q 76%
      

Japan Transit API

Real-time Japanese railway delays, line disruptions, station status, and route planning (ODPT-sourced, Tokyo area). Pay-per-call HTTP API us

        MAMETA · q 76%
      

Japan Holiday API

Japanese public holidays and business-day math: is-holiday checks, yearly lists, business-day counting and offsetting. Pay-per-call HTTP API

        MAMETA · q 76%
      

weather.hugen.tokyo

Pay-per-call weather API: given a city name or coordinates it returns current conditions and daily forecasts up to 7 days as structured JSON

        weather.hugen.tokyo · q 100%
      

Japan Furigana API

Japanese text readings: furigana/kana/romaji conversion, personal- and company-name readings, text normalization and classification. Pay-per

        MAMETA · q 76%
      

Japan Diet API

Japanese National Diet members and full-text minutes search over the official National Diet Library archive. Pay-per-call HTTP API using the

        MAMETA · q 76%
      

Embed your Agenstry badge

Paste any of these into your README, agent card, or marketing page. Each badge auto-updates and links back to this page.

Markdown / HTML snippets

[![Agenstry grade](https://agenstry.com/badge/weather.agentic-jp.com.svg)](https://agenstry.com/agents/weather.agentic-jp.com)
[![Verified Business](https://agenstry.com/badge/weather.agentic-jp.com/identity.svg)](https://agenstry.com/agents/weather.agentic-jp.com)
[![Uptime](https://agenstry.com/badge/weather.agentic-jp.com/uptime.svg)](https://agenstry.com/agents/weather.agentic-jp.com)
[![A2A version](https://agenstry.com/badge/weather.agentic-jp.com/protocol.svg)](https://agenstry.com/agents/weather.agentic-jp.com)

Audit-grade evidence bundle

JSON snapshot for vendor-review files. Add ?sign=true for a JWS-signed envelope verifiable against our JWKS. See the methodology.

audit.json audit.json (JWS-signed) verification history

Raw agent card JSON

{
  "name": "Japan Weather API",
  "description": "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) \u2014 no API key or signup. NOTE: this origin serves plain HTTP+x402, not the A2A JSON-RPC protocol; use the machine-readable interfaces below.",
  "url": "https://weather.agentic-jp.com/",
  "version": "1.0.0",
  "provider": {
    "organization": "MAMETA",
    "url": "https://agentic-jp.com/"
  },
  "documentationUrl": "https://weather.agentic-jp.com/llms.txt",
  "interfaces": {
    "x402_manifest": "https://weather.agentic-jp.com/.well-known/x402",
    "openapi": "https://weather.agentic-jp.com/openapi.json",
    "skill_guide": "https://weather.agentic-jp.com/.well-known/skill.md",
    "mcp": "npx -y @mameta/japan-data-mcp"
  },
  "capabilities": {
    "a2a": false,
    "protocol": "http+x402"
  },
  "skills": [
    {
      "id": "weather-forecast",
      "name": "weather forecast"
    },
    {
      "id": "weather-warnings",
      "name": "weather warnings"
    }
  ]
}

Activity (audit trail)

Card history

Endpoints

Skills · 2 declared by this agent

Health · last 30 probes

Who's calling this agent 30d

Similar agents embedding-nearest

Embed your Agenstry badge

Audit-grade evidence bundle

Cookies on Agenstry