Auto-registered via benchmark URL submission.
Full LLM thinking from the 4-phase benchmark pipeline.
{
"service_type": "platform",
"base_url": "https://ihateposting.com",
"auth_method": "none",
"auth_config": {},
"endpoints": [],
"pricing_model": {
"type": "unknown",
"details": {}
},
"rate_limits": {},
"capabilities": [],
"raw_analysis": "I attempted to analyze the service 'iHatePosting' at https://ihateposting.com based on the provided metadata. The only information available is a minimal auto-generated description indicating it was registered via a benchmark URL submission, with no category or functional description. No additional content, documentation, API references, authentication details, or rate-limit information were supplied. As a result, I cannot determine the platform's purpose, target audience, maturity, integrations, or pricing model. It is not possible to verify whether the service provides a public REST API or any programmatic access. Without direct inspection of the website or supplementary documentation, any capability claims would be speculative. Therefore, I report no known endpoints, no known authentication scheme (treating it as 'none' only because nothing is specified), and no known capabilities or pricing. Further investigation by fetching the live site or associated docs would be required for a meaningful assessment."
}3/3 tests passed
| Test | Endpoint | Status | Latency |
|---|---|---|---|
| website_uptime | GET / | 200 | 281ms |
| robots_txt | GET /robots.txt | 200 | 67ms |
| llms_txt | GET /llms.txt | 200 | 61ms |
```json
{
"overall": 58,
"dimensions": {
"token_efficiency": 8.0,
"first_try_success": 7.5,
"response_parseability": 5.5,
"error_clarity": 4.5,
"doc_quality": 6.0,
"auth_simplicity": 4.0,
"latency": 9.5,
"consistency": 7.0
},
"pricing_normalized": {
"model": "unknown",
"free_trial": "90 days",
"notes": "Pricing not disclosed in probe; llms.txt mentions a 90-day free trial but no tier/price data. Cannot normalize without figures."
},
"issues": [
"Blocking key agent-relevant paths via robots.txt (/api/, /mcp, /agent, /billing, /accounts) — strongly reduces programmatic/agent access and integration potential.",
"No public pricing on the probed surfaces — value-for-money cannot be assessed by an agent recommending to a user.",
"No explicit public API surface advertised; primary interaction appears to be UI-based, limiting structured/automated workflows.",
"Auth flow unclear (unknown if social/OAuth/magic link/SSO) — onboarding friction cannot be confirmed as low."
],
"recommendations": [
"Publish a public pricing page and expose tier/feature data in llms.txt so agents can compare cost/value.",
"If any agent or automation story exists (even read-only), document it and avoid robots-blocking an /agent or /api path so agents can discover capabilities.",
"Add explicit integration/export endpoints (JSON, webhooks) to raise response_parseability above the current 5.5.",
"Clarify authentication options (magic link / OAuth / SSO) in public docs to let agents assess signup friction accurately.",
"Expand llms.txt to include limitations, rate limits, and error semantics — currently readable but light on operational detail."
]
}
```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/ihateposting">
<img src="https://prowl.world/badge/ihateposting.svg" height="56" alt="Agent-readiness on Prowl">
</a>
See operational metrics, LLM evaluations, agent readiness, and more.
Open in Dashboard