Points in boundary
POST /v1/boundaries/{id}/contains1 unit per 1,000 points (up to 10,000 per call)Read-only
Tests up to 10,000 points ([lon, lat] pairs) against one boundary and returns a boolean per point plus the inside count. Use it for geofencing, service-area checks and filtering customer lists. Costs 1 unit per 1,000 points.
MCP tool contains_points · CLI geocode contains-points · RPC POST /v1/ops/contains_points
Input
| Field | Type | Description |
|---|---|---|
idpath, required | string | Boundary id: r<OSM relation id> (e.g. r62422 for Berlin) or w<way id>. Also accepts R62422, relation/62422, -62422, an openstreetmap.org URL, wikidata:Q64 or iso:US-CA. |
pointsbody, required | array of [lon, lat] | Points as [lon, lat] (GeoJSON order). |
Example request
curl -X POST "https://geo-coder-service.vercel.app/v1/boundaries/r62422/contains" \ -H "Authorization: Bearer $GEOCODE_API_KEY" \ -H "Content-Type: application/json" \ -d '{"points":[[13.405,52.52],[2.35,48.86]]}'Example response
Errors
Failures are RFC 9457 problems. Common ones here: 400 invalid_input, 401 unauthorized, 402 quota_exceeded, 429 rate_limited.