Plan a route between two Japanese (JP) train stations — timetable-based, with transfers, duration, and fare. Standard planning without delay adjustment (cheaper). Use for ordinary trip planning.
POST https://transit.agentic-jp.com/route-planListed in 3 directories: bazaar, x402-list, x402-new. First seen 5 Sept 2026.
The endpoint answers an unpaid request with an HTTP 402 and a payment challenge. @x402/fetch signs it, pays in USDC, and retries — you get the result back in one call.
import { wrapFetchWithPayment } from "@x402/fetch";
import { privateKeyToAccount } from "viem/accounts";
const account = privateKeyToAccount(process.env.PRIVATE_KEY);
const pay = wrapFetchWithPayment(fetch, account);
const res = await pay("https://transit.agentic-jp.com/route-plan", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({ /* see the 402 challenge for the shape */ }),
});
console.log(await res.json());transit.agentic-jp.com
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.
BaseEverything elseAtransit.agentic-jp.com
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.
BaseNews & contentAtransit.agentic-jp.com
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.
BaseSearch & webAUptime and compliance: x402-list.com (CC BY 4.0). Safety scores: x402.direct. Call and payer counts: x402.new. AMNT indexes this endpoint and does not host, operate or vouch for it.