The geo API directory contains very different services: geocoding, reverse geocoding, IP location, routing, and boundaries are not interchangeable. Define the user-facing task before comparing providers.
Test set
- Use representative rural, urban, international, and ambiguous addresses; include non-Latin text where relevant.
- For geocoding, record the returned coordinates, confidence, and whether a match is rooftop, street, or approximate.
- For routing, compare travel mode, restrictions, ETA, and coverage—not just a displayed line.
- Check retention, consent, and whether personal location is sent to a third party.
- Verify quotas, attribution, caching rules, and what the interface does when the provider is unavailable.
Never silently treat an approximate IP-derived location as a precise address. Show uncertainty to the user and offer a manual correction path.
Akousa