- Maximize input data. The more context the engine receives (postal code, city, street), the higher the match accuracy.
- Structure your inputs. Submit distinct components (structured JSON) rather than a single string to improve parsing accuracy.
- Trust the normalizer. Don't pre-clean addresses before sending them. Pre-normalizing can lose information during geocoding.
- Privacy first. Remove personal identifiers before submission. The system filters this data, but cleaner inputs ensure stricter GDPR compliance.
- Performance tuning. Parallelize requests to maximize throughput, but avoid excessive bursts. Client-side rate limiting is not currently enforced.
- Quality monitoring: track the accuracy score and
attribute_scoresin the response. - Operational health: set alerts for API latency and HTTP response codes.
- Baseline testing: validate against a known set of addresses to establish a performance baseline.
No relevance score is returned between the request and response address.
The service does not validate whether the input is a potentially valid address.
Forward geocoding only (address to coordinates). Reverse geocoding is not supported.
Available for 55 countries. See Supported Countries.
The last-meter layer (entrances, parking, handover) is available only within the Bettermile suite, not through the standalone API.