Full LLM thinking from the 4-phase benchmark pipeline.
{
"service_type": "platform",
"base_url": "https://api.tfl.gov.uk",
"auth_method": "none",
"auth_config": {},
"endpoints": [],
"pricing_model": {"type": "free", "details": {"note": "Publicly accessible API with no authentication required for many endpoints, but registration may be needed for higher rate limits."}},
"rate_limits": {},
"capabilities": [
"Real-time journey planning",
"Live status updates for tube, rail, bus, and DLR",
"Disruption information",
"Stop and line information",
"Route planning",
"Bike share availability (Santander Cycles)",
"Accessibility information",
"Air quality data",
"Road condition updates",
"Fare information",
"IoT and sensor data for some services"
],
"raw_analysis": "The Transport for London (TfL) API is a mature, public, open-data platform provided by the Mayor of London's office. It offers a comprehensive RESTful API for accessing real-time and static data about London's transport network, including buses, underground, overground, DLR, trams, and river services. The API is well-documented with extensive endpoint coverage and is widely used by third-party developers, researchers, and mobility startups. It supports formats like JSON and is free to use without authentication for most endpoints, though an application key can be requested for higher rate limits and usage tracking. The platform is a flagship example of open data, with a strong emphasis on accessibility and transparency. Maturity is high, given years of operation and a robust infrastructure. There are no inherent endpoints in this review context, but the platform's capabilities are extensive. Key integrations include compatibility with Google Maps, Citymapper, and various local transport apps. Overall, it is a reliable, production-ready platform for any application needing London transport data."
}1/3 tests passed
| Test | Endpoint | Status | Latency |
|---|---|---|---|
| website_uptime | GET / | 200 | 560ms |
| robots_txt | GET /robots.txt | 404 | 49ms |
| llms_txt | GET /llms.txt | 404 | 645ms |
{
"overall": 68,
"dimensions": {
"token_efficiency": 7.0,
"first_try_success": 6.0,
"response_parseability": 8.0,
"error_clarity": 8.0,
"doc_quality": 7.0,
"auth_simplicity": 8.0,
"latency": 6.0,
"consistency": 8.0
},
"pricing_normalized": {
"type": "free",
"note": "Free public API with no auth for many endpoints; registration may raise rate limits"
},
"issues": [
"Uptime check returned 560ms (slightly above the 500ms ideal for real-time use)",
"No robots.txt file (404), which may not affect API use but limits agent discovery",
"No llms.txt file, so agents must rely on documentation elsewhere",
"Rate limits may apply for unauthenticated requests, which could affect high-volume use"
],
"recommendations": [
"Add an llms.txt file to help agents discover and parse API documentation more efficiently",
"Provide explicit rate limit documentation for unauthenticated access to set expectations",
"Consider adding a status page for latency/uptime transparency",
"Ensure API documentation is concise and points to JSON responses for faster parsing"
]
}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-london-england">
<img src="https://prowl.world/badge/transport-for-london-england.svg" height="56" alt="Agent-readiness on Prowl">
</a>
See operational metrics, LLM evaluations, agent readiness, and more.
Open in Dashboard