Japan Transit API
Real-time train delays + delay-aware alternative routes for Japan rail. x402-enabled for AI agents. Data: x402-list.com (CC BY 4.0)
Listed · $0.001–$0.015 USDC/request · 5 endpoints · Tools · base network · x402 protocol
Networks: Base (accepted)
Discovery is free. Agents search the catalogue here. Payment happens on the listing 402, not on PayAPI.
url https://payapi.market/mcpListing facts
- Provider
- Unclaimed
- Hosted at
transit.agentic-jp.com- Category
- Tools
- Price
- $0.001 to $0.015 USDC per request
- Endpoints
- 5
- Payment networks
- Base
- Settlement-verified
- Not yet. Listed, not paid for by PayAPI Market.
- Listed on PayAPI Market
- 2026-10-30
About this API
Japan Transit API is listed in the Tools category with pricing at $0.001–$0.015 USDC/request.
Payments settle on base in USDC via the x402 protocol. AI agents discover this API through the PayAPI Market MCP server and pay per request without API keys or accounts.
This API exposes 5 endpoints.
Add this badge to your README
Paste this on your site. The link points at this listing. Listing is free and providers keep 100%.
Markdown
[](https://payapi.market/api/japan-transit-api)
HTML
<a href="https://payapi.market/api/japan-transit-api"><img src="https://payapi.market/badge/japan-transit-api.svg" alt="Listed on PayAPI Market" height="20"></a>
Questions about this API
What does Japan Transit API do?
Real-time train delays + delay-aware alternative routes for Japan rail. x402-enabled for AI agents. Data: x402-list.com (CC BY 4.0) It is provided by Unclaimed.
How much does Japan Transit API cost?
Japan Transit API is priced at $0.001 to $0.015 USDC per request, paid per call with no subscription. The exact amount for each call is in the HTTP 402 response before any money moves.
Do I need an API key or account to use Japan Transit API?
No. Japan Transit API uses the x402 protocol, so an agent pays per request in USDC on Base and gets the response, with no API key, account or signup.
Has Japan Transit API been verified?
Not yet. Japan Transit API is listed and answers an x402 payment challenge, but PayAPI Market has not paid for a call to it, so it carries no settlement-verified badge.
How does an AI agent find Japan Transit API?
Through the free PayAPI Market MCP server at https://payapi.market/mcp, using search_apis or get_api, or over plain HTTP at https://payapi.market/agent/search. Discovery is free; the agent pays the provider directly on the listing's own 402.
More Tools APIs · Browse the marketplace · List your own API
Related APIs
- NO HANDS AI Merchant Check · 1 route verified · Deterministic merchant policy evaluation for API purchases. Returns an advisory decision and reason codes. Not identity verification or payment authorization.
- Klowor Web Brief · 1 route verified · Fetch a public HTTP(S) web page and return a structured extractive brief: title, description, headings, key points, a text digest and content statistics. Public pages only.
- Vennatta Document Extraction · 1 route verified · Extract structured text, summaries, or metadata from supplied text or a public HTTPS document URL. Agent-facing x402 API.
- USDC decimal <-> atomic (6 dp) converter for x402 amounts with native USDC · 1 route verified · USDC decimal <-> atomic (6 dp) converter for x402 amounts with native USDC address, EIP-55 checksum and EIP-712 domain per chain. Pure compute.
- FreelanceDesk Invoicing API · 2 of 5 routes verified · Validate invoice JSON ($0.05); get a print-ready A4 invoice as PDF or self-contained HTML ($0.10). Also the offline invoicing app and document pack as zip ($14/$7). USDC on Base, no key.
- Agent Extraction API: Named entity extraction · 1 route verified · Named entity extraction: people, organizations, locations, dates, money amounts and products from text (max 6,000 chars)
More from Unclaimed
- Japan Corporate-Number (法人番号) API
- Japan Holiday & Business-Day API
- Japan Weather Forecast & Warnings API
- Japan Diet API
- Japan Address API
- View all from Unclaimed
By Unclaimed