Bus stop information, route and schedule data, and bus positions.
About the Bus Route and Stop Methods API
Bus Route and Stop Methods API on Apizie: 12 endpoints (XML - Bus Position, XML - Path Details, XML - Schedule, XML - Routes, …) 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://zieapi.vercel.app/v1/transport:wmata-bus-route/{endpoint} or from Claude, ChatGPT and Cursor through the Apizie MCP server. Free plan: 1,000 requests a month.
| Project key | transport:wmata-bus-route |
|---|---|
| Status | Your key |
| Endpoints | 12 |
| Category | Transport |
| Source | wmata.com |
| Base URL | https://zieapi.vercel.app/v1/transport:wmata-bus-route/{endpoint} |
| For AI tools | OpenAPI spec · Markdown (what is this?) |
Bus Route and Stop Methods API FAQ
How do I call the Bus Route and Stop Methods API?
Create a free Apizie key, then send GET https://zieapi.vercel.app/v1/transport:wmata-bus-route/5476362a281d830c946a3d6e with the header x-api-key. Every endpoint returns { project, data, timestamp }.
Is the Bus Route and Stop Methods API free on Apizie?
Yes. The Free plan includes 1,000 requests a month at 100 requests a minute, no credit card. Bus Route and Stop Methods itself also needs your own key from wmata.com.
Can AI agents use the Bus Route and Stop Methods API?
Yes. Add the Apizie MCP server (https://zieapi.vercel.app/mcp) to Claude, ChatGPT, Cursor or VS Code, then ask in plain language. The agent calls run_scraper with project key transport:wmata-bus-route.
What is the status of the Bus Route and Stop Methods API?
Needs your own provider key (bring your own key)