Monitor your key's usage before you hit a limit
Watching your quota headers as you go tells you when a limit is approaching, well before a request actually gets rejected.
Test your integration without spending your daily quota
Building an integration usually means dozens or hundreds of test calls before anything goes near production traffic, and none of that testing needs to touch a paid tier.
Testing with no key at all
2,500 free requests a day are available from any address with no key needed at all, which is enough for most integration work: wiring up request formatting, checking response parsing, and working through error handling for a handful of test cases each.
GET /v1/forward?q=Test Address, Test City&limit=1No X-API-Key header, no Authorization header, nothing but the request itself.
Watching quota headers while testing
Even without a key, every response carries the same quota headers, so you can watch X-Quota-Used and X-Quota-Free-Remaining climb and fall exactly as they would in production, which is useful for testing how your own code handles those headers before it matters for real.
X-Quota-Limit: 2500
X-Quota-Used: 42
X-Quota-Free-Remaining: 2458Testing a key without spending credit
Once you sign up and generate a key, that key also gets its own 2,500 free requests a day, separate testing room that does not touch prepaid credit or count against an Unlimited package. This is the point to test key-specific behavior, such as the different ways to send the key, header, bearer token, basic auth, or query parameter, all without spending anything.
Deliberately testing error paths
Send a request with an invalid parameter to see a 400, or an intentionally wrong key to see a 401, so your error handling code has actually been exercised before launch rather than assumed to work. Each of these test calls, successful or not, is one request against the free allowance, not something that should worry you at normal testing volumes.
Moving to production traffic
Once real traffic starts, the same free allowance keeps covering typical daily usage for a lot of smaller integrations, with prepaid credit or an Unlimited package only needed once volume passes 2,500 requests a day.
There is no separate sandbox environment needed here, since the free allowance already gives a full testing ground with the real API. Get started by generating a key from the dashboard, or read the authentication docs first if you want to see the key formats before signing up.