RMV API (Public Transport in Hessen)
Full LLM thinking from the 4-phase benchmark pipeline.
{
"service_type": "platform",
"base_url": "https://opendata.rmv.de/site/start.html",
"auth_method": "none",
"auth_config": {},
"endpoints": [],
"pricing_model": {"type": "free", "details": {"license": "Open Data, free to use with attribution"}},
"rate_limits": {},
"capabilities": ["public transport journey planning", "real-time departure information", "timetable data", "stop and station information", "route and line details", "GTFS and GTFS-RT support"],
"raw_analysis": "The RMV Open Data portal provides public transport data for the Rhein-Main area in Hessen, Germany. It offers a REST API (Rhein-Main-Verkehrsverbund) with journey planning, real-time departures, and timetable information. The platform is mature, operated by the regional transit authority, and is part of a broad open data initiative. It requires no authentication for open data endpoints (though some may require a token for higher volume). Documentation is available at the site. Integration examples include using GTFS data with tools like OpenTripPlanner. The platform is free to use under an open data license with attribution. The site is in German, but the API documentation is bilingual. The base URL shown is a landing page; actual API endpoints are under /api/... (e.g., /api/trips, /api/stops, /api/locations). The platform targets developers building transit apps, researchers, and smart city solutions."
}0/3 tests passed
| Test | Endpoint | Status | Latency |
|---|---|---|---|
| website_uptime | GET / | None | 30244ms |
| robots_txt | GET /robots.txt | None | 30392ms |
| llms_txt | GET /llms.txt | None | 30170ms |
```json
{
"overall": 12,
"dimensions": {
"token_efficiency": 8.0,
"first_try_success": 2.0,
"response_parseability": 6.0,
"error_clarity": 3.0,
"doc_quality": 3.0,
"auth_simplicity": 7.0,
"latency": 0.5,
"consistency": 1.0
},
"pricing_normalized": {
"type": "free",
"cost": 0,
"notes": "Open Data, free with attribution"
},
"issues": [
"All three checks timed out (>30s), indicating severe server instability",
"No website response obtained — could not verify content, headers, or functionality",
"Robots.txt and llms.txt not accessible, limiting discoverability and API documentation access",
"Service appears to be down or extremely slow, making it unreliable for production use",
"No security headers detected (though could not confirm due to timeout)"
],
"recommendations": [
"Investigate critical server performance issues — 30s+ timeouts are unacceptable",
"Implement a CDN or caching layer to improve response times to under 2 seconds",
"Ensure robots.txt and llms.txt are served quickly for agent discoverability",
"Add a status page and uptime monitoring to proactively communicate issues",
"Provide GTFS/GTFS-RT feeds via fast, dedicated endpoints rather than relying on web UI",
"Create programmatic access documentation for agents to consume data efficiently"
]
}
```Show your live agent-readiness score on your own site. Free, no auth — it updates as your score changes.
<a href="https://prowl.world/service/transport-for-hessen-germany">
<img src="https://prowl.world/badge/transport-for-hessen-germany.svg" height="56" alt="Agent-readiness on Prowl">
</a>
See operational metrics, LLM evaluations, agent readiness, and more.
Open in Dashboard