Install Jentic One Beta

Connect the MapAtlas API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the MapAtlas API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmapatlas.eu%2Fmapatlas" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmapatlas.eu%2Fmapatlas" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with MapAtlas API.

Forward geocode an address or place name to coordinates, filtered by boundary.country, a bounding rectangle, or a circle

Reverse geocode a point.lat and point.lon pair to the nearest address or place

Autocomplete addresses and points of interest as a user types, biased by focus.point.lat and focus.point.lon

Get turn-by-turn directions between two or more locations with a costing mode such as auto, bicycle, truck, or pedestrian

GET STARTED

Start building with MapAtlas API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use MapAtlas API for, with concrete tasks.

★ Location-aware agent through Jentic

An assistant that handles place questions calls the MapAtlas API through Jentic: it geocodes the user's address, then requests directions or an isochrone from that point. The token query parameter is injected by Jentic at call time, so the agent never holds it. Because MapAtlas runs on EU infrastructure, this suits teams that want location calls kept out of US data transfers.

Call GET /forward-geocode/ with text 'Damrak 1, Amsterdam' and size 1, take the returned coordinates, then POST /directions/ with locations from that point to 52.3600, 4.8852 and costing 'pedestrian'

Delivery route planning

Dispatch tools need to know which depot serves which customer and in what order to visit stops. The matrix operation returns travel times and distances between sources and targets, and the optimisation operation reorders intermediate stops TSP-style for a chosen costing such as truck. Together they cover assignment and sequencing on OpenStreetMap roads.

POST /matrix/ with two depot sources, eight customer targets, and costing 'truck', then POST /optimization/ with the chosen depot and its assigned stops to get the visit order

Catchment and reachability maps

Retail site selection and service planning start with who can reach a location in a given time. The isochrone operation returns up to four contours per request by minutes or kilometers, optionally as polygons, which can be drawn on a MapLibre map using a style fetched from the styles operation.

POST /isochrone/ with one location, costing 'auto', contours of 10, 20, and 30 minutes, and polygons true, then return the contour geometry

Cleaning GPS tracks

Fleet and fitness apps record noisy GPS points that drift off the road. The map-matching operation snaps a shape of coordinates to the road network for a costing mode, and the elevation operation returns terrain height along the same shape, so a track can be cleaned and profiled in two calls.

Call GET /map-matching/ with a shape of recorded points and costing 'bicycle', then POST /elevation/ with the matched shape and range true to get distance and height pairs

Key Endpoints

10 endpoints — the mapatlas api geocodes addresses, reverse geocodes coordinates, and calculates routes on an openstreetmap-based platform that runs on eu infrastructure.

METHOD

PATH

DESCRIPTION

GET

/forward-geocode/

Forward geocode an address or place

GET

/reverse-geocode/

Reverse geocode coordinates

GET

/autocomplete/

Autocomplete addresses and POIs

POST

/directions/

Turn-by-turn directions

POST

/isochrone/

Reachability contours

POST

/matrix/

Travel-time and distance matrix

POST

/optimization/

Optimise stop order

GET

/styles/

Fetch a vector map style

GET

/forward-geocode/

Forward geocode an address or place

GET

/reverse-geocode/

Reverse geocode coordinates

GET

/autocomplete/

Autocomplete addresses and POIs

POST

/directions/

Turn-by-turn directions

POST

/isochrone/

Reachability contours

POST

/matrix/

Travel-time and distance matrix

POST

/optimization/

Optimise stop order

GET

/styles/

Fetch a vector map style

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring MapAtlas by hand means appending its token query parameter to every call and shaping routing bodies with locations and a costing mode. Through Jentic you install once, import the MapAtlas API from the API Directory, store the token once, and your agent calls it.

Permission scoping

MapAtlas takes locations in query parameters and request bodies, not in the URL path, so rules bound which operations your agent may call, not which places. Limit the agent to the operations it needs, such as geocoding only, and leave matrix or optimisation out unless you add them.

Credential isolation

Your MapAtlas token 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.

Intent-based discovery

Agents search Jentic by intent such as 'geocode an address' or 'draw a drive-time isochrone', and Jentic returns the matching MapAtlas operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using MapAtlas API through Jentic.

Is there a MapAtlas MCP server?

You don't need an MCP server to give your agent the MapAtlas API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it. Geocoding and routing operations are found by intent when needed, so no extra tool definitions sit in the agent's context.

What authentication does the MapAtlas API use?

Per its OpenAPI spec, the MapAtlas API authenticates with an API token passed as the token query parameter, issued from the keys page of the MapMetrics portal. Through Jentic the token is stored encrypted by your own Jentic One instance and appended at call time, so it never appears in the agent's prompt or in URLs it logs.

Which travel modes does MapAtlas routing support?

Routing operations take a costing value from the spec's enum: auto, bicycle, bus, truck, taxi, motor_scooter, pedestrian, and bikeshare. The same costing field applies to directions, isochrone, matrix, optimisation, and map matching requests.

Can I limit what my agent is allowed to do with the MapAtlas API?

Yes. Write a rule that allows only GET /forward-geocode/ and GET /reverse-geocode/, so an address-lookup agent can resolve places but cannot run matrix or optimisation jobs you did not plan for. Every call it makes runs through your own instance.

What are the rate limits for the MapAtlas API?

The OpenAPI spec does not specify rate limits. Check your plan in the MapMetrics portal at https://portal.mapmetrics.org/keys for current limits.

How do I geocode an address with the MapAtlas API through Jentic?

Add the MapAtlas API to Jentic One from the directory and store your token once. Your agent searches for 'geocode an address to coordinates', calls GET /forward-geocode/ with the text parameter, and can narrow results with boundary.country. To run it on your own infrastructure, install Jentic One from its GitHub repo.

MapAtlas API

AI ReadinessNon-Ready (F)39/100

See full scorecard

Official vendor OpenAPI document · agent-readyMaps GeolocationGeocodingapiKey10 EndpointsREST

For Agents

Geocode and reverse geocode places in Europe and beyond, autocomplete addresses, and compute directions, isochrones, matrices, stop optimisation, map matching, and elevation on OpenStreetMap data.

Use for: I need to convert this street address in Berlin into coordinates, Find the address at latitude 48.8566 and longitude 2.3522, Get cycling directions from Amsterdam Centraal to the Rijksmuseum, Show the area reachable within 15 minutes by car from our warehouse

Not supported: Does not handle live traffic incidents, public transit timetables, or business reviews. Use for OpenStreetMap geocoding, routing, and elevation only.

The MapAtlas API geocodes addresses, reverse geocodes coordinates, and calculates routes on an OpenStreetMap-based platform that runs on EU infrastructure. Beyond forward, reverse, and autocomplete search it returns turn-by-turn directions, isochrone reachability contours, travel-time and distance matrices, optimised stop orders, map-matched GPS traces, and terrain elevation along a shape. Routing calls take a costing mode such as auto, bicycle, truck, or pedestrian, and a styles call serves vector map style JSON for MapLibre GL or Mapbox GL.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: C-Signals: 4

90%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

17%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

16%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

50%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

52%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1

15%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B+Signals: 1

69%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the MapAtlas API to your agent

Capabilities

Start building with MapAtlas API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

MapAtlas API

Jentic AI Readiness Score

MapAtlas API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness