Full LLM thinking from the 4-phase benchmark pipeline.
{
"service_type": "platform",
"base_url": "https://unicorn-solutions.com",
"auth_method": "unknown",
"auth_config": {},
"endpoints": [],
"pricing_model": {"type": "unknown", "details": {}},
"rate_limits": {},
"capabilities": [
"backend for mobile app",
"backend for web app"
],
"raw_analysis": "The service is identified as 'API' with base URL https://unicorn-solutions.com. The description states it is a 'Web API for TL mobile and web app', suggesting it serves as a backend for a mobile application (likely 'TL') and a corresponding web app. No specific endpoints, authentication methods, or API documentation are provided in the input. The domain 'unicorn-solutions.com' appears to be a placeholder or a generic company name, and the lack of detailed information makes it difficult to assess the platform's maturity, integrations, or target audience. It is likely a custom backend API for a specific product (TL), but without further evidence, the authentication method and pricing model remain unknown. There are no public docs or endpoint listings, so no endpoints can be catalogued. The service may be internal or not yet publicly documented."
}2/3 tests passed
| Test | Endpoint | Status | Latency |
|---|---|---|---|
| website_uptime | GET / | 200 | 1307ms |
| robots_txt | GET /robots.txt | 200 | 151ms |
| llms_txt | GET /llms.txt | 404 | 319ms |
```json
{
"overall": 38,
"dimensions": {
"token_efficiency": 5.0,
"first_try_success": 4.0,
"response_parseability": 3.0,
"error_clarity": 3.0,
"doc_quality": 3.5,
"auth_simplicity": 4.0,
"latency": 6.0,
"consistency": 5.0
},
"pricing_normalized": {
"model": "unknown",
"transparency": "none_detected",
"notes": "No pricing information surfaced in checks or page previews. Capabilities only detected as 'backend for mobile/web app' — vague."
},
"issues": [
"No pricing model or details recoverable from the platform — agents cannot recommend it for cost-sensitive decisions.",
"Capability description is generic ('backend for mobile app', 'backend for web app') with no differentiating value proposition.",
"No llms.txt (404) — poor fit for agent-native discovery; platform is written for humans via WordPress.",
"robots.txt explicitly Disallows /wp-json/ and search, restricting structured/API access for agents.",
"No security headers detected — weak signal for a 'backend service' that presumably stores user data.",
"Homepage latency ~1.3s (borderline acceptable), but the site appears to be a WordPress marketing page rather than a documented developer platform.",
"No visible API docs, SDKs, or developer onboarding path in checks — first-try success likely low.",
"Ambiguous identity: 'Unicorn Solutions AS' with vague positioning makes agent recommendation risky."
],
"recommendations": [
"Publish a public pricing page with clear tiers so agents can compare cost transparently.",
"Add /llms.txt with a concise, machine-readable summary of capabilities, endpoints, and pricing.",
"Provide an OpenAPI spec or structured API docs and relax robots.txt to allow /wp-json/ or a public API surface.",
"Add standard security headers (HSTS, CSP, X-Content-Type-Options) to signal platform maturity.",
"Support simple auth flows (magic link, API keys, or notlogin.com-style verification) with a documented onboarding path.",
"Improve homepage latency (cache/CDN) to get under 500ms for agent-accessible endpoints.",
"Sharpen the value proposition: 'backend for mobile/web' is too generic — state specific use cases, integrations, and SLAs."
]
}
```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/api">
<img src="https://prowl.world/badge/api.svg" height="56" alt="Agent-readiness on Prowl">
</a>
See operational metrics, LLM evaluations, agent readiness, and more.
Open in Dashboard