This is an API for accessing information about bicycling related incidents. You can find the source code on GitHub .
About the BikeWise API v2 API
BikeWise API v2 API on Apizie: 4 endpoints (Paginated incidents matching parameters, GET /v2/incidents/{id}, Unpaginated geojson response, Unpaginated geojson response with simplestyled markers) returned as clean JSON through one API key. 4 endpoints are live now. Call it over REST at https://zieapi.vercel.app/v1/open-data:bikewise/{endpoint} or from Claude, ChatGPT and Cursor through the Apizie MCP server. Free plan: 1,000 requests a month.
| Project key | open-data:bikewise |
|---|---|
| Status | Live |
| Endpoints | 4 |
| Category | Open Data |
| Source | bikewise.org |
| Base URL | https://zieapi.vercel.app/v1/open-data:bikewise/{endpoint} |
| For AI tools | OpenAPI spec · Markdown (what is this?) |
BikeWise API v2 API FAQ
How do I call the BikeWise API v2 API?
Create a free Apizie key, then send GET https://zieapi.vercel.app/v1/open-data:bikewise/get-version-incidents-format with the header x-api-key. Every endpoint returns { project, data, timestamp }.
Is the BikeWise API v2 API free on Apizie?
Yes. The Free plan includes 1,000 requests a month at 100 requests a minute, no credit card.
Can AI agents use the BikeWise API v2 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 open-data:bikewise.
What is the status of the BikeWise API v2 API?
Live: works with just an Apizie key