Clean a postal address a human typed, in 249 countries. Check a product against every EU recall since 2005. One REST call each, an answer in milliseconds, and a plain explanation of what was corrected and what was not. Start free in two minutes - no contract, no minimum, no credit card for the free tier.
Paid plans start at $29 a month and fall to $0.0004 a call at volume. You can see every price before you sign up, and cancel in one click.
# An address as a customer actually typed it. curl -X POST https://<host>.p.rapidapi.com/v1/normalize \ -H 'X-RapidAPI-Key: YOUR_KEY' \ -d '{"address":"8 bd du port 95000 cergy","country":"FR"}' → 8 Boulevard du Port, 95000 Cergy house number found in the street itself, coverage "authoritative", and an explanation of every single change.
Because free is the raw file, and the raw file is not the answer. Here is what stands between the two, and what it costs you to cross it yourself.
A public register is typed by different people, in different countries, into fields never meant to be queried. The same place is spelled three ways; the same product is recalled four times. Reconciling that is the work, and it does not end: the file is republished and the work starts again.
Both APIs refresh on the publisher's own clock, automatically, and every answer carries the date of the data it was built from. Nobody on your side has to notice that a source changed shape.
Every source was checked for commercial reuse before a line of code was written, and the attribution travels inside each response. You call an endpoint; you do not inherit a licence review.
On RapidAPI, which issues the key and meters the calls. The free tier bills nothing and needs no card.
One key works across every API you subscribe to on the hub, with ready-made snippets in 20+ languages.
The interactive console runs your first real call in the browser, before you write any code at all.
Each one covers a single public source, end to end. More are in preparation; they appear here when they are live, not before.
Turn an address a human typed into the official one. Abbreviated, misspelled, parts in the wrong order: send it with a two-letter country code and get back the postcode, the official locality, the normalised street, the house number checked against the street itself, print-ready lines, and a plain explanation of every correction. 249 countries in one integration, instead of one integration per country.
Who buys it. Checkouts that must not print a parcel against a street that does not exist, customer files accumulated over ten years, and agents that must decide whether two records describe the same place.
| Plan | Per month | Requests | Beyond that | Addresses per call |
|---|---|---|---|---|
| BASIC | Free | 100 | stops | 1 |
| PRO | $29 | 10,000 | $0.004 | 25 |
| ULTRA | $99 | 100,000 | $0.002 | 50 |
| MEGA | $399 | 1,000,000 | $0.001 | 100 |
Check your catalogue against the European Commission's Safety Gate. 47,000+ alerts since 2005 from 31 countries, matched by barcode, brand, model, or plain product title - one call per product, or 50 in a single batch. For sellers and marketplaces that must detect unsafe products under Regulation (EU) 2023/988.
Why a plain lookup misses it. Only a quarter of alerts carry a usable barcode in the barcode field, and the most common brand value in the whole archive is the literal word "Unknown". Reconciling what the source actually holds brings 84% of alerts within reach of a strong key. Measured: 92.7% exact on a seller's own product title.
Not how they are built - what you can hold us to.
Every API states how often it returns the right answer, measured on its full archive and rerun on every change. Nothing ships on a claim that has not been measured.
Weak matches carry a confidence score and a plain explanation, and are flagged as leads to review. A confidently wrong answer costs more than an honest uncertain one.
Official fields come back verbatim under source. Anything derived comes back separately under enriched, with the attribution, the extraction date and a link to the official record.
Where an API speaks the Model Context Protocol, it does so over the same data and the same code as its REST endpoints. One engine, never a second implementation to reconcile. The recalls API already does; the others follow.
Collection follows the publisher's own schedule, automatically, and the extraction date travels with every response, so you always know how fresh an answer is.
Every source is checked for reuse rights before a line of code is written, and the terms that apply to you are stated on that API's own page.
Nothing. Both APIs carry a free tier on RapidAPI: 100 requests a month on the address API, and a free tier on the recalls API. No credit card is needed for the free tier, and there is no contract and no minimum.
No. Oredrift is distributed through API marketplaces only. You subscribe yourself, you get a key immediately, and you cancel in one click. There is nothing to negotiate and nobody to talk to.
Plans are $0, $29, $99 and $399 a month, covering 100, 10,000, 100,000 and 1,000,000 requests. At the top plan that is about $0.0004 a call, and a single call may carry up to 100 addresses.
249 countries and territories, with 12,167,673 postcode and locality pairs and 24,022,634 streets. Coverage is not uniform, and it is not claimed to be: every answer declares its own coverage level, and the quality of each country is published.
No, and no honest open-data product can. Deliverability certification and postal bulk tariff eligibility are granted by each postal operator for its own network. What is promised is what the official reference says about what you sent, how far it could be corroborated, and an explanation of every correction.
Yes. The recalls API speaks the Model Context Protocol over the same engine as its REST endpoints, so an agent gets the same answers as any other client. Both APIs return a confidence score and a plain-English explanation, which is what an agent needs in order not to act on a guess.
It is returned as a lead to review, with a confidence score and the reason it matched, never as a decision. A confidently wrong answer costs more than an honest uncertain one.
If there is a public register you keep reading by hand, tell us which one. The APIs that get built are the ones somebody actually asked for.
Oredrift APIs are distributed through API marketplaces, with a free tier on each of them, so there is no sales process to sit through and nothing to negotiate. Every API page links to its contract and its live status, so you can read exactly what you would be calling before signing up for anything.