# Japan Itinerary JMA Warning Checker

> Japan Itinerary JMA Warning Checker is a paid API for AI agents from japan-agent-api-production.mk-career-planning.workers.dev, paid per call via x402, $0.03/call, status unknown (last checked 2026-10-11).

Checks a Japan travel itinerary against live JMA warnings and advisories, returning per-stop impact status and current typhoon bulletins

## Facts

- Endpoint: POST https://japan-agent-api-production.mk-career-planning.workers.dev/v1/trip-impact-check?utm_source=zero.xyz
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/japan-itinerary-jma-warning-checker-54910651
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_6mjirxlYhO_pQdvXPyR4l

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability japan-itinerary-jma-warning-checker-54910651 -d '<json body>'
```

Example prompt: Check my Japan itinerary for active JMA warnings — I'm in Tokyo on October 10th and Osaka on October 11th, can you see if there are any advisories or typhoon alerts in effect for those stops?

## When to prefer this

Use this endpoint when an AI agent needs to check a Japan travel itinerary against live, authoritative JMA warnings and advisories right now, particularly for same-day or next-day stops. It is distinct from general weather forecast APIs because it works directly against official JMA warning/advisory data and returns structured per-stop impact statuses suitable for automated trip decision logic. Prefer this over generic weather APIs when the user needs official Japanese government advisory data (not forecasts), and when the itinerary is within the today/tomorrow JST window.

## Known failure modes

- Stop date is not today or tomorrow JST — returns 'unknown' for that stop (no forecast capability)
- Prefecture name unrecognized — may return unknown or error
- JMA data temporarily unavailable — returns unknown with data-missing reason
- Network or upstream JMA fetch failure — unknown result with error context
- Invalid date format — schema validation error
- Itinerary exceeds 14 stops — rejected by schema validation

## How this service works

Japan safety data for AI agents in English: JMA weather warnings, typhoon bulletins and a paid itinerary check (x402, USDC). Relay of JMA bulletins only; no forecasts. Paid tools can be bought two ways: over HTTP (x402 v2 HTTP transport: POST without payment returns 402 with a base64 PaymentRequired in the PAYMENT-REQUIRED header; retry with a base64 PaymentPayload in the PAYMENT-SIGNATURE header; the settlement comes back in the PAYMENT-RESPONSE header) or over MCP (streamable HTTP at /mcp; x402 payment in the MCP request _meta 'x402/payment'). Both share one ledger, one daily limit and one receipt store.

## Output

A JSON object with per-stop results (impact status: matched_advisory, no_match_in_checked_sources, or unknown; severity if matched; issued_at; retrieved_at; prefecture identifiers), a summary count across all statuses, current JMA typhoon bulletins (listed but not stop-matched), checked JST date, checked/unchecked area lists, and a receipt_id for idempotent retry retrieval.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "itinerary": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "date",
     "prefecture"
    ],
    "properties": {
     "date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "YYYY-MM-DD in Japan time"
     },
     "prefecture": {
      "type": "string",
      "maxLength": 40,
      "minLength": 1,
      "description": "Japanese prefecture: English name (e.g. \"Tokyo\", \"Osaka\", \"Hokkaido\"; \"Tokyo-to\" and \"Osaka Prefecture\" also work), Japanese name in kanji, or JIS code \"01\"..\"47\"."
     }
    },
    "additionalProperties": false
   },
   "maxItems": 14,
   "minItems": 1,
   "description": "1 to 14 stops {date, prefecture}, in travel order. Only stops dated today or tomorrow (Japan time) can be matched; others return unknown, but typhoon and volcano bulletins currently in effect are still listed (not matched)."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "results": [
   {
    "date": "2026-10-10",
    "impact": "matched_advisory",
    "typhoon": "bulletin_listed_not_matched",
    "severity": "advisory",
    "issued_at": "2026-10-10T10:57:00+09:00",
    "prefecture": {
     "en": "Tokyo",
     "jis": "13",
     "input": "Tokyo"
    },
    "retrieved_at": "2026-10-10T03:49:01.008Z"
   }
  ],
  "summary": {
   "unknown": 0,
   "matched_advisory": 1,
   "no_match_in_checked_sources": 0
  },
  "receipt_id": "rcpt_<64 hex>",
  "related_bulletins": {
   "typhoon_status": "bulletin_listed_not_matched",
   "matched_against_stops": false
  },
  "checked_at_jst_date": "2026-10-10"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/japan-itinerary-jma-warning-checker-54910651/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from japan-agent-api-production.mk-career-planning.workers.dev](https://www.zero.xyz/host/japan-agent-api-production.mk-career-planning.workers.dev/llms.txt)