canonical: https://jentic.com/apis/stadiamaps.com/stadiamaps

# Stadia Maps Geospatial APIs

The Stadia Maps Geospatial APIs provide you with the data you need to build awesome applications. The API exposes 20 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get turn by turn routing instructions between two or more locations., find the nearest roads to the set of input locations.. Covers 20 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Get turn by turn routing instructions between two or more locations.
- Find the nearest roads to the set of input locations.
- Calculate a time distance matrix for use in an optimizer.
- Match a recorded route to the road network.
- Trace the attributes of roads visited on a route.

## Use cases

### Developer Tools Operations

Use the Stadia Maps Geospatial APIs to perform developer tools operations programmatically. The API provides 20 endpoints covering core functionality including get turn by turn routing instructions between two or more locations., find the nearest roads to the set of input locations., calculate a time distance matrix for use in an optimizer..

Example prompt: Call POST `/route/v1` to get turn by turn routing instructions between two or more locations.

### Automated Geocoding Management

Automate geocoding operations by combining multiple Stadia Maps Geospatial APIs endpoints. Agents can find the nearest roads to the set of input locations. and then calculate a time distance matrix for use in an optimizer. in a single workflow.

Example prompt: Call POST `/nearest_roads/v1` to find the nearest roads to the set of input locations., then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Stadia Maps Geospatial APIs endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'get turn by turn routing instructions between two or more locations.', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/route/v1` | Get turn by turn routing instructions between two or more locations. |
| POST | `/nearest_roads/v1` | Find the nearest roads to the set of input locations. |
| POST | `/matrix/v1` | Calculate a time distance matrix for use in an optimizer. |
| POST | `/isochrone/v1` | Calculate areas of equal travel time from a location. |
| POST | `/optimized_route/v1` | Calculate an optimized route between a known start and end point. |
| POST | `/map_match/v1` | Match a recorded route to the road network. |
| POST | `/trace_attributes/v1` | Trace the attributes of roads visited on a route. |
| GET | `/geocoding/v1/autocomplete` | Search and geocode quickly based on partial input. |

## Key resources

- **Geocoding** — Operations related to Geocoding
- **Geospatial** — Operations related to Geospatial
- **Routing** — Operations related to Routing

## Why Jentic

- **Setup:** Wiring the Stadia Maps Geospatial APIs by hand means carrying its API key into api.stadiamaps.com and building the routing, matrix, and isochrone request bodies yourself. Through Jentic you install once, import the Stadia Maps Geospatial APIs from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** You can limit the agent to the operations it needs, such as routing between locations, autocomplete geocoding, or computing a matrix, so it calls only the geospatial operations you allow.
- **Credential handling:** Your Stadia Maps API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get turn-by-turn directions between two points' or 'autocomplete a place name', and Jentic returns the matching Stadia Maps operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Stadia Maps Geospatial APIs use?

The Stadia Maps Geospatial APIs uses an API key passed in the `api_key` query. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get turn by turn routing instructions between two or more locations. with the Stadia Maps Geospatial APIs?

Yes. Use the POST `/route/v1` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Stadia Maps Geospatial APIs?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I get turn by turn routing instructions between two or more locations. through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get turn by turn routing instructions between two or more locations.'. Jentic returns the matching Stadia Maps Geospatial APIs operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Stadia Maps Geospatial APIs have?

The Stadia Maps Geospatial APIs exposes 20 endpoints covering geocoding, geospatial, routing operations.

### Can I limit what my agent is allowed to do with the Stadia Maps Geospatial APIs?

Yes. Because you run your own self-hosted Jentic One instance, your rules decide which Stadia Maps operations and credentials the agent may use. You can restrict it to just the endpoints it needs, such as POST `/route/v1` for turn-by-turn routing, GET `/geocoding/v1/autocomplete` for place lookups, or POST `/matrix/v1` for time-distance matrices, and block the rest. The agent can then call only the geospatial operations you have allowed.