Geoapify Pricing Details

This page provides all the information you need to understand the pricing of Geoapify's geolocation and mapping services.

We use credits to measure the API requests in Geoapify APIs. Credits play an important role in helping us measure the usage of different APIs, even when they vary in computational complexity. This allows us to provide a unified pricing structure that accommodates the differences in computational demands.

We have developed an API request Cost Calculator to help you estimate the cost of your API requests in credits. The calculator allows you to input the details of your usage, including the specific API parameters and quantities, and instantly provides an estimate of the corresponding credit consumption:

API Name	Number of requests	Cost in credits
Maps 1 Map Tile request costs 0.25 credits (4 map tiles = 1 credit) According to statistics, an interactive map loads approximately 50 map tiles per user session According to statistics, an interactive map load 14 map tiles per map view		0
Static Maps Width (px): Height (px): Number of Map Marker Icons: A Static Maps API request counts the API call by itself, map tile requests, and Marker Icon API requests 1 Static Maps request = 1 + MAP_TILES / 4 + MAP_ICONS 1 Static Maps call itself costs 1 credit 1 Geoapify Map Tile request costs 0.25 credits (4 map tiles = 1 credit) 1 Marker Icon API request costs 1 credit The total number of map tiles is roughly estimated as Math.ceil(MAP_WIDTH/256) x Math.ceil(MAP_HEIGHT/256) 1 request = 0.00 credits		0
Geocoding API 1 Geocoding API request costs 1 credit 1 Reverse Geocoding API request costs 1 credit 1 Address Autocomplete API request costs 1 credit		0
Routing API Number of waypoints: Route length (km): 1 credit per each pair of waypoints: NUMBER_OF_CREDITS = WAYPOINTS - 1 1 additional credit is counted for each 500 km of result route length if route length > 500 km 1 request = 0 credits		0
Map Matching API Number of waypoints: 1 credit per each 100 waypoints 1 request = 0 credits		0
Route Matrix API Number of source locations: Number of target locations: The number of credits you receive depends on the number of source and target elements or Matrix elements. The maximum number of elements is 1000. Max(NUMBER_OF_SOURCES, NUMBER_OF_TARGETS) * Min(NUMBER_OF_SOURCES, NUMBER_OF_TARGETS, 10) Example: for 5 sources and 7 targets the API call will cost Max(5, 7) * Min(5, 7, 10) = 7 * 5 = 35 credits 1 request = 0 credits		0
Route Planner API Number of locations: The Route Planner API cost depends on the number of locations you provide. The maximum number of locations for synchronous API calls is 300. The locations include Agent Start & End locations, Shipment Pickup & Delivery locations, Job locations When number of locations < 10: REQUEST_COST = NUMBER_OF_LOCATIONS * NUMBER_OF_LOCATIONS When number of locations >= 10: REQUEST_COST = NUMBER_OF_LOCATIONS * 10 Example: 7 agents with start and end location set + 30 jobs ( 72 + 30 = 44 location in total) will cost 44 10 = 440 credits 1 request = 0 credits		0
Isoline API Isochrone range: 5 minutes 1 credit counted for each 5 minutes of isochrone 1 request = 0 credits		0
Places API Number of places: The Places API requires 1 credit when the limit is 20 places or less When you query more than 20 places in one request, it costs 1 credit plus an additional credit for every 20 places returned 1 request = 0 credits		0
Place Details API With additional features: This is only features examples, check the full list of the features on the Place Details Documentation Page 1 Place Details API request costs 1 credit plus requested features costs "building", "details.population", "details.full_geometry", and "details.names" features add an additional 1 credit each "building.places", "radius_100.restaurant", "walk_10.supermarket" and other places features add 1 additional credit per every 20 results "walk_5", "walk_10", "drive_5", "drive_10", "drive_15" and other isochrone features add 1 additional credit per each 5 minutes isochrone 1 request = 0 credits		0
Boundaries API Number of results: Geometry as point Every 20 Boundaries API results are counted as 1 credit When geometry type is different than point (the default value), each returned result costs 1 credit additional 1 request = 0 credits		0
IP Geolocation 1 IP Geolocation API request costs 1 credit		0
Map Marker API 1 Marker Icon API request costs 1 credit		0
Total		0

The estimated usage:

0 credits / day
0 credits / month

Recommended Pricing Plan:

Free

3,000 credits / day

~90,000 credits / month

Frequently Asked Questions

What are credits?

Credits are the fundamental currency of Geoapify APIs. They serve as a unit of measurement for the services you consume within our mapping platform. Every API request you make deducts a certain number of credits from your account, reflecting the resources utilized by that particular request.

Why do we use credits?

At Geoapify, we have chosen to implement a credit-based system to provide flexibility and cost-effectiveness to our users. This approach offers several advantages:

Granular resource consumption: Credits enable us to precisely measure the resources consumed by each API request. Different API endpoints and functionalities have varying resource requirements, and credits allow us to reflect this accurately in our pricing structure.
Scalable usage: With a credit-based system, you have the freedom to scale your usage according to your project's needs. Instead of being confined to fixed pricing tiers, credits allow you to pay only for the specific services you require, making it easier to manage costs as your application grows.
Transparent and predictable pricing: By utilizing credits, we provide transparent pricing that allows you to estimate and plan your usage effectively. You can evaluate the credit consumption of different API requests in advance, ensuring that there are no surprises when it comes to billing.
Flexibility across APIs: Geoapify offers a range of APIs with diverse functionality, such as geocoding, routing, distance matrix calculations, and more. The credit-based system allows us to assign appropriate credit values to each API, taking into account factors like computational complexity and data usage. This ensures fair and proportional pricing across all our services. Using credits as our currency allows us to strike a balance between providing a powerful geospatial platform and offering flexible, transparent pricing. It empowers you to leverage our APIs precisely according to your project's needs, optimizing both functionality and cost-effectiveness.

What happens if I exceed Geoapify's API usage limit? Will my API keys be blocked immediately?

No, we won't block your API keys immediately if you exceed the usage limit. Instead, we will contact you to discuss the situation and offer possible scenarios on how to proceed. We understand that usage patterns can vary, and our goal is to work with you to find a solution that suits your needs. We may explore options such as upgrading to a higher-tier plan, adjusting your usage patterns, or customizing a solution to ensure you can continue using our services effectively.

What are rate limits in Geoapify's API services?

Rate limits refer to the restrictions on the number of requests you can make within a specific time frame. They are designed to control the rate at which requests are made to the API. Rate limits help ensure the stability, performance, and availability of the API system by preventing excessive traffic and overloading the servers.

What happens if I exceed the rate limits?

If you exceed the rate limits, we may need to take measures to protect the system and maintain a stable environment. In such cases, we reserve the right to block or limit your requests temporarily. This action is taken to prevent excessive load on the system and ensure the best possible service for all users.

To determine whether the rate limits are being exceeded, we calculate the average request rate over a certain period. This means that even if your requests occasionally spike above the rate limit but your average request rate remains within the allowed limits, you are less likely to be affected. However, consistently exceeding the rate limits may result in restrictions on your requests.

What is the difference between synchronous and asynchronous API calls with Geoapify?

Geoapify supports both synchronous and asynchronous API calls, offering flexibility to developers based on their specific requirements:

Synchronous API calls: With Geoapify, you can make synchronous API calls where the client application sends a request and waits for the immediate response from the API. This approach is suitable when you need real-time or near real-time information and require an immediate response before proceeding.
Asynchronous API calls with Geoapify Batcher: Geoapify provides an additional option for making asynchronous API calls using Geoapify Batcher. This feature allows you to send multiple API requests asynchronously in a batch, and the API processes them in the background. You can continue with other tasks while the requests are being processed. Once the processing is complete, you can retrieve the responses.

What are the benefits of using asynchronous API calls with Geoapify Batcher?

Using asynchronous API calls with Geoapify Batcher offers several benefits:

Cost savings: Asynchronous API calls can help you save up to 50% of API costs compared to synchronous calls. By sending multiple requests in a single batch, you optimize resource usage and reduce the overall number of API calls.
Processing larger tasks: Asynchronous calls are particularly useful for processing larger tasks or handling complex computations. For example, with asynchronous API calls, you can process Route Optimization tasks involving up to 1000 locations, enabling you to tackle more extensive routing scenarios efficiently.

How long does the processing of an asynchronous API task take with Geoapify?

The processing time for asynchronous API tasks with Geoapify can vary depending on several factors. While asynchronous requests help optimize resource usage and enable us to offer better pricing, it's important to note that the processing of these tasks may take longer compared to synchronous requests.

Geoapify employs efficient resource allocation to ensure reliable and timely processing of asynchronous tasks. Asynchronous requests are processed using available free system resources and are typically assigned a lower processing priority compared to synchronous tasks. This approach allows us to maximize resource utilization and provide more cost-effective pricing for asynchronous or background jobs.

However, due to the lower processing priority and utilization of available free resources, the processing time for asynchronous tasks may be longer. In worst-case scenarios or during peak periods, it is possible for the processing time to extend to several hours.

How is the cost of an Asynchronous (batch) request calculated with Geoapify?

The cost of an Asynchronous (batch) request with Geoapify is calculated in the following way:

Each API call included in the batch is counted with a coefficient of 0.5, which helps to offer more cost-effective pricing for batched requests.
In addition, the cost includes one credit for job creation and one credit for each result request.

For example, when you send an asynchronous request to geocode 1000 addresses and then retrieve the result with a single request, the cost would be calculated as follows:

The 1000 API calls included in the batch would be counted as 1000 * 0.5 = 500 credits (using the coefficient of 0.5).
The job creation cost would be 1 credit.
The result request cost would be 1 credit. Therefore, the total cost for this asynchronous request would be 500 credits (API calls) + 1 credit (job creation) + 1 credit (result request) = 502 credits.

If you have any further questions or need additional assistance, please don't hesitate to contact us. We're here to help!