Billing is determined by the number of tile requests to basemaps-api.arcgis.com, ibasemaps-api.arcgis.com, or static-map-tiles-api.arcgis.com.

Billing is determined by the number of basemap styles sessions created with the sessions/start operation.

Billing is determined by the number of requests to /places/near-point/ or /places/within-extent/.

Billing is determined by the number of /places/{placeId} requests returning place attributes.

Billing is determined by the number of /places/{placeId} requests returning address attributes.

Billing is determined by the number of /places/{placeId} requests returning detail attributes.

Billing is determined by number of /places/{placeId} requests returning location attributes.

Billing is determined by number of results returned from the findAddressCandidates operation.

Billing is determined by number of requests to the findAddressCandidates operation with the forStorage=true parameter.

Billing is determined by the number of geocode results returned from the batchGeocode operation.

Billing is determined by the number of routes returned using the solve or submitJob operation.

Billing is determined by the number of routes returned using the findBestsSequence parameter of the solve or submitJob operation.

Billing is determined by the number of service areas returned from the solveServiceArea or submitJob operation.

Billing is determined by the number of routes returned from the execute or submitJob operation.

Billing is determined by the number of orders requested with the submitJob operation.

Billing is determined by the number of requests to the solveClosestFacility or FindClosestFacilities/submitJob operation.

Billing is determined by the number of demand points returned from the submitJob operation.

Billing is determined by the number of origin-destination pairs generated with the solveODCostMatrix or submitJob operation.

Billing is determined by the number of points considered with the SnapToRoads operation.

Billing is determined by number of attributes returned using the enrich operation.

Billing is determined by number of reports generated using the Reports operation.

Billing is determined by number of locations returned using the at-point or at-many-points operation.

Find data includes extract features, find existing locations, and derive new locations.

Combine data operations include dissolve boundaries, merge layers, overlay layers, and join features.

Summarize data operations include aggregate points, summarize within, summarize nearby, summarize center and dispersion.

Analyze patterns operations include hot spot analysis, find outliers, interpolate points, and calculate density.

Calculate geometries operations include create buffers, find centroids, and generate tessellations.

Billing is per megabyte stored in your feature service database.

Billing is per megabyte of your stored items, files, feature attachments, and published tiles.

Billing is per megabyte of bandwidth returned by queries to your feature services.

Billing is per megabyte of bandwidth consumed by edits applied to your feature services.

Billing is per megabyte of bandwidth consumed by requests to your vector tile services.

Billing if per megabyte of bandwidth consumed by requests to your map tile services.

Billing is per tile generated by publishing your services.