Free tier
Get an API key
Enter an email address and the key is in the response.
What the free key includes
| Calls per day | 200 |
|---|---|
| Back to back | 20 |
| Endpoints | Every one that takes a key |
| Batch size | 10 per request |
| Keys per address | 5 |
| Expiry | None |
Every endpoint is open on the free key, including the cluster planner, the service-target inverter, the batch endpoint and the change feed. The free plan’s one condition is a visible credit beside results you show publicly; a paid plan removes it, unbrands the widget on your own site and raises the daily allowance — never a feature hidden from the free key.
Before you request a key
- The key is shown once. Only its SHA-256 digest is stored, which is enough to recognise the key and not enough to show it again. Lose it and request another.
- The address is not verified. No confirmation email is sent. The address is kept so a breaking change can be announced to the people it affects.
- 200 a day is a trial allowance. Enough to read the docs, wire a client and run something small; not enough to serve a shop’s catalogue. Every endpoint answers on it at full fidelity.
- You are warned before you are refused. Past 80% of the day every response carries an
X-RateLimit-Warningheader, and the usage page shows where a key stands without spending a call.
Before you build
Read the endpoint reference for request shapes, and the accuracy scorecard for how far each figure can be trusted. A response that cannot be justified returns a 422 naming the missing field rather than a plausible number.
Running a storefront? The embeddable widget needs no key at all.