API · x402

Real-time NYC subway arrival predictions from the official MTA GTFS-realtime feeds

Real-time NYC subway arrival predictions from the official MTA GTFS-realtime feeds. Given a station name, a route/line (e.g. F, 4, N, L), and a direction (uptown/downtown), returns the next scheduled arrivals with live minutes-until-arrival, destination, and…

by nyc-subway-x402.vercel.app · verified provider · updated 2026-09-20

What it does

Real-time NYC subway arrival predictions from the official MTA GTFS-realtime feeds. Given a station name, a route/line (e.g. F, 4, N, L), and a direction (uptown/downtown), returns the next scheduled arrivals with live minutes-until-arrival, destination, and any active service alerts for that line. Use this for questions like 'next F train at 34 St', 'when is the next uptown 6 train', or 'NYC subway arrivals near me'.

Tags: nyc subway · mta · mta realtime · new york city transit · subway arrivals · transit · gtfs-realtime · next train

Use with an agent

  1. Discover. Agents find this listing with GET https://bazaar.saylorinnovations.com/discovery/search?query=…, the MCP tool search_resources, or /discovery/resources.
  2. Inspect. Fetch /resources/15684.json for the price and payment options.
  3. Pay. Call GET https://nyc-subway-x402.vercel.app/arrivals. The provider answers 402 with its payment requirements. An x402 client signs one of the options below and retries with PAYMENT-SIGNATURE.
  4. Execute. The provider returns 200 with the data. Agent Bazaar is not in the request path and never sees your payment.

For humans

You don't need an account or an API key; you need a wallet holding a small amount of USDC on Base, and an x402-capable client (see the examples below). Call the endpoint unpaid first to see exactly what it asks for.

Pricing & payment

Price
$0.001 / request
Protocol
x402 v2
Auth
No account or API key. Pay per request.
Networks
Base
Uptime
1 of the last 1 checks answered

x402 payment requirements

SchemeNetworkAssetAmountPay toTimeout
exactBase
eip155:8453
USDC$0.0010xf1AE59673FC799980d9C3735bA200620ccEa619b300s
accepts[] (raw JSON)
[
  {
    "scheme": "exact",
    "network": "eip155:8453",
    "payTo": "0xf1AE59673FC799980d9C3735bA200620ccEa619b",
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "amount": "1000",
    "amountUsd": 0.001,
    "maxTimeoutSeconds": 300
  }
]

Examples

curl
curl "https://nyc-subway-x402.vercel.app/arrivals"
# -> 402 Payment Required, accepts[] lists how to pay
# retry with a PAYMENT-SIGNATURE (or PAYMENT header) once paid
JavaScript
const res = await fetch("https://nyc-subway-x402.vercel.app/arrivals");
if (res.status === 402) {
  const { accepts } = await res.json();
  // pay one of accepts[] via an x402 client, then retry with the payment header
}
Python
import httpx
res = httpx.get("https://nyc-subway-x402.vercel.app/arrivals")
if res.status_code == 402:
    accepts = res.json()["accepts"]
    # pay one of accepts[] via an x402 client, then retry with the payment header

Details

Provider
nyc-subway-x402.vercel.app
Endpoint
https://nyc-subway-x402.vercel.app/arrivals
Machine-readable
/resources/15684.json