Mapserv Utah Gov Utah UGRC Web API
Official vendor OpenAPI document · agent-readyMaps GeolocationGeocodingapiKey6 EndpointsREST
For Agents
Geocode Utah street addresses, reverse geocode coordinates, locate route mileposts, and search Utah's SGID spatial database by feature class and fields. Returns coordinates, matched addresses, and spatial feature attributes for Utah.
Use for: I need to geocode a Utah street address into coordinates, Reverse geocode a coordinate to the nearest Utah address, Find the location of a milepost on a Utah state route, Search Utah SGID data for a set of spatial features
Not supported: Covers Utah geographic data only; does not geocode addresses outside Utah, render map tiles, or provide routing and directions. Use for Utah geocoding and SGID spatial search.
The Utah UGRC Web API geocodes Utah street addresses into coordinates, reverse geocodes coordinates back into the nearest address, and locates a point along a state route by milepost. It also searches the State Geographic Information Database (SGID) for spatial features, lists the available feature class names, and lists the attribute field names on a given feature class. It is focused on Utah geographic data rather than worldwide coverage.
Install Jentic One Beta
Connect the Utah UGRC Web API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Utah UGRC Web 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%2Fmapserv.utah.gov%2Futah-agrc" | 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%2Fmapserv.utah.gov%2Futah-agrc" | 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 Utah UGRC Web API.
Geocode a Utah street address and zone into latitude and longitude coordinates
Reverse geocode a coordinate into the nearest Utah address
Locate a point along a state route by route number and milepost
Search the Utah SGID spatial database for features by table and fields
List the available SGID feature class names
List the attribute field names on a given feature class
Use Cases
Patterns agents use Utah UGRC Web API for, with concrete tasks.
★ Utah location tools for an AI agent
Give an AI agent the ability to geocode Utah addresses and query the state's spatial database without hand-wiring the UGRC apikey query parameter. Through Jentic the agent discovers the geocoding and search operations by intent and calls them with a validated input schema, so a state or civic assistant can turn 'where is this Utah address' and 'what district is it in' into concrete answers grounded in official Utah data.
Geocode a Salt Lake City street address, then search the SGID for the voting precinct that contains the resulting coordinate
Utah address geocoding
Convert Utah street addresses into coordinates and reverse geocode coordinates back into the nearest address. The geocoder is tuned to Utah's official address data, so it is a strong fit for state agencies, utilities, and local governments that need accurate in-state geocoding rather than a generic worldwide service.
Reverse geocode a list of field-inspection coordinates into the nearest Utah street addresses
SGID spatial data search
Query the State Geographic Information Database for spatial features, discover which feature classes are available, and inspect the attribute fields on each. This lets a tool answer boundary and jurisdiction questions, such as which district, precinct, or service area a point falls in, using Utah's authoritative data layers.
List the SGID feature classes, then search the boundaries layer for the county that contains a given coordinate
Route and milepost location
Locate a point along a Utah state route by route number and milepost, which is useful for transportation, incident-reporting, and asset-management tools that reference locations by route and milepost rather than by street address.
Find the coordinate of milepost 310 on Interstate 15 and return its latitude and longitude
Key Endpoints
6 endpoints — the utah ugrc web api geocodes utah street addresses into coordinates, reverse geocodes coordinates back into the nearest address, and locates a point along a state route by milepost.
METHOD
PATH
DESCRIPTION
GET
/geocode/{street}/{zone}
Geocode a Utah street address
GET
/geocode/reverse/{x}/{y}
Reverse geocode coordinates
GET
/geocode/milepost/{route}/{milepost}
Geocode a route and milepost
GET
/search/{table}/{fields}
Search SGID spatial data
GET
/info/featureClassNames
List feature class names
GET
/info/fieldnames/{tableName}
List feature class attributes
GET
/geocode/{street}/{zone}
Geocode a Utah street address
GET
/geocode/reverse/{x}/{y}
Reverse geocode coordinates
GET
/geocode/milepost/{route}/{milepost}
Geocode a route and milepost
GET
/search/{table}/{fields}
Search SGID spatial data
GET
/info/featureClassNames
List feature class names
GET
/info/fieldnames/{tableName}
List feature class attributes
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Utah UGRC Web API by hand means appending your key to the `apikey` query parameter on every request and templating address, coordinate, and layer segments into the path. Through Jentic you install once, import the UGRC Web API from the API Directory, store the key once, and your agent calls the geocoding and SGID search operations directly.
Permission scoping
You choose the operations your agent may call, so you can allow geocoding and feature-class listing while leaving out anything you have not listed. Because the address and search parameters travel in the path and query rather than as a mutable resource id, rules bound which operations run, not which record is changed.
Credential isolation
Your UGRC 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 a Utah address' or 'search Utah spatial data', and Jentic returns the matching UGRC operation with its input schema so the agent calls the right endpoint without reading the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Utah UGRC Web API through Jentic.
What authentication does the Utah UGRC Web API use?
The Utah UGRC Web API authenticates with an API key passed as the `apikey` query parameter on each request, per its OpenAPI spec. You obtain a key from the UGRC 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 Utah addresses with the Utah UGRC Web API?
Yes. The geocoding endpoint converts a Utah street address and zone into coordinates, the reverse endpoint turns coordinates back into the nearest address, and the milepost endpoint locates a point along a state route. The geocoder uses Utah's official address data, so it is accurate for in-state addresses.
Is there a Utah UGRC MCP server?
You do not need an MCP server to give your agent the Utah UGRC Web API. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the geocoding and SGID 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 Utah UGRC Web API?
Yes. Write a rule that allows only the operations you need, such as geocoding and feature-class listing, so the agent can look up addresses and inspect layers but cannot call anything you have not listed. Every call it makes is logged, so you can audit exactly which operations ran.
What data does the Utah UGRC SGID search cover?
The search operation queries the State Geographic Information Database, Utah's authoritative collection of spatial data layers. You can list the available feature classes and their attribute fields, then search a layer for features. Coverage is limited to Utah rather than worldwide.
How do I search Utah spatial data through Jentic?
Search Jentic for 'search Utah spatial data' to find the SGID search operation, which returns matching features from a chosen layer, and pair it with the feature-class listing to discover which layers exist 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.
GET STARTED