List feature requests and issues
GET /v1/feedbackFreeNo key neededRead-only
The public feedback board: feature requests and issue reports with their status and upvotes, most upvoted first. Free and needs no key (with a key, each item says whether you voted). Call it before request_feature or report_issue to find an existing item to upvote instead of filing a duplicate, or when the human asks what is planned.
MCP tool list_feedback · CLI geocode list-feedback · RPC POST /v1/ops/list_feedback
Input
| Field | Type | Description |
|---|---|---|
kindquery | "feature" | "issue" | "all" | feature = feature requests, issue = bug reports. Default "all". |
statusquery | "active" | "all" | "open" | "planned" | "in_progress" | "done" | "declined" | "duplicate" | active = open, planned or in progress. Default "active". |
sortquery | "top" | "new" | top = most upvoted, new = most recent. Default "top". |
qquery | string | Words to find in the title. |
minequery | boolean | "true" | "false" | Only items you filed (needs a key). |
limitquery | integer | Page size, at most 100. Default 20. |
offsetquery | integer | Default 0. |
Example request
curl "https://geo-coder-service.vercel.app/v1/feedback?kind=feature&q=postcode"Example response
See the description above for what this returns.
Errors
Failures are RFC 9457 problems. Common ones here: 400 invalid_input, 429 rate_limited.