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.

Listed price
$0.001
Challenge detected
1 of the last check
Median response
1841 ms
Last checked
14 Oct, 21:21 UTC
In our index since
14 Oct 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.

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

Recent checks

14 Oct 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.14 Oct 2026
All 1 checks
When (UTC)ResultHTTPResponse
14 Oct, 21:21 UTCChallenge detected4021841ms

Questions

Did our last probe detect a payment challenge?

At our last probe on 14 Oct, 21:21 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 14 Oct 2026.

Something wrong on this page? Tell us.