Base Plan Pricing
Users of HERE Platform Base Plan have access and use-rights to the following HERE Materials, SDKs and Tools, Data Service and Location Services in accordance to the HERE platform terms.
The information included on this page constitutes “Confidential Information” under the HERE Platform Terms or your NDA with HERE.
HERE Location Service Rates
Transactions definitions and excluded use cases
1 Transaction is counted for every Request for all HERE service features, except as follows:
Feature | Transaction definition |
Multi Reverse Geocode | 1 Transaction equals each geocoordinate in the Multi Reverse Geocode Request. |
Batch Geocode & Reverse Batch Geocode | 1 Transaction equals each individual address or geocoordinate within a batch Geocode Request. |
Geofencing | 1 Transaction is counted for every Request. If Geofencing is requested including HERE Map Geometries, then 1 Map Attributes Transaction is additionally counted for each accessed Map Attributes API tile per layer. |
Map Attributes | 1 Transaction is counted for each tile per layer. For example, a request that results in 5 tiles for speed limit layer and 5 tiles for fuel stations layer equates to 10 Transactions. |
Intermodal Routing | 1 Transaction is counted for each returned alternative Intermodal Route(s) set by the Customer for the intermodal_alternatives parameter in the API request. If the system determines that there are no available intermodal routes, the Request is still counted as one Transaction. |
Isoline Routing | 1 Transaction equals each individual Isoline within an Isoline Request. |
Matrix Routing | 1 Transaction means if Starting Points or number of Destination Points is less than 5, the number of Transactions is calculated by multiplying the number of Starting Points by the number of Destination Points. If the number of Starting Points and number of Destination Points are 5 or greater, the number of Transactions is calculated by multiplying 5 with the greater of (i) the number of Starting Points or (ii) the number of Destination Points. |
Tour Planning | The number of Transactions charged for a Request is the sum of all locations such as starting points, destination points and/or stops as processed by the API. |
Route Matching | 1 Transaction is counted for every Request. If Map Attributes along the matched route are requested, then 1 Map Attributes Transaction is additionally counted for each accessed Map Attributes API tile per layer. |
Waypoints Sequencing | For each request with up to 100 waypoints plus origin and destination, 1 Transaction is counted. If a Request contains 101 to 200 waypoints plus origins and destination, 2 Transactions are counted. |
Speed Limits | 1 Transaction equals 1 Request if the Request returns at least one Speed Limit Result. Additionally, 1 Geocode & Reverse Geocode, Multi Reverse Geocode or Lookup Transaction is counted. |
EV Charge Points | 1 Transaction equals 1 Request if the Request returns at least one EV Charge Point Result. Additionally, 1 Discover / Search Transaction is counted. |
More information about each HERE service feature can be found in the documentation.
Excluded Use Cases
The following use cases are excluded from the Base Plan. If you are interested in these use cases please contact us.
“Asset Management,” meaning, in relation to an Asset, the provision of any one or all of the following (i) locating, tracking and/or displaying on a map; (ii) provision of route calculations; and (iii) deriving of analytics; and (iv) alerts that inform drivers of potential hazards on the road such as incoming pedestrians, vehicle braking, dynamic hazards or potholes "Safety Enhancement Alerts";
“Usage Based Insurance (UBI)/Telematics,” meaning, in relation to an Asset, the analysis of post trip driving information which excludes, in particular but not limited to, real-time tracking and providing real-time alerts or feedback loop to the Asset; and
“Optimization,” meaning Asset Management and, in relation to one or more Assets, utilizing software or application(s) to calculate the order of destinations and or routes.
“Asset” means, individually, a person (including the user of your application), an animal, a device, a piece of cargo, a means of transportation, a vehicle or any other object actively managed using HERE’s service.
Data Services
The HERE Platform offers tools to create and manage data assets. Data is organized in catalogs, layers which can be created, configured, managed, and shared using the platform portal, command line interface, data client library or data API.
Free Usage | Rate Per Unit | |
Blob | Up to 20 GB-months | $0.09 per GB-months |
Data IO | Up to 20 GB | $0.33 per GB |
Interactive Map IO | Up to 0.25 GB | $6.19 per GB |
Interactive Map Storage | Up to 0.1 GB-months | $0.83 per GB-months |
Meta Data | Up to 0.1 GB-months | $66 per GB-months |
Volatile | Up to 0.2 GB-months | $66 per GB-months |
Stream | Up to 0.5 MB/s-months | $50 per MB/s-months |
Stream TTL | Up to 42 GB-months | $0.72 per GB-months |
For more details about storage measurements and costs, see the Cost Analysis Guide.
SDK Rates
You will be charged the rates for the HERE Location Services and Data Services that are utilized through your use of the SDKs. To see list of Location Services by SDK, click here.
SDK | Rate Per Unit |
HERE SDK Explore Edition | HERE Location Service Rates |
Maps API for Javascript | HERE Location Service Rates |
HERE Data SDK | Data Service Rates |
