Auto-registered via benchmark URL submission.
Full LLM thinking from the 4-phase benchmark pipeline.
{
"service_type": "platform",
"base_url": "https://signalnodus.ai",
"auth_method": "none",
"auth_config": {},
"endpoints": [],
"pricing_model": {"type": "unknown", "details": {}},
"rate_limits": {},
"capabilities": ["unknown"],
"raw_analysis": "The URL https://signalnodus.ai is a landing page for a service called 'Signal Nodus'. The page appears to be an AI-related platform, but no specific product details, documentation, or API references are visible on the main page. There is no obvious sign-in, API key, or developer portal. The service seems to be in early or minimal stage, with no public REST API endpoints, authentication methods, or integration references. The domain is not widely referenced in public developer communities. It might be an internal or niche tool, but without further information, it is not possible to determine its exact functionality, target audience, maturity, or integrations. The site does not display pricing or rate limit information. As such, it is classified as an unknown platform with no accessible API."
}3/3 tests passed
| Test | Endpoint | Status | Latency |
|---|---|---|---|
| website_uptime | GET / | 200 | 332ms |
| robots_txt | GET /robots.txt | 200 | 45ms |
| llms_txt | GET /llms.txt | 200 | 42ms |
```json
{
"overall": 78,
"dimensions": {
"token_efficiency": 9.0,
"first_try_success": 8.5,
"response_parseability": 9.0,
"error_clarity": 7.0,
"doc_quality": 9.0,
"auth_simplicity": 9.0,
"latency": 8.5,
"consistency": 8.0
},
"pricing_normalized": {
"model": "pay_per_call_over_http_402",
"account_required": false,
"subscription": false,
"notes": "HTTP 402-based pay-per-call, no account or subscription needed per llms.txt"
},
"issues": [
"No explicit information on rate limits or request throttling beyond HTTP 402 paywall",
"llms.txt response suggests SEC data extraction only; capabilities limited to 10-K/10-Q items and diffs — not generalized API",
"Error clarity not fully verifiable: docs mention HTTP 402 but not detailed error response schemas"
],
"recommendations": [
"Add a dedicated errors.md or /docs/errors page documenting all 4xx/5xx status codes with example responses",
"Include a rate limits section in llms.txt (requests/min, burst allowances) to improve consistency expectations",
"Provide a quickstart code snippet in llms.txt (curl example) to shorten first-call time for agents"
]
}
```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/signal-nodus">
<img src="https://prowl.world/badge/signal-nodus.svg" height="56" alt="Agent-readiness on Prowl">
</a>
See operational metrics, LLM evaluations, agent readiness, and more.
Open in Dashboard