← REST APIREST endpoint

Where is this place?

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

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

The problem this solves.

Almost every spatial workflow starts with a string and needs coordinates. geocode resolves a single place to a lat/lon plus structured address components. Use it before routing, plotting, or feeding any downstream geospatial logic.

What it does for you

What comes back in the response.

  • Ranked candidates with confidence scores per result.
  • Structured address components (street, locality, postcode, country) on each match.
  • Multilingual place name handling.
  • Pair with parse_address upstream on messy free-text input to lift match rates.
  • Standard GET + query params. Use from any HTTP client.
Built for
For AI developersFor 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/search
curl "https://api.footstep.ai/v1/geocoding/search" \
  -H "x-api-key: sk_live_your_key_here"

Related capabilities.

reverse_geocode

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

search_places

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

parse_address

Free-text in, structured out. Fixes typos, expands abbreviations, infers missing fields, and scores confidence.

Ready to call it?

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

Get an API keySee the MCP tool