---
# System prepended metadata

title: Anchors

---

## Anchors

### Types of anchors
Anchor types are differentiated by the scope in which they are valid, from local to world-wide.

1. **Local anchors** are stored with the app locally, and valid only for that instance of the app. The user must be physically at the location where they are placing the anchor.

2. **[Cloud Anchors](https://developers.google.com/ar/develop/cloud-anchors)** are stored in Google Cloud and may be shared between app instances. The user must be physically at the location where they are placing the anchor.

3. **[Geospatial anchors](https://developers.google.com/ar/develop/geospatial)** are based on geodetic latitude, longitude, and altitude, plus Google's Visual Positioning System (VPS) data, to provide precise location almost anywhere in the world. The user may place an anchor from a remote location as long as the app is connected to the internet and able to use the VPS.

**Questions:**

Can we place and retrieve anchors?
- Yes. Local, Cloud and Geospatial Anchors can be placed
- ARCore Cloud Anchor Management API can be used to manage cloud and geospatial anchors
 
API Pricing?
- ARCore API is free.

### Geospatial API usage quota

The ARCore SDK limits API requests to the ARCore service to the following limits for each project that uses the ARCore SDK:

1,000 sessions started per minute, or
100,000 requests per minute
API requests in excess of these limits may result in an `AR_EARTH_STATE_ERROR_RESOURCE_EXHAUSTED` error and an unfulfilled request.

