← REST APIREST endpoint

What's near here?

Points of interest near a location, by category or by venue name. Sorted by distance.

Get an API keySee the MCP tool
GET /v1/geocoding/places
Why you need it

The problem this solves.

Travel apps, dispatch, and field-service workflows all run 'find X near Y' queries. search_places accepts categories or specific venue names and returns ranked results from a single GET. No SDK lock-in, no SDK config, just an HTTP call.

This endpoint bundles Geocoding + Place search in a single call.

What it does for you

What comes back in the response.

  • Categories expand internally to multilingual synonyms.
  • Pass lat+lon directly or 'near' as a place name (auto-geocoded).
  • Sorted by distance with structured place info.
  • Distance and bearing from the search point on each result.
  • Standard GET + query params. Use from any HTTP client.
Built for
For AI developersFor SAR teamsFor integrators
Try it

Call it from your backend.

Predictable HTTP. JSON in, JSON out. One auth header. Use it from any backend, edge function, or script.

Read the full reference
GET /v1/geocoding/places
curl "https://api.footstep.ai/v1/geocoding/places" \
  -H "x-api-key: sk_live_your_key_here"

Related capabilities.

geocode

Turn an address, landmark, or place name into coordinates. Returns ranked candidates with confidence scores.

reverse_geocode

Given a coordinate, return the address or place label. Useful for labelling pins and incident reports.

search_along_route

Coffee, charging, fuel, food. Ranked by how little detour they add to the existing route.

Ready to call it?

£5 free credit on signup. One auth header, every major runtime.

Get an API keySee the MCP tool