Frequently asked questions

No. Any address gets 2,500 requests a day with no key and no account, on every endpoint and every drop-in host. Sign up (your name, an email address and a password) when you want keys of your own, a usage history, prepaid credit or an Unlimited package. Requests made without a key and requests made with a key from the same network share one daily allowance, so an account does not double the free 2,500.

Your name, an email address and a password. Nothing else: no company, no card. You can create more keys straight away and add credit or a package whenever you decide to.

You top up a balance in advance with a pack of €10, €25, €50 or €100, by card or in crypto. Each request above your account's free 2,500 for the day takes €0.0001 from it. Credit is shared by all your pay-as-you-go keys, never expires, and nothing is charged automatically. When it is empty, requests above the free allowance are refused with 402 until you top up.

By card through Polar, or in crypto through NOWPayments: Bitcoin, Ethereum, USDT, USDC, Litecoin and many more. The amount is fixed at checkout and applied once the payment confirms. Everything is priced in euros.

A key with no per-request charges on every endpoint and every drop-in host, for €50 per month or €500 per year (two months free), usable from up to three IP addresses per rolling 24 hours. Each package has its own key; order several if you have several applications. See pricing.

Yes. Your dashboard has a referral link; 10% of every invoice paid by someone who signed up through it goes to a referral balance kept apart from your credit. Move it into credit whenever you like, or cash it out in crypto from €20. Cashouts are processed by hand and the transaction id appears in your dashboard.

Sometimes: percentage or fixed discounts on a top-up or package, or bonus credit. Enter a code when you create the invoice or on any unpaid invoice before paying.

Per account, per UTC day (all of its keys together), across all endpoints and drop-in hosts. Batch IP lookups and multi-point elevation calls count one per item. Refused requests and server errors are never counted.

The first addresses to use a key each take a slot for 24 hours from their first request. A pay-as-you-go key has two slots, an Unlimited key three. When a slot's 24 hours end it frees on its own, so if two servers used the key at 02:00 and a third at 04:00, two slots are free again at 02:00 the next day and the third at 04:00. A request from a new address while every slot is held is refused with HTTP 403 and the code key_ip_limit; the response says when the next slot frees. For more machines, create more keys or add more packages.

Yes, with a browser key. Create one in the dashboard for your website: it works only from scripts on that one website (with or without www.), has no IP limit, and each visitor may make 60 requests a minute. Give it a daily spending limit so a copied key cannot run up your credit. Server keys stay on your servers. Without a key, calls from scripts on a web page get 2,500 free requests a day per website.

From a web page, yes: CORS is enabled and the drop-in hosts accept the JSONP callback parameter their original providers do. Use a browser key, which works only from your website, or no key within the free allowance for web pages. A server key in client code is visible to everyone and would hit its IP limit after a couple of visitors. A mobile app has no website to check, so call the API from your own server and keep a server key there.

Not a fixed one today. Traffic that looks like a runaway loop or an attack may be slowed down, and we will tell you if that ever happens to a key of yours. Batch endpoints exist so that you do not need hundreds of requests a second.

Revoke it in the dashboard and create a new one. Because of the IP limit a leaked key cannot be used from more than two or three machines a day anyway, and since credit is prepaid, nobody can run up a bill beyond the balance you chose to load.