Rail, bus, and elevator disruptions/outages.
About the Incidents API
Incidents API on Apizie: 6 endpoints (XML - Bus Incidents, XML - Elevator/Escalator Outages, XML - Rail Incidents, JSON - Bus Incidents, …) returned as clean JSON through one API key. Send your own provider key in the x-upstream-key header. Call it over REST at https://apizie.tech/v1/transport:wmata-incidents/{endpoint} or from Claude, ChatGPT and Cursor through the Apizie MCP server. Free plan: 1,000 requests a month.
| Project key | transport:wmata-incidents |
|---|---|
| Status | Your key |
| Endpoints | 6 |
| Category | Transport |
| Source | wmata.com |
| Base URL | https://apizie.tech/v1/transport:wmata-incidents/{endpoint} |
| For AI tools | OpenAPI spec · Markdown (what is this?) |
Incidents API FAQ
How do I call the Incidents API?
Create a free Apizie key, then send GET https://apizie.tech/v1/transport:wmata-incidents/54763641281d830c946a3d78 with the header x-api-key. Every endpoint returns { project, data, timestamp }.
Is the Incidents API free on Apizie?
Yes. The Free plan includes 1,000 requests a month at 100 requests a minute, no credit card. Incidents itself also needs your own key from wmata.com.
Can AI agents use the Incidents API?
Yes. Add the Apizie MCP server (https://apizie.tech/mcp) to Claude, ChatGPT, Cursor or VS Code, then ask in plain language. The agent calls run_scraper with project key transport:wmata-incidents.
What is the status of the Incidents API?
Needs your own provider key (bring your own key)