REST API for Japanese seasonal data. 57 JMA stations, 73 years of cherry blossom records, real-time autumn foliage tracking, and 200+ curated festivals with GPS coordinates. MCP server included — works with Claude, GPT, and any MCP-compatible AI agent out of the box. First API to support x402 protocol: AI agents pay per request with USDC on Base. No API key needed. HTTP 402 tells the price, agent pays, data flows back. Free (100 req/day) · Pro $9.99/mo · Pay-as-you-go $0.001/req · x402 USDC
No reviews yetBe the first to leave a review for Japan Seasons API
Maker
📌
Hey everyone! 👋
I built Japan Seasons API because I kept running into the same problem — building apps related to Japan travel and there was no single, reliable API for cherry blossom forecasts, autumn foliage status, or festival schedules. The data exists across dozens of Japanese government sites, but it's all in Japanese HTML pages with no API access.
So I scraped 73 years of JMA observation data from 57 stations, built an AI-powered forecast model, and curated 200+ festivals with GPS coordinates.
What I'm most excited about is the x402 integration. If you haven't heard of it — x402 is a new protocol that lets AI agents pay for API access using USDC stablecoin, with no API key or account needed. When an agent hits an endpoint without auth, it gets back HTTP 402 with the price and payment details. The agent pays, and data flows back. It's like a native paywall for the AI agent economy.
Here's what's available:
- 🌸 /v1/sakura — bloom forecasts, historical data, recommendations
- 🍁 /v1/kouyou — autumn foliage tracking
- 🏮 /v1/matsuri — festival search with dates and locations
- 🤖 MCP server — plug into Claude or GPT directly
Free tier gives you 100 requests/day. Pro is $9.99/mo. Or just pay per request — $0.001 via Stripe or USDC micropayments.
Would love to hear your feedback, especially from anyone building AI agents or Japan-related apps. What endpoints would you want to see next?