canonical: https://jentic.com/apis/atlasfetch.xyz/atlasfetch

# Atlasfetch Xyz AtlasFetch

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.

## For AI 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.

## Scope

Does not do forward geocoding, place search, map tiles, or guaranteed house numbers. Use for reverse geocoding, boundary matching, and routing only.

## Capabilities

- 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

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Call POST /route with two coordinates to get the route between them

## Key endpoints

| 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 |

## Key resources

- **Lookup** — Resolve a coordinate to administrative areas and boundary-set matches
- **Boundary sets** — Create, list, update, and delete sets of polygons
- **Boundaries** — Add, read back, and delete individual polygons
- **Directions** — Route between coordinates and report routing coverage
- **Public** — Health, version, street coverage, demo key, and plan catalogue

## AI readiness

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.

- **Score:** 64 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 62 / 100
  - AI-Readiness & Agent Experience: 43 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 74 / 100
- **View full report:** https://jentic.com/apis/atlasfetch.xyz/atlasfetch/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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

- **Kakao Maps Local API** — Alternative geocoding and local place lookup
- **bng2latlong** — Convert British National Grid references to latitude and longitude
- **Navitia API** — Multimodal transit routing and journey planning

## FAQ

### 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.