# Japan Transit Line Disruptions API

> Japan Transit Line Disruptions API is a paid API for AI agents from transit.agentic-jp.com, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-15).

Returns current service disruptions for a specific Japanese train line, including status, estimated delay, cause, and last-updated time with bilingual (Japanese/English) summary sourced live from ODPT.

## Facts

- Endpoint: GET https://transit.agentic-jp.com/line/:line/disruptions
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/japan-transit-line-disruptions-api-76b70abb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_-m7-i-K8a4ruDUDBBILEB

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-transit-line-disruptions-api-76b70abb
```

Example prompt: Can you check if there are any current delays or suspensions on the Yamanote line right now, and tell me the cause and how long it's been since the status was last updated?

## When to prefer this

Use this endpoint when you need disruption data for a single specific Japanese train line rather than the entire network. It is more efficient than the full-network feed when monitoring or alerting on one line, and provides structured bilingual output suitable for both Japanese and English-language applications. Prefer this over the station-status endpoint when the user's concern is about a line-wide disruption rather than conditions at a specific station.

## Known failure modes

- Invalid or unrecognized line ID returns a 404 or error response
- Line ID uses wrong canonical format — must match ODPT operator:line naming convention
- ODPT upstream data unavailable causing stale or empty response
- Line currently has no disruptions — returns normal status with no delay data
- Rate limiting or payment failure via x402 protocol blocking the request

## How this service works

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.

## Output

Returns the current disruption status for the requested line (e.g. normal, delayed, suspended), the estimated delay duration, the cause of the disruption (e.g. signal failure, passenger incident), the last-updated timestamp, and a bilingual Japanese/English summary of the situation.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/japan-transit-line-disruptions-api-76b70abb/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from transit.agentic-jp.com](https://www.zero.xyz/host/transit.agentic-jp.com/llms.txt)