The case for keeping a public status page honest
A status page that always shows green, even during an outage, is not reassuring at all. It is evidence the page is decorative rather than operational.
Blog topic
Our takes (page 3)
Opinion on the location data business: pricing, lock-in, privacy, and what the big providers get wrong.
Why webhook-only APIs quietly exclude batch users
A webhook works well for one request at a time. It works badly for a script that just wants to send a thousand lookups and wait for a thousand answers.
What coordinate precision marketing gets backwards
A response with fifteen decimal places of latitude looks precise. It is not accurate just because it has more digits than the method can actually support.
Why we publish our error codes instead of hiding them
An undocumented error code turns every failed request into a guessing game. Publishing the list is a small thing that saves real debugging time.
The trouble with data that's accurate on launch day only
A dataset announced with pride and never revisited degrades quietly. Borders shift, postal systems change, and time zone rules get amended by governments that do not send a press release.
Why batch pricing should match single-request pricing
A thousand lookups sent one at a time and a thousand lookups sent as a batch are the same amount of work. The price should not depend on how they were packaged.
What a free tier is actually for
A free tier is not a discount, and it is not bait for a sales call. It is the smallest useful amount of a product a developer needs to find out if it fits.
Why "AI-powered geocoding" claims deserve scrutiny
Calling a lookup AI-powered is a marketing choice more often than a technical disclosure. The question that matters is whether the answer is right, not what produced it.
The case for boring, stable API versioning
An exciting new API version is a migration project for everyone downstream of it. Boring, stable versioning is a feature, not a lack of ambition.
Why we didn't build a browser SDK first
A browser SDK for a server-side lookup mostly just moves your API key somewhere a visitor's browser can see it. That is not a convenience worth having.
Only Our takes, as it is published.
Subscribe to Our takes