Discover / transit.agentic-jp.com

Japan Transit API

■ Challenge detected

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.

x402
Base
Polygon
Solana
USDC
Data

Listed price: $0.001
Challenge detected: 10 of the last 10 checks
Median response: 694 ms
Last checked: 17 Oct, 09:26 UTC
In our index since: 26 Sept 2026

Endpoint

curl -i https://transit.agentic-jp.com/lines
# 402 Payment Required: pay with an x402 client (USDC on Base),
# then send the same request again with the payment attached.

3 listed endpoints · on x402 Bazaar

Checks and payment terms on this page refer to the endpoint above. Other listed endpoints have not been checked individually.

Base URLhttps://transit.agentic-jp.com

GET/lines$0.001Directory 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.
GET/stations/search$0.005Fuzzy-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.
GET/alerts/feed$0.005Live 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.

A dash means the listing gives no price or method. Copy buttons copy the full URL.

Showing 3 of 3 listed endpoints.

Agents can find it through the Superstables MCP server and JSON API: GET /api/v1/services/transit.agentic-jp.com

Recent checks

29 Sept 2026One bar per check, showing up to 20 recent checks. Coloured bars show relative response time, with a minimum visible height; full-height grey bars mean no challenge was detected. “Challenge detected” means HTTP 402 or another detected payment-challenge signal.17 Oct 2026

All 10 checks

When (UTC)	Result	HTTP	Response
17 Oct, 09:26 UTC	Challenge detected	402	837ms
16 Oct, 08:13 UTC	Challenge detected	402	579ms
14 Oct, 23:56 UTC	Challenge detected	402	816ms
13 Oct, 10:39 UTC	Challenge detected	402	690ms
11 Oct, 10:02 UTC	Challenge detected	402	618ms
9 Oct, 21:31 UTC	Challenge detected	402	1054ms
8 Oct, 18:39 UTC	Challenge detected	402	626ms
7 Oct, 15:42 UTC	Challenge detected	402	698ms
6 Oct, 15:31 UTC	Challenge detected	402	613ms
29 Sept, 17:03 UTC	Challenge detected	402	1215ms

Questions

Did our last probe detect a payment challenge?

At our last probe on 17 Oct, 09:26 UTC, it returned HTTP 402 or another detected payment-challenge signal. This check did not test payment, delivery or compatibility with the Superstables client.

What price is recorded for Japan Transit API?

Its listed price is $0.001.

What payment terms does Japan Transit API advertise?

The listing advertises x402, Base, Polygon, Solana and USDC. It names cdp as its facilitator. Check the seller's current payment challenge and authentication requirements before paying.

Where is Japan Transit API listed?

In x402 Bazaar and x402-list.com. Superstables first indexed it on 26 Sept 2026.

Something wrong on this page? Tell us.