Install Jentic One Beta

Connect the MapQuest API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the MapQuest 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%2Fmapquest.com%2Fmapquest" | 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%2Fmapquest.com%2Fmapquest" | 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 MapQuest API.

Forward geocode an address into latitude and longitude coordinates

Reverse geocode coordinates back into a structured address

Batch geocode a list of addresses in a single request

Calculate a route between locations and return alternate routes

Optimise the order of stops on a multi-stop route

GET STARTED

Start building with MapQuest API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use MapQuest API for, with concrete tasks.

★ Location tools for an AI agent

Give an AI agent the ability to geocode addresses, calculate routes, and search for places without hand-wiring the MapQuest key query parameter. Through Jentic the agent discovers the geocoding, directions, and search operations by intent and calls them with a validated input schema, so a logistics or travel assistant can turn 'where is this address' and 'what is the fastest route' into concrete answers.

Geocode a customer address, then calculate the driving route from the depot to that coordinate and return the distance and estimated time

Address geocoding and cleanup

Convert user-entered addresses into coordinates and reverse geocode raw coordinates back into structured addresses. The batch endpoint processes a list of addresses in one request, which is useful for cleaning imported customer data or enriching a dataset with location detail.

Batch geocode a list of 40 delivery addresses and flag any that fail to resolve to a coordinate

Route planning and optimisation

Calculate routes between locations, return alternate routes, optimise the order of stops on a multi-stop trip, and build a route matrix of travel times between many points. Route shape geometry lets a tool draw the path, so a delivery or field-service app can plan and display efficient routes.

Optimise a route that visits six stops and return the ordered sequence with total distance and time

Place search and autocomplete

Search for places by name and offer predictive search-ahead suggestions as a user types. The place-search and prediction operations back store locators, destination pickers, and in-app search boxes that need to resolve a typed query to a real location.

Return predictive place suggestions for the partial query 'San Fran' and resolve the top result to coordinates

Key Endpoints

15 endpoints — the mapquest api converts addresses into coordinates, reverse geocodes coordinates back into addresses, and geocodes lists of locations in a single batch call.

METHOD

PATH

DESCRIPTION

GET

/geocoding/v1/address

Forward geocode an address

GET

/geocoding/v1/reverse

Reverse geocode coordinates

GET

/geocoding/v1/batch

Batch geocode a list of addresses

GET

/directions/v2/route

Calculate a route between locations

GET

/directions/v2/optimizedroute

Optimise a multi-stop route

POST

/directions/v2/routematrix

Build a route matrix between points

GET

/geocoding/v1/address

Forward geocode an address

GET

/geocoding/v1/reverse

Reverse geocode coordinates

GET

/geocoding/v1/batch

Batch geocode a list of addresses

GET

/directions/v2/route

Calculate a route between locations

GET

/directions/v2/optimizedroute

Optimise a multi-stop route

POST

/directions/v2/routematrix

Build a route matrix between points

Why Jentic?

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

Setup

Wiring the MapQuest API by hand means appending your key to the `key` query parameter on every request and choosing between its GET and POST forms for geocoding and routing. Through Jentic you install once, import MapQuest from the API Directory, store the key once, and your agent calls the geocoding, directions, and search operations directly.

Permission scoping

You choose the operations your agent may call, so you can allow geocoding and route calculation while leaving out static-map rendering or search. Because the address and route parameters travel in the request rather than a resource id in the path, rules bound which operations run, not which place is queried.

Credential isolation

Your MapQuest 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.

Intent-based discovery

Agents search Jentic by intent such as 'geocode an address' or 'calculate a route', and Jentic returns the matching MapQuest operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using MapQuest API through Jentic.

What authentication does the MapQuest API use?

The MapQuest API authenticates with an API key passed as the `key` query parameter on each request, per its OpenAPI spec. You obtain a key from the MapQuest developer portal. Through Jentic the key is stored once and injected at call time, so your agent never places it in the query string itself.

Can I geocode and reverse geocode addresses with the MapQuest API?

Yes. The forward geocoding endpoint turns an address into coordinates, the reverse endpoint turns coordinates back into a structured address, and the batch endpoint handles a list of addresses in one request. This supports both interactive lookups and bulk address cleanup.

Is there a MapQuest MCP server?

You do not need an MCP server to give your agent the MapQuest API. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the geocoding, directions, and search operations on demand. Nothing extra runs, and no server tool definitions sit in the agent's context between calls.

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

Yes. Write a rule that allows only the operations you need, such as geocoding and route calculation, so the agent can look up locations and plan trips but cannot call anything you have not listed. Every call it makes is logged, so you can audit exactly which operations ran.

What are the rate limits for the MapQuest API?

The OpenAPI spec does not specify rate limits. Limits depend on your MapQuest plan, so check the developer documentation at https://developer.mapquest.com/documentation/ for the transaction quota that applies to your key.

How do I calculate a route with the MapQuest API through Jentic?

Search Jentic for 'calculate a driving route' to find the route operation, which returns distance, time, and turn guidance between locations, and pair it with the geocoding operation to convert addresses to coordinates first. Jentic returns each operation with its input schema so your agent calls it correctly. To run it on your own infrastructure, install Jentic One from its GitHub repo.

MapQuest API

AI ReadinessFoundational (D+)47/100

See full scorecard

Official vendor OpenAPI document · agent-readyMaps GeolocationGeocodingapiKey15 EndpointsREST

For Agents

Geocode and reverse geocode addresses, batch geocode lists of locations, calculate and optimise routes, build a route matrix, and search for places with predictive suggestions. Returns coordinates, addresses, and route geometry.

Use for: I need to geocode a street address into coordinates, Reverse geocode a coordinate into an address, Batch geocode a list of customer addresses, Calculate the driving route between two locations

Not supported: Does not host business listings or reviews, provide live traffic incident feeds, or render interactive map tiles beyond the static-map endpoint. Use for geocoding, routing, and place search.

The MapQuest API converts addresses into coordinates, reverse geocodes coordinates back into addresses, and geocodes lists of locations in a single batch call. It calculates routes between points, optimises the order of stops on a multi-stop trip, returns alternate routes and a route matrix, and produces route shape geometry for drawing a path. Place search and predictive search-ahead operations back location lookups, and a static map endpoint renders a map image.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

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

100%

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.

47%

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: D+Signals: 4

32%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

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

58%

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: A-Signals: 1

75%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the MapQuest API to your agent

Capabilities

Start building with MapQuest API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

MapQuest API

Jentic AI Readiness Score

MapQuest 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