Install Jentic One Beta

Connect the Utah AGRC Web API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Utah AGRC 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.

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%2Fmapserv-utah-main" | 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%2Fmapserv.utah.gov%2Fmapserv-utah-main" | 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 Utah AGRC Web API.

Geocode a Utah street address to coordinates with /geocode/{street}/{zone} including locator scoring

Reverse geocode an x,y coordinate pair into the closest Utah address through /geocode/reverse/{x}/{y}

Resolve a milepost on a Utah state route to coordinates via /geocode/milepost/{route}/{milepost}

Run a spatial or attribute query across any SGID feature class with /search/{table}/{fields}

GET STARTED

Start building with Utah AGRC Web API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Utah AGRC Web API for, with concrete tasks.

★ Utah Address Validation and Geocoding

Civic and government products operating inside Utah call /geocode/{street}/{zone} to validate residency on application forms, voter records, and benefits portals. The endpoint returns a match score and the matched address components so a form can flag uncertain hits for manual review. Integration is typically a half-day for a single form.

Call /geocode/123 Main Street/Salt Lake City and return the coordinate with the locator score, flagging the result if the score is below 80.

Highway Milepost to Coordinate Conversion

Transport, emergency response, and incident reporting tools call /geocode/milepost/{route}/{milepost} to convert mile markers reported by drivers, troopers, or maintenance crews into latitude/longitude. This is the only endpoint of its kind in Utah and replaces brittle internal lookup tables. Wiring it in is a few hours of work.

Call /geocode/milepost/I-15/318 and return the latitude and longitude of milepost 318 on Interstate 15.

SGID Spatial Layer Lookups

Real estate, civic engagement, and analytics applications use /search/{table}/{fields} against any of the 300+ SGID feature classes to enrich a Utah address with parcel, school, voting, or land-use attributes. The endpoint accepts attribute filters or geometry envelopes and returns matching features. Field-name discovery is supported by /info/fieldnames so a query can be built without reading the source dataset documentation.

Call /info/fieldnames/SchoolBoundaries to discover the schema, then /search/SchoolBoundaries/NAME with a point-in-polygon filter for a customer's coordinate to return the school district name.

Reverse Geocoding for Utah Field Apps

Inspection and field-services apps used by Utah agencies call /geocode/reverse/{x}/{y} to convert a captured GPS coordinate back to the closest street address. The endpoint returns the matched address, distance to the input coordinate, and locator confidence. Integration takes a few hours behind a mobile app's check-in handler.

Call /geocode/reverse/-111.8910/40.7608 and return the matched street address with the distance offset in metres.

AI Agent for Utah Civic Workflows

An AI agent automating constituent services, address verification, or routing inside Utah calls the AGRC Web API through Jentic to geocode addresses and resolve them against SGID layers. Jentic exposes each AGRC operation as a typed tool with a discoverable input schema so the agent never has to read api.mapserv.utah.gov directly. Setup runs through search, load, and execute in under an hour.

Search Jentic for 'geocode an address in Utah', load the schema for /geocode/{street}/{zone}, and execute the call for '350 N State St' in zone 'Salt Lake City'.

Key Endpoints

6 endpoints — jentic publishes the only available openapi specification for utah agrc web api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/geocode/{street}/{zone}

Geocode a Utah street address

GET

/geocode/reverse/{x}/{y}

Reverse geocode a coordinate

GET

/geocode/milepost/{route}/{milepost}

Resolve a Utah highway milepost to coordinates

GET

/search/{table}/{fields}

Query an SGID feature class

GET

/info/featureClassNames

List all available SGID feature classes

GET

/info/fieldnames/{tableName}

List fields for a feature class

GET

/geocode/{street}/{zone}

Geocode a Utah street address

GET

/geocode/reverse/{x}/{y}

Reverse geocode a coordinate

GET

/geocode/milepost/{route}/{milepost}

Resolve a Utah highway milepost to coordinates

GET

/search/{table}/{fields}

Query an SGID feature class

GET

/info/featureClassNames

List all available SGID feature classes

GET

/info/fieldnames/{tableName}

List fields for a feature class

Why Jentic?

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

Setup

Wiring the Utah AGRC Web API by hand means appending its apikey query parameter, learning the /geocode, /search, and /info path segments, and handling the SGID table and field lookups yourself. Through Jentic you install once, import the Utah AGRC Web API from the API Directory, store the key once, and your agent calls it.

Permission scoping

The Utah AGRC endpoints are read-only geocode and spatial-search lookups, so scoping is by operation: you limit the agent to the operations it needs, such as geocoding an address, reverse geocoding coordinates, or searching an SGID table, and leave out the rest. Every operation you allow is one you have chosen, so the agent stays inside that set.

Credential isolation

Your Utah AGRC 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 an SGID table', and Jentic returns the matching Utah AGRC operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Utah AGRC Web API through Jentic.

Why is there no official OpenAPI spec for Utah AGRC Web API?

Utah Geospatial Resource Center does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Utah AGRC Web API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Utah AGRC Web API use?

The API uses a UGRC-issued API key passed as the `apikey` query parameter. Jentic stores the key encrypted in your Jentic One instance and appends it to each request at execution time so the raw key never enters the agent context.

Can I geocode an address outside Utah with this API?

No. The Utah AGRC Web API is scoped to addresses, mile markers, and SGID feature classes inside the state of Utah. For nationwide US geocoding pair this API with a national geocoder such as Geocodio.

What are the rate limits for the Utah AGRC Web API?

UGRC enforces per-key quotas rather than a published per-second rate limit. Quotas vary by access tier and can be reviewed in the UGRC developer console; requests beyond the quota return an HTTP 429 response.

How do I look up a school district for a Utah address through Jentic?

Run `pip install jentic`, then chain two operations: first /geocode/{street}/{zone} to convert the address to a coordinate, then /search/SchoolBoundaries/NAME with a point filter on that coordinate. Jentic returns the matching feature attributes.

What spatial datasets are searchable through this API?

The /info/featureClassNames endpoint lists every SGID feature class exposed by /search, covering 300+ datasets including parcels, roads, schools, voting precincts, and land use. Use /info/fieldnames/{tableName} to discover the queryable fields on each one.

Can I limit what my agent is allowed to do with the Utah AGRC Web API?

Yes. Because you run Jentic One yourself, your own rules decide which Utah AGRC operations the agent may call, so you can allow only geocoding a street address, reverse geocoding a coordinate, resolving a highway milepost, or searching an SGID feature class, and leave the rest out. Every one of these endpoints is a read-only lookup, so the agent can never write or change data no matter what it calls. The API key stays stored by your own instance and is added at execution time, so the agent uses it only on the operations you have permitted.

Mapserv Utah Gov Utah AGRC Web API

Browse all Mapserv Utah Gov APIs

AI ReadinessFoundational (D+)49/100

See full scorecard

Agent-ready OpenAPI document · curated by JenticMaps GeolocationGeocodingapiKey6 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Geocode Utah addresses, reverse-geocode coordinates, look up positions on Utah highway mileposts, and query 300+ Utah SGID spatial layers through six endpoints. Authentication is an API key in the query string.

Use for: I need to geocode a Salt Lake City street address to latitude and longitude, Find the nearest Utah address for a GPS coordinate captured by a field worker, Get the coordinate at milepost 254 on Utah State Route 24, Search the SGID parcel layer for the parcel containing a given coordinate

Not supported: Does not handle routing, turn-by-turn directions, addresses outside Utah, or static map rendering - use for Utah geocoding and SGID spatial search only.

Jentic publishes the only available OpenAPI specification for Utah AGRC Web API, keeping it validated and agent-ready. The Utah Geospatial Resource Center (UGRC) Web API exposes statewide geocoding, reverse geocoding, milepost geocoding, and spatial searching across more than 300 SGID (State Geographic Information Datasource) data layers covering parcels, roads, addresses, schools, voting precincts, and other Utah-specific reference data. The API authenticates with an `apikey` query parameter and is designed for civic, real-estate, transport, and field-services applications operating inside Utah.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

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.

50%

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: C-Signals: 4

52%

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.

50%

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: ASignals: 1

83%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Utah AGRC Web API to your agent

Capabilities

Start building with Utah AGRC Web API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Mapserv Utah Gov Utah AGRC Web API

Jentic AI Readiness Score

Utah AGRC Web 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