canonical: https://jentic.com/apis/yandex.com/yandex-maps-geocoder-api

# Yandex Maps Geocoder API

The Yandex Maps Geocoder API converts addresses to geographic coordinates (forward geocoding) and geographic coordinates to addresses (reverse geocoding). It supports structured and unstructured address queries and covers Russia, CIS countries, Turkey, and other regions. The API exposes 1 endpoints secured with apiKey authentication.

## For AI agents

Programmatically geocode an address or coordinates. Covers 1 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for maps and geolocation only.

## Capabilities

- Geocode an address or coordinates
- Manage maps geolocation data programmatically
- Integrate Yandex Maps Geocoder API into automated workflows
- Query and filter Yandex Maps Geocoder API records by parameters
- Monitor Yandex Maps Geocoder API operational status and events

## Use cases

### Maps and Geolocation Operations

Use the Yandex Maps Geocoder API to perform maps geolocation operations programmatically. The API provides 1 endpoints covering core functionality including geocode an address or coordinates.

Example prompt: Call GET /1.x/ to geocode an address or coordinates

### Data Retrieval and Monitoring

Query Yandex Maps Geocoder API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary Yandex Maps Geocoder API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Yandex Maps Geocoder API 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 'geocode an address or coordinates', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /1.x/ | Geocode an address or coordinates |

## Key resources

- **Geocoding** — Forward and reverse geocoding operations

## Why Jentic

- **Setup:** Wiring Yandex Maps Geocoder by hand means appending your apikey to each query against geocode-maps.yandex.ru, parsing its response format, and handling retries yourself. Through Jentic you install once, import Yandex Maps Geocoder from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Yandex Maps Geocoder exposes a single geocoding operation, so scoping is simply whether the agent may call it. You grant that one read operation and nothing more travels with the credential.
- **Credential handling:** Your Yandex Maps Geocoder 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 'geocode an address' or 'resolve coordinates to a place', and Jentic returns the matching Yandex Maps Geocoder operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Here** — Alternative maps geolocation API
- **Tomtom** — Alternative maps geolocation API
- **Googleapis** — Complementary maps geolocation API

## FAQ

### What authentication does the Yandex Maps Geocoder API use?

The Yandex Maps Geocoder API uses an API key passed in the `apikey` 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 geocode an address or coordinates with the Yandex Maps Geocoder API?

Yes. Use the GET /1.x/ endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Yandex Maps Geocoder API?

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 geocode an address or coordinates through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'geocode an address or coordinates'. Jentic returns the matching Yandex Maps Geocoder API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Yandex Maps Geocoder API have?

The Yandex Maps Geocoder API exposes 1 endpoints covering geocoding operations.

### Can I limit what my agent is allowed to do with the Yandex Maps Geocoder API?

Yes. The Yandex Maps Geocoder API exposes a single read operation, the GET /1.x/ geocoding call, so in your self-hosted Jentic One instance you decide whether your agent may call it at all. Because you set the rules, the agent can reach only that one geocoding operation and no other capability travels with the stored credential. You control which credentials the agent uses, and the API key is injected at execution time rather than exposed to the agent.