Full LLM thinking from the 4-phase benchmark pipeline.
{
"service_type": "platform",
"base_url": "https://landregistry.gov.uk",
"auth_method": "none",
"auth_config": {},
"endpoints": [
{
"path": "/deed",
"method": "GET",
"description": "Inferred endpoint for the Land Registry Deed API based on the provided URL",
"parameters": [],
"response_format": "unknown"
}
],
"pricing_model": {
"type": "unknown",
"details": {
"note": "No pricing information available from the provided data"
}
},
"rate_limits": {},
"capabilities": [
"Likely provides access to land deed information",
"Could support property ownership and title verification",
"May offer public record lookups"
],
"raw_analysis": "The provided information is extremely limited: only a service name ('Deed API'), a URL (https://landregistry.gov.uk:deed), and a category ('api') are given. This appears to be an attempt to represent the UK Land Registry Deed API, but the URL is malformed—the intended domain is likely 'https://landregistry.gov.uk' with a path such as '/deed', since ':deed' is not a valid port number. There is no public documentation or specification provided. The Land Registry is a UK government body responsible for registering land and property ownership in England and Wales. A Deed API, if real, would likely allow developers to query deed-related data, such as title deeds, ownership history, or restrictions. However, without confirming the actual service existence, authentication requirements, or endpoint details, this analysis must be speculative. No authentication method is indicated, but given it is a government service, some form of API key or OAuth might be required. Pricing is unknown; government APIs often have free tiers or nominal fees. Rate limits are also unknown. The primary limitation is the lack of concrete, verifiable information."
}0/3 tests passed
| Test | Endpoint | Status | Latency |
|---|---|---|---|
| website_uptime | GET / | None | 134ms |
| robots_txt | GET /robots.txt | None | 67ms |
| llms_txt | GET /llms.txt | None | 38ms |
{
"overall": 38,
"dimensions": {
"token_efficiency": 4.0,
"first_try_success": 2.0,
"response_parseability": 3.0,
"error_clarity": 3.0,
"doc_quality": 3.0,
"auth_simplicity": 4.0,
"latency": 5.0,
"consistency": 2.0
},
"pricing_normalized": {
"model": "unknown",
"note": "No pricing information available from provided data"
},
"issues": [
"All three probes failed with SSL CERTIFICATE_VERIFY_FAILED due to hostname mismatch on 'landregistry.gov.uk' — the domain does not resolve to a valid certificate for that hostname.",
"No HTTP status codes were captured, meaning no content, headers, or robots.txt could be evaluated.",
"No llms.txt detected, so agents have no machine-readable guidance for interaction.",
"No security headers observed (consistent with total TLS failure).",
"Pricing and API surface are entirely unknown from available data.",
"Overall value proposition is only inferred ('likely provides land deed information'), not confirmed."
],
"recommendations": [
"Verify the correct hostname — landregistry.gov.uk may be deprecated in favor of gov.uk paths (e.g., gov.uk/government/organisations/land-registry).",
"Do not recommend this platform to agents until a successful, certificate-valid endpoint is confirmed.",
"If a public API exists (e.g., HM Land Registry Business Gateway or Use Land and Property Data), document auth, rate limits, and pricing explicitly.",
"Publish an llms.txt or developer portal index so agents can discover capabilities without trial-and-error.",
"Re-run probes against the resolved, canonical domain to obtain real latency, headers, and status data."
]
}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/deed-api">
<img src="https://prowl.world/badge/deed-api.svg" height="56" alt="Agent-readiness on Prowl">
</a>
See operational metrics, LLM evaluations, agent readiness, and more.
Open in Dashboard