# StatePulse Transit Status

> StatePulse Transit Status is a paid API for AI agents from statepulse-api.hahavoid0.workers.dev, paid per call via x402, $0.03/call, status unknown (last checked 2026-09-15).

Returns real-time service status, delays, and alerts for a given city transit line

## Facts

- Endpoint: POST https://statepulse-api.hahavoid0.workers.dev/transit/status
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/statepulse-transit-status-f1187068
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_bEIPBdFd5jkk336zzp5xU

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 statepulse-transit-status-f1187068 -d '<json body>'
```

Example prompt: Is the L train in NYC running normally right now — any delays or service alerts I should know about?

## When to prefer this

Use this endpoint when an agent needs real-time transit service status for a specific city and line, particularly when no account setup is desirable and pay-per-call USDC micropayment via x402 is acceptable. Best for quick spot-checks of subway or metro line health rather than full route planning.

## Known failure modes

- Unsupported city or transit line returns supported:false with no status data
- Payment failure via x402 results in 402 response before data is returned
- Network or upstream data source outage may return empty or stale results
- Invalid POST body missing city or line parameters may return a 400 error

## How this service works

Live subway alerts, delays, and planned-work advisories from the official MTA GTFS-RT feed for NYC lines. Other cities can be requested via the free /agent/request-data endpoint.

## Output

A JSON object with the city, line name, current status label (e.g. 'Good Service'), a boolean delay flag, an array of active alerts, a supported flag indicating whether that city/line is covered, and a confidence level (e.g. 'medium') for the returned data.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "result": {
   "city": "nyc",
   "line": "L",
   "alerts": [],
   "delays": false,
   "status": "Good Service"
  },
  "supported": true,
  "confidence": "medium"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/statepulse-transit-status-f1187068/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from statepulse-api.hahavoid0.workers.dev](https://www.zero.xyz/host/statepulse-api.hahavoid0.workers.dev/llms.txt)