OpenTripMap API
46
AI ReadinessFoundational (D)46/100
Agent-ready OpenAPI document · curated by JenticMaps GeolocationPlaces And Points Of Interestapikey5 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Find points of interest by radius, bounding box, or place name and retrieve place detail from OpenTripMap.
Use for: Find attractions near a coordinate, List points of interest in a map area, Find places near a named city, Suggest places matching a partial name
Not supported: Does not provide routing or turn-by-turn navigation. Use it to find points of interest by radius, bounding box, or name, autosuggest places, and retrieve place detail.
OpenTripMap is a places API for points of interest: an agent can find attractions within a radius of a coordinate, inside a bounding box, or near a named place, autosuggest places by partial name, and pull the full detail for one place by its identifier. It suits travel and mapping assistants that need to surface things to see near a location. The API is read-only and returns tourist and geographic points of interest.
Install Jentic One Beta
Connect the OpenTripMap API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the OpenTripMap 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.
1
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%2Fopentripmap.com%2Fopentripmap" | sh2
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%2Fopentripmap.com%2Fopentripmap" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 OpenTripMap API.
Find points of interest within a radius of a coordinate
Find points of interest inside a bounding box
Find points of interest near a named place
Autosuggest places by partial name
Retrieve full detail for a place by its identifier
Use Cases
Patterns agents use OpenTripMap API for, with concrete tasks.
★ Nearby Attractions
A travel agent surfaces things to see around a user by calling GET /places/radius with a coordinate and distance. This answers 'what is near me' without a separate mapping service.
Find nearby points of interest with GET /places/radius for the coordinate
Map Area Search
When a map view defines a region, an agent lists what is inside it with GET /places/bbox for the bounding box. This populates a map with attractions as the user pans and zooms.
List places in the view with GET /places/bbox for the bounding box
Place Detail
After a user picks a result, an agent reads its full record with GET /places/xid/{xid}, including description and attributes. This backs a detail card without a second data source.
Retrieve full detail with GET /places/xid/{xid} for the selected place
Autosuggest by Name
As a user types, an agent offers matches with GET /places/autosuggest so it can resolve a partial name to a place. This drives a responsive search box for destinations.
Offer matches with GET /places/autosuggest for the partial name
Key Endpoints
5 endpoints — opentripmap is a places api for points of interest: an agent can find attractions within a radius of a coordinate, inside a bounding box, or near a named place, autosuggest places by partial name, and pull the full detail for one place by its identifier.
METHOD
PATH
DESCRIPTION
GET
/places/radius
Find places within a radius
GET
/places/bbox
Find places inside a bounding box
GET
/places/geoname
Find places near a named place
GET
/places/autosuggest
Autosuggest places by partial name
GET
/places/xid/{xid}
Retrieve place detail by id
GET
/places/radius
Find places within a radius
GET
/places/bbox
Find places inside a bounding box
GET
/places/geoname
Find places near a named place
GET
/places/autosuggest
Autosuggest places by partial name
GET
/places/xid/{xid}
Retrieve place detail by id
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
O
OpenTripMap API
- Foundational (D)46/100
93
Foundational Compliance59
Developer Experience & Jentic Compatibility42
AI-Readiness & Agent Experience94
Agent Usability15
Security75
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
93
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).
75%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
59
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: C+Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
35%
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.
42
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: D-Signals: 4
39%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
80%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
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.
15
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).
75
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A-Signals: 1
75%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the OpenTripMap API by hand means passing the API key as a query parameter, learning its 5 operations for radius, bounding box, geoname, autosuggest, and place detail against https://api.opentripmap.com/0.1/en. Through Jentic you install once, import the OpenTripMap API from the API Directory, store the credential once, and your agent calls it.
Permission scoping
Because you run Jentic One yourself, you decide which OpenTripMap operations the agent may call. Every operation is a read, so you can expose only the search endpoints and leave the rest out of the allowed set unless you add them.
Credential isolation
Your OpenTripMap API key is stored once, encrypted, by your own Jentic One instance and added as the apikey query parameter at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent, such as 'find attractions near a coordinate' or 'get the detail for a place', and Jentic returns the matching OpenTripMap operation with its input schema so the agent calls the right endpoint.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using OpenTripMap API through Jentic.
What can an AI agent do with the OpenTripMap API?
An agent can find points of interest within a radius, inside a bounding box, or near a named place, autosuggest places by partial name, and retrieve the full detail for a place by its identifier. It is a read-only places and attractions source.
What authentication does the OpenTripMap API use?
The specification declares an apiKey scheme that passes the API key as a query parameter named apikey. Through Jentic that key is held by your own instance and added to the request at execution time.
How does an agent find attractions near a user?
It calls GET /places/radius with a coordinate and a distance to list nearby points of interest, then GET /places/xid/{xid} for detail on any the user picks. The two together drive a nearby-attractions view.
Is there an MCP server for the OpenTripMap API?
You do not need a separate MCP server to use the OpenTripMap API with an agent. Through Jentic One, the self-hosted execution layer, your agent calls the operations directly after you import them from the API Directory. Install Jentic One from github.com/jentic/jentic-one to run it yourself.
How does my agent discover OpenTripMap operations through Jentic?
Agents search Jentic by intent, such as 'find attractions near a coordinate', and Jentic returns the matching operation with its input schema. The agent then calls the right endpoint without reading the full reference.
Can I limit what my agent is allowed to do with the OpenTripMap API?
Yes. Because you run Jentic One yourself, you decide which OpenTripMap operations the agent may call. Every operation is a read, so you can expose only the search endpoints and leave the rest out of the allowed set unless you add them, so the agent acts only within the operations you permit.
GET STARTED