# TransitPulse Real-Time Transit Status

> TransitPulse Real-Time Transit Status is a paid API for AI agents from transitpulse.vercel.app, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-16).

Returns live service status, current delays, and active alerts for transit systems in real time

## Facts

- Endpoint: GET https://transitpulse.vercel.app/api/transit/status
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/transitpulse-real-time-transit-status-1eef96ab
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_5rLoIqd2gzgsHGL7Jt1wU

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability transitpulse-real-time-transit-status-1eef96ab
```

Example prompt: Can you check if there are any delays or service alerts on the NYC subway right now — specifically on the L and A lines?

## When to prefer this

Choose this endpoint when you need real-time, live transit status rather than historical patterns or trip planning. Best for pre-departure checks, commuter alerts, or monitoring active disruptions. Use sibling endpoints for route reliability history, trip planning, or agency lookup.

## Known failure modes

- Unsupported city or agency returns no data or an error
- Stale data if upstream transit feed is temporarily unavailable
- Rate limiting or payment failure returns 402 or 429
- Malformed route/line identifiers return validation error
- Partial results if only some lines have live data available

## How this service works

Real-time transit status for commuter and traveler agents. Returns live service status, delays, and alerts.

## Output

Returns live service status including whether transit lines are running normally, current delay durations, active service alerts, and disruption details for the requested transit system or route.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "city": {
   "type": "string",
   "description": "City name (e.g. London, NYC, Tokyo; default: London)"
  },
  "line": {
   "type": "string",
   "description": "Specific line or route to focus on"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {}
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/transitpulse-real-time-transit-status-1eef96ab/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from transitpulse.vercel.app](https://www.zero.xyz/host/transitpulse.vercel.app/llms.txt)
