76
/100
prowl
Benchmarked May 05, 2026

City, Helsinki

Helsinki(FI) City Open Data

data platform_profile
Benchmark Your API

Score Breakdown

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

Benchmark Analysis Log

Full LLM thinking from the 4-phase benchmark pipeline.

Analyze
```json
{
  "service_type": "platform",
  "base_url": "https://hri.fi/en_gb",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "free",
    "details": {}
  },
  "rate_limits": {},
  "capabilities": [
    "Access open data sets",
    "Download data in various formats",
    "Browse and search data sets",
    "Data visualization resources",
    "APIs for developers"
  ],
  "raw_analysis": "The platform, Helsinki Region Infoshare (HRI), provides access to the city of Helsinki's open data. It is intended for individuals, developers, researchers, and companies who are interested in utilizing public data provided by the city for various purposes, such as application development, urban planning, or academic research. This platform is quite mature, reflecting a comprehensive regional effort to promote transparency and innovation through open data. The HRI platform offers not only downloadable datasets in multiple formats but also APIs to facilitate the development of applications and services. While HRI does not utilize a classic REST API model for communication, it supports developers with APIs to engage with the data more interactively. Directed towards a broad audience, from local Finnish residents to international researchers, HRI is a part of open data initiatives worldwide. The platform is free to use, which encourages wide participation and integration. Though comprehensive in scope, specific details about rate limiting (e.g., API call limits) aren't explicitly documented, suggesting there might be none or that they are incorporated in developer-friendly ways. No authentication is needed to access the fundamental features, showcasing its openness and accessibility."
}
```
Execute

1/3 tests passed

TestEndpointStatusLatency
website_uptimeGET /2002028ms
robots_txtGET /robots.txt404267ms
llms_txtGET /llms.txt404258ms
Interpret
```json
{
  "overall": 71,
  "dimensions": {
    "token_efficiency": 8.0,
    "first_try_success": 8.0,
    "response_parseability": 7.5,
    "error_clarity": 6.5,
    "doc_quality": 8.0,
    "auth_simplicity": 9.0,
    "latency": 4.0,
    "consistency": 8.0
  },
  "pricing_normalized": {
    "type": "free",
    "details": {}
  },
  "issues": [
    "High latency detected (>2s in one of the tests).",
    "No robots.txt or llms.txt files found, indicating potential issues with well-structured SEO or other integrations."
  ],
  "recommendations": [
    "Improve the website's response time to enhance user experience.",
    "Consider adding robots.txt and llms.txt files to streamline SEO practices and integration capabilities."
  ]
}
```

Agent Readiness

x402 Payments
Not supported
Streaming
No
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