Request a feature
POST /v1/feedback/featuresFreeWrites
Files a feature request on the public board and upvotes it for you. Use it when the human wants something the API cannot do yet (a boundary type, export format, op or option). Check list_feedback first and upvote an existing request instead of filing a duplicate. Free; needs a key; 10 new items per account a day. Returns the item and similar existing requests. Everything on the board is public (never the author's email). Do not include API keys, personal data or customer data.
MCP tool request_feature · CLI geocode request-feature · RPC POST /v1/ops/request_feature
Input
| Field | Type | Description |
|---|---|---|
titlebody, required | string | What you want, in one line. |
detailsbody | string | Why you need it and what you are building; concrete examples help it get planned. Default "". |
Example request
curl -X POST "https://geo-coder-service.vercel.app/v1/feedback/features" \ -H "Authorization: Bearer $GEOCODE_API_KEY" \ -H "Content-Type: application/json" \ -d '{"title":"Export boundaries as Shapefile","details":"Our GIS team imports zones into ArcGIS, which wants .shp."}'Example response
See the description above for what this returns.
Errors
Failures are RFC 9457 problems. Common ones here: 400 invalid_input, 401 unauthorized, 429 rate_limited.