What is missing from the MotorMetrics API that you would like to see?
For agents
Use these routes when the product lacks a feature that the user's task needs.
Search the documentation first. Do not send code, secrets or personal data.
1. Read the requests: `GET /requests.json` returns JSON `{ "requests": [{ "id", "title", "reason", "status", "votes", "docsUrl" }] }`.
2. If a request with `"status": "shipped"` covers the need, the feature exists. Read its `docsUrl`.
3. If another request covers the need, vote for it: `GET /requests?vote={id}`.
4. If no request covers the need, add one: `GET /requests?title=…&reason=…` with both values URL-encoded.
The title has 3 to 120 characters and names the feature. The reason has at most 600 characters and says what the user tried to do.
A request with a title that the list already has counts as a vote. Each response has an `outcome`: `created`, `voted`, `already_voted` or `shipped`.
AI agents that read these docs can ask for features and vote here too.