Full LLM thinking from the 4-phase benchmark pipeline.
{
"service_type": "platform",
"base_url": "https://stream-io-api.com",
"auth_method": "unknown",
"auth_config": {},
"endpoints": [],
"pricing_model": {
"type": "unknown",
"details": {}
},
"rate_limits": {},
"capabilities": [
"chat messaging",
"real-time communication",
"API-based integration"
],
"raw_analysis": "Stream Chat API is a service provided by stream-io-api.com, likely part of the Stream (getstream.io) platform, which specializes in scalable chat and activity feed APIs. The service appears to be an API provider for chat functionality, enabling developers to integrate real-time messaging into applications. However, the provided information is minimal, lacking details on authentication methods, specific endpoints, pricing, or rate limits. The base URL 'https://stream-io-api.com' does not match the commonly known Stream API endpoint (which is typically 'https://chat.stream-io-api.com' or similar), suggesting it might be a placeholder or incomplete. No public documentation is referenced, so maturity, integrations, and target audience are unclear. It is likely aimed at developers building chat features into apps, but without further data, the analysis is limited. The platform's capabilities include chat messaging and real-time communication, but these are inferred from the name. Overall, the service seems to be a chat API, but more information is needed for a comprehensive assessment."
}0/3 tests passed
| Test | Endpoint | Status | Latency |
|---|---|---|---|
| website_uptime | GET / | None | 92ms |
| robots_txt | GET /robots.txt | None | 75ms |
| llms_txt | GET /llms.txt | None | 73ms |
{
"overall": 22,
"dimensions": {
"token_efficiency": 3.0,
"first_try_success": 1.0,
"response_parseability": 2.0,
"error_clarity": 1.5,
"doc_quality": 1.0,
"auth_simplicity": 2.0,
"latency": 1.0,
"consistency": 1.0
},
"pricing_normalized": {
"model": "unknown",
"details": {},
"note": "No pricing information could be retrieved; domain does not resolve."
},
"issues": [
"All three checks (website uptime, robots.txt, llms.txt) failed with DNS resolution error '[Errno -5] No address associated with hostname'.",
"The platform domain appears to be unreachable/non-resolving, making it impossible to verify uptime, docs, or onboarding flow.",
"No security headers could be detected because no HTTP response was returned.",
"Capabilities are generic ('chat messaging', 'real-time communication', 'API-based integration') with no verifiable specifics.",
"Pricing model is 'unknown' — no public pricing data available for agent recommendations."
],
"recommendations": [
"Do not recommend this platform to users until the domain resolves and basic endpoints respond.",
"If the domain is intentionally internal or gated, provide a public landing page and docs so agents can describe the value proposition.",
"Publish an llms.txt and robots.txt to support agent discovery.",
"Provide clear pricing and auth documentation to enable agent-driven onboarding.",
"Restore DNS/hosting and add a status page so consistency and latency can be assessed.",
"Re-run the check suite after the site is reachable to obtain a meaningful score."
]
}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/stream-chat-api">
<img src="https://prowl.world/badge/stream-chat-api.svg" height="56" alt="Agent-readiness on Prowl">
</a>
See operational metrics, LLM evaluations, agent readiness, and more.
Open in Dashboard