What is one credit?

Credits are GraphHopper’s currency and can be spent on all Directions API products. A Standard subscription, for example, includes 15,000 credits per day. Each request costs credits as follows:

Routing API

A standard request with 2 to 10 locations costs 1 credit and so 15 000 daily credits allow 15 000 such routes. Above 10 locations, the cost is #locations / 10 e.g. a route with 25 locations costs 2.5 credits.

A request that demands alternative routes (algorithm=alternative_route) or round trips (algorithm=round_trip) costs 2 credits.

Requests with optimize=true (solves a Traveling Salesman problem) cost 10× the normal cost. E.g. optimizing 12 locations costs 12 credits instead of 1.2.

Route Optimization API

The cost of a Route Optimization API request depends on the number of vehicles and unique locations in that request and is calculated as #vehicles × #locations. However, an optimization request costs at least 10 credits and not more than 10 × #locations.

For example:

• If you want to solve a Traveling Salesman problem with 1 vehicle and 100 stops, it will cost you 1 × 100 credits.
• If you want to solve a vehicle routing problem with 10 vehicles and 150 stops, it costs 10 × 150 = 1,500 credits. If you buy a Premium plan, you receive 50,000 credits per day, i.e. you can solve 50,000/1,500 = 33 of such vehicle routing problems per day.
• If you want to solve a big vehicle routing problem with 50 vehicles and 1000 stops you can buy a custom package and the credit costs will be 10 × 1000 = 10,000.

The GET request to fetch the solution costs 0.3 credits per request. This might be an incentive to reduce heavy polling. You can avoid this and use the recommended synchronous POST endpoint instead.

Matrix API

The costs of one Matrix API request are calculated as follows: #origins × #destinations / 2 credits. For larger requests the formula MAX_OF(#origins, #destinations) × 10 is used if the result is smaller. However, each request costs at least 1 credit.

For example, if you have 2 origins and 10 destinations, 2 × 10 / 2 = 10 credits will be charged. If you have 30 origins and 40 destinations, the second formula is cheaper and so the credits are calculated as 40 × 10 = 400.

Geocoding API

For the Geocoding API we have integrated different providers. Each provider has its own prices. To take these differences into account, the prices per geocoding request vary depending on the provider. The following list shows the credit costs per request for the different providers:

• default: 0.3 credits
• gisgraphy: 0.3 credits
• nominatim: 0.9 credits
• opencagedata: 0.9 credits

Map Matching API

The cost of a Map Matching API request is calculated using the following formula: input_locations / 50. However, each request costs at least 1 credit.

Isochrone API

The costs for one Isochrone API request are 2 credits for every minute it explores. However, each request costs at least 10 credits. For example, if you want to calculate an isochrone with a time limit of 20 minutes (1200 seconds), that request will cost 2 × 20 = 40 credits.

Cluster API

One Cluster API request costs the number of customers times 10 and so at least 10 credits. For example, if you want to calculate a cluster request with 50 customers it costs 50 × 10 = 500 credits.

An exception is if you use the profile ‘as_the_crow_flies’, then the credit costs are equal to the number of customers, i.e. at least 1 credit.

---

← Back to the FAQ overview