Japan Transit API

Endpoints (6 live)

• GET /stations/search — Fuzzy-search Japanese (JP) train stations by name — accepts kanji, kana, or romaji and tolerates the 駅/station suffix. Returns matching stations with their operators and lines. Use to resolve a station name to a canonical record. (0.005 USDC on Solana)
• GET /alerts/feed — Live feed of every active rail disruption across the Japanese (JP) network in one call — delays and suspensions with bilingual summaries, refreshed continuously from ODPT. Built for MONITORING agents: poll on an interval (e.g. every 5 minutes) to maintain a nationwide incident watchlist without querying stations one by one. (0.005 USDC on Solana)
• GET /lines — Directory of Japanese (JP) rail operators and their lines, with canonical ids and Japanese/English names. Use to discover valid line and operator identifiers for the other endpoints. (0.001 USDC on Base)
• POST /route-plan — Generates transit route plans for a requested journey. (0.01 USDC on Solana)
• GET /line/1/disruptions — Current service disruptions on a specific Japanese (JP) train line: status, estimated delay, cause, and last-updated time, with a bilingual summary. Sourced live from ODPT. Use to monitor one line for delays or suspensions. (0.005 USDC on Solana)
• POST /alternative-routes — Suggest delay-aware alternative routes for Japanese (JP) train travel: returns the primary route plus ranked alternatives that route around currently-disrupted lines, each with a reason. The differentiating endpoint — use when trains are delayed and the agent needs a route that still works. (0.015 USDC on Base)