# TransitPulse Historical Delay Patterns API

> TransitPulse Historical Delay Patterns API is a paid API for AI agents from transitpulse.theaslangroupllc.com, paid per call via x402, $0.08/call, status unknown (last checked 2026-09-15).

Returns historical transit delay patterns and reliability trends over time for a given transit system or route

## Facts

- Endpoint: GET https://transitpulse.theaslangroupllc.com/api/transit/delays-history
- Price: $0.08/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/transitpulse-historical-delay-patterns-api-841874bc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_zKl5FVheezV-PLp6xzZZ-

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-historical-delay-patterns-api-841874bc
```

Example prompt: Can you pull up the historical delay patterns and reliability trends for the Chicago L Red Line over the past 12 months so I can see how often it runs late and when delays tend to be worst?

## When to prefer this

Use this endpoint when you need historical/trend data on transit reliability rather than live disruptions. Ideal for commute planning research, relocation decisions, or understanding long-term transit performance. Use the sibling 'current delays' endpoint for real-time disruption data instead.

## Known failure modes

- Unknown city or transit system returns 404 or empty result
- Date range too far in the past may return no data
- Unsupported transit mode or line identifier returns error
- Malformed query parameters return 400 bad request
- Payment not processed results in 402 response

## How this service works

Historical transit delay patterns for commuter and transit agents. Returns delay patterns and reliability trends over time.

## Output

Returns historical delay patterns including average delay durations, delay frequency, reliability trends over the requested time period, and potentially peak delay windows or worst-performing routes/times

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "city"
 ],
 "properties": {
  "city": {
   "type": "string",
   "description": "city"
  },
  "line": {
   "type": "string",
   "description": "line"
  }
 }
}
```

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/transitpulse-historical-delay-patterns-api-841874bc/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from transitpulse.theaslangroupllc.com](https://www.zero.xyz/host/transitpulse.theaslangroupllc.com/llms.txt)