# Japan Transit API

> Real-time Tokyo-area train delays, disruptions, route planning (ODPT data). Pay per call with USDC via the x402 protocol (HTTP 402) on Base, Polygon, or Solana. No API key, no signup: call any endpoint, read the payment instructions from the 402 response, pay, retry. Facilitator: Coinbase CDP.

## Endpoints
- GET /station/{name}/status ($0.005) — real-time delays, poll-friendly
- GET /line/{line}/disruptions ($0.005)
- POST /route-plan ($0.01)
- POST /alternative-routes ($0.015) — delay-aware
- GET /alerts/feed ($0.005) — poll for current alerts
- GET /lines ($0.001)
- GET /stations/search ($0.005)

## Machine-readable docs
- [x402 manifest with schemas and examples](https://transit.agentic-jp.com/.well-known/x402)
- [OpenAPI 3.1](https://transit.agentic-jp.com/openapi.json)
- [Agent skill guide](https://transit.agentic-jp.com/.well-known/skill.md)

## How to pay
Any x402 client works: @x402/fetch or @x402/axios (npm), x402 (pip), Coinbase AgentKit, `npx agentcash`. MCP server for all 7 Japan Data APIs: `npx -y @mameta/japan-data-mcp`.

## All Japan Data APIs
- [Directory of all 8 services](https://agentic-jp.com/) · [services.json](https://agentic-jp.com/services.json)