Reference data and enrichment
Thirty-four million rows, as one step
Countries, languages and currencies. 13.4 million populated places and geographic features. 19 million name variants. Two million postal codes. Airports, seaports, vehicle makes. Sixty-five endpoints, no authentication, no rate card, because na di same platform wey your workflow already dey run ontop.
Why dis one different
For every other automation tool, "validate dis address" na paid third-party integration. You go find vendor, open account, agree rate card, get key, store di key, watch di quota, come renegotiate when your volume change. Di lookup itself take twenty milliseconds; di procurement take two weeks.
Here na just one step inside di picker. Di data na public reference data — GeoNames, official code lists, published registers — wey castomAPI clean, index and serve, and di reason say plenty products for dis family need di same thing and to build am once cheap pass to build am twelve times.
Search dey use trigram with three-character minimum, so partial name or name wey dem spell wrong go still find di place. Dat minimum na deliberate: two characters go match everything, and lookup wey match everything worse pass no lookup at all.
Di three things people dey do with am
Validate — stop bad data for door. Dat one na real postal code for dat city? Dat country code dey exist, or na typo wey somebody make for 2019 wey don dey spread since? PLN na currency, and na di one dem suppose charge dis customer?
Normalise — "Warsaw", "Warszawa", "Varsovie" and "Варшава" na one place with one identifier. Nineteen million name variants dey exist so your customer database no go need hold four spelling of di same city come pretend say na four cities.
Enrich — city name come turn coordinates, timezone, administrative region and population figure. Airport code come turn name and location. Postal code come turn everything wey dey above am for di hierarchy. Six fields wey person suppose type by hand, filled for twenty milliseconds, for free.
Di timezone na di quiet one
When you resolve place, e give you di timezone, and timezone na wetin make "send dis one nine for morning" mean nine for morning for di person wey go receive am, no be nine for morning for you. Quiet hours, schedules and reminders all go correct for international list without anybody dey maintain mapping table.
- 1Input"ul. Powstańców Śląskich 5, 53-332 Wrocław, PL"
- 2Postal code match53-332 → Wrocław, Dolnośląskie, PL.
- 3Place resolve51.0938 N, 17.0226 E · Europe/Warsaw · population bi 674 079.
- 4Wetin dem write backSix fields wey dem don fill wey one person for don type by hand.
- §CostDeterministic step. No key, no quota, no charge for each lookup.
Time wey e take: 40 ms65 endpoints dey available
Thirty-four million row dem. One step.
Example wey don work
Where e dey earn im place
Before di carrier see am
Address wey dem check and normalise before dem buy shipping label. Label wey dem reject cost fee plus one day; postal code wey dem reject cost twenty milliseconds.
Before di accountant see am
Currency code and country code wey dem validate before dem raise invoice, wey cheap well well pass to validate dem after dem don send am.
Deduplicate one list
Two records wey get di same customer under two spellings of di same city go merge well once both cities resolve to di same identifier.
Routing by geography
Coordinates for a customer and coordinates for your depots, and di run go pick di nearest one without anybody dey maintain postcode-to-depot spreadsheet.
Language, correct
A country resolve to im languages, so di message wey go out go be one wey di recipient fit read — na data decide am, no be assumption about flag.
Fleet and logistics
Vehicle makes, airports and seaports as canonical records, for di workflows wey dia work involve something wey dey move physically.
Di honest limits
Dis na public reference data, no be commercial address-verification service. E go tell you say 53-332 na real postal code inside Wrocław and give you di coordinates of di locality. E no go tell you whether flat 212 dey exist for number 5, or whether anybody dey live there. For delivery-point-level verification, you need national postal operator product, and a workflow fit call am over HTTP alongside dis one.
E sef no be source of personal data. No person dey inside am. E contain places, codes, registers and public facts — na exactly why e fit dey served without authentication.
On freshness: reference data dey change slowly, and dem dey refresh dis one on schedule rather than continuously. Village wey dem just rename no go appear dat same afternoon. For anything wey dey change by di hour, you need di events feed instead, wey dem build for exactly dat kain thing.