Real-time bus prediction methods.
About the Real-Time Bus Predictions API
Real-Time Bus Predictions API on Apizie: 2 endpoints (XML - Next Buses, JSON - Next Buses) 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-bus-realtime/{endpoint} or from Claude, ChatGPT and Cursor through the Apizie MCP server. Free plan: 1,000 requests a month.
| Project key | transport:wmata-bus-realtime |
|---|---|
| Status | Your key |
| Endpoints | 2 |
| Category | Transport |
| Source | wmata.com |
| Base URL | https://apizie.tech/v1/transport:wmata-bus-realtime/{endpoint} |
| For AI tools | OpenAPI spec · Markdown (what is this?) |
Real-Time Bus Predictions API FAQ
How do I call the Real-Time Bus Predictions API?
Create a free Apizie key, then send GET https://apizie.tech/v1/transport:wmata-bus-realtime/5476365e031f5909e4fe331e with the header x-api-key. Every endpoint returns { project, data, timestamp }.
Is the Real-Time Bus Predictions API free on Apizie?
Yes. The Free plan includes 1,000 requests a month at 100 requests a minute, no credit card. Real-Time Bus Predictions itself also needs your own key from wmata.com.
Can AI agents use the Real-Time Bus Predictions 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-bus-realtime.
What is the status of the Real-Time Bus Predictions API?
Needs your own provider key (bring your own key)