Atlasfetch Xyz AtlasFetch
64
AI ReadinessAI-Aware (B)64/100
Official vendor OpenAPI document · agent-readyMaps GeolocationGeocodingbearer17 EndpointsREST
For Agents
Reverse geocode coordinates to administrative areas, match them against custom boundary sets, and route between points. Returns structured JSON over a bearer-authenticated REST API, with a few public endpoints that need no key.
Use for: I want to reverse geocode a latitude and longitude to its administrative region, Check which of my boundary sets contain a given point, Create a boundary set and upload a polygon for geofencing, Find the nearest street and house number for a coordinate
Not supported: Does not do forward geocoding, place search, map tiles, or guaranteed house numbers. Use for reverse geocoding, boundary matching, and routing only.
The AtlasFetch API resolves a coordinate to the country, region, and municipality that contain it, and matches it against your own uploaded boundary sets, in a single call. It can also return the nearest street and house number worldwide where coverage exists, and route between two or more coordinates. Boundary endpoints let you create sets, add polygons, and read your geometry back for geofencing and jurisdiction checks.
Install Jentic One Beta
Connect the AtlasFetch to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AtlasFetch, 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%2Fatlasfetch.xyz%2Fatlasfetch" | 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%2Fatlasfetch.xyz%2Fatlasfetch" | 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 AtlasFetch API.
Reverse geocode a coordinate to the country, region, and municipality that contain it
Match a coordinate against your own uploaded boundary sets in one lookup
Return the nearest street and house number for a coordinate where coverage exists
Create and populate boundary sets with polygons for geofencing
Route between two or more coordinates and read routing coverage per plan
Use Cases
Patterns agents use AtlasFetch API for, with concrete tasks.
★ AI Agent Geolocation Integration via Jentic
An agent that enriches locations or checks jurisdictions can call AtlasFetch through Jentic without wiring the bearer key or learning which endpoints are public. The agent searches by intent, receives the operation schema, and submits a coordinate to get back administrative areas and boundary matches. This fits logistics, compliance, and mapping agents that need region context rather than a full map stack.
Search Jentic for 'reverse geocode a coordinate', load the operation schema, and call it with a latitude and longitude to receive the containing region
Reverse Geocoding to Administrative Areas
Turn a raw coordinate into the country, region, and municipality that contain it. AtlasFetch answers in one lookup and can add the nearest street and house number where its street layer covers the country, which suits enriching event or sensor data with place names and region codes.
Call GET /location/lookup with a latitude and longitude to get the country, region, and municipality
Geofencing Against Custom Boundaries
Define your own polygons as boundary sets and test whether a point falls inside any of them in the same lookup that resolves administrative areas. This lets a delivery or territory agent check a coordinate against sales regions, service zones, or restricted areas without a separate geospatial service.
Call POST /boundaries/sets to create a set, then POST /boundaries to add a polygon the agent can match points against
Point-to-Point Routing
Compute a route between two or more coordinates and check the routing coverage and limits for your plan. A dispatch agent can request the route between a pickup and drop-off, with coverage reported per plan so it degrades gracefully where routing is unavailable.
Call POST /route with two coordinates to get the route between them
Key Endpoints
17 endpoints — the atlasfetch api resolves a coordinate to the country, region, and municipality that contain it, and matches it against your own uploaded boundary sets, in a single call.
METHOD
PATH
DESCRIPTION
GET
/location/lookup
Resolve a coordinate to the boundaries that contain it
GET
/boundaries/sets
List the account's boundary sets
POST
/boundaries/sets
Create a boundary set
POST
/boundaries
Add a polygon to a boundary set
GET
/boundaries/view
Read back your boundaries with geometry
POST
/route
Route between two or more coordinates
GET
/streets/coverage
Countries covered by the street layer
GET
/location/lookup
Resolve a coordinate to the boundaries that contain it
GET
/boundaries/sets
List the account's boundary sets
POST
/boundaries/sets
Create a boundary set
POST
/boundaries
Add a polygon to a boundary set
GET
/boundaries/view
Read back your boundaries with geometry
POST
/route
Route between two or more coordinates
GET
/streets/coverage
Countries covered by the street layer
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.
A
AtlasFetch
- AI-Aware (B)64/100
93
Foundational Compliance62
Developer Experience & Jentic Compatibility43
AI-Readiness & Agent Experience94
Agent Usability60
Security74
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.
62
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
5%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
43%
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.
43
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: D-Signals: 4
47%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
71%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
55%
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.
60
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
60%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
74
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A-Signals: 1
74%
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 AtlasFetch API by hand means managing its bearer key, calling the right lookup, boundary, or route endpoint, and handling the public endpoints that need no key. Through Jentic you install once, import AtlasFetch from the API Directory, store the key once, and your agent calls it.
Permission scoping
AtlasFetch puts the boundary-set name and boundary id in the URL path (/boundaries/sets/{name}, /boundaries/{id}), so a rule can pin your agent to the sets and operations you pick. You choose the operations it may call, so destructive ones like deleting a set or a boundary are not included unless you add them.
Credential isolation
Your AtlasFetch 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 'reverse geocode a coordinate' or 'route between two points', and Jentic returns the matching AtlasFetch operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using AtlasFetch API through Jentic.
Is there an AtlasFetch MCP server?
You don't need a separate MCP server to give your agent the AtlasFetch API. Jentic connects it directly from the API Directory: import it, store your bearer key once, and your agent calls the lookup, boundary, and routing operations it needs.
Can I limit what my agent is allowed to do with the AtlasFetch API?
Yes. Write a rule that allows the coordinate lookup and route operations plus reads on one boundary set by name, and the agent can resolve coordinates and read that set while deleting a set or a boundary stays out of reach. Every call is logged by your self-hosted instance.
What authentication does the AtlasFetch API use?
The AtlasFetch API authenticates with a bearer API key sent in the Authorization header, per its OpenAPI spec. Public endpoints such as health, version, and the plan catalogue need no credential, while lookups, boundary writes, and routing require the key. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time.
Can I match a coordinate against my own boundaries with the AtlasFetch API?
Yes. Upload polygons into a boundary set, then a single coordinate lookup returns both the administrative areas and any of your boundary sets that contain the point. This supports jurisdiction checks and geofencing in one call.
What are the rate limits for the AtlasFetch API?
The OpenAPI spec does not specify fixed rate limits; routing limits are reported per plan by the route coverage endpoint. Check the vendor's documentation at https://atlasfetch.xyz for current limits and plan tiers.
How do I reverse geocode a coordinate with the AtlasFetch API through Jentic?
Search Jentic for 'reverse geocode a coordinate' and it returns the AtlasFetch lookup operation with its input schema; supply a latitude and longitude and the agent receives the containing region and any boundary matches. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED