73
/100
prowl
Benchmarked May 01, 2026

Utah AGRC

Utah Web API for geocoding Utah addresses

api platform_profile Streaming
Benchmark Your API

Score Breakdown

Latency 10/10
Token Efficiency 8/10
Parseability 8/10
Consistency 7/10
Documentation 7/10
Auth Simplicity 7/10
First-Try Success 7/10
Error Clarity 6/10

Benchmark Analysis Log

Full LLM thinking from the 4-phase benchmark pipeline.

Analyze
```json
{
  "service_type": "platform",
  "base_url": "https://api.mapserv.utah.gov",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {}
  },
  "rate_limits": {},
  "capabilities": [
    "geocode Utah addresses",
    "geospatial data services",
    "support for cartographic and mapping analysis"
  ],
  "raw_analysis": "The Utah AGRC (Automated Geographic Reference Center) provides a web API focused on geocoding Utah addresses. This service is part of their efforts to support geographic data and mapping analysis in Utah. It is primarily intended for developers and organizations that need to integrate geocoding capabilities specific to Utah's geographic data into their applications. The platform offers capabilities such as geocoding and geospatial services, but the available documentation does not specify any particular authentication methods or pricing models. As a state-supported service, the details about monetization, rate limiting, or extensive integration capabilities like marketplace addons or partnerships are typically sparse. The platform is mature enough to have its dedicated API, mostly used for public administration, urban planning, or any industry dealing with local geographic data. However, specific integrations might not be directly supported or widely advertised."
}
```
Execute

1/3 tests passed

TestEndpointStatusLatency
website_uptimeGET /20055ms
robots_txtGET /robots.txt40419ms
llms_txtGET /llms.txt40420ms
Interpret
```json
{
  "overall": 72,
  "dimensions": {
    "token_efficiency": 8.0,
    "first_try_success": 7.0,
    "response_parseability": 7.5,
    "error_clarity": 6.0,
    "doc_quality": 7.0,
    "auth_simplicity": 7.0,
    "latency": 9.5,
    "consistency": 7.0
  },
  "pricing_normalized": {},
  "issues": ["No robots.txt", "No llms.txt"],
  "recommendations": [
    "Implement robots.txt for better web crawling and indexing.",
    "Provide a clear pricing model or details on how the service is billed.",
    "Enhance documentation to ensure limitations and requirements are clear."
  ]
}
```

Agent Readiness

x402 Payments
Not supported
Streaming
Yes
Sandbox
None
Agent Auth
Unknown
SDKs
None listed
MCP Support
No

Want the full interactive view?

See operational metrics, LLM evaluations, agent readiness, and more.

Open in Dashboard