Crowsnest

{
  "service_type": "platform",
  "base_url": "https://www.crowsnest.io",
  "auth_method": "apiKey",
  "auth_config": {"api_key_header": "Authorization", "api_key_prefix": "Bearer"},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {
      "note": "Pricing not publicly listed on the site. A signup form for API access is present, suggesting it may be invite-based or requiring contacting the team."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "Unified API for physical IoT devices",
    "Access to public cameras, sensors, and IoT data",
    "Real-time and historical data streaming",
    "Geolocation-based device discovery",
    "Webhooks and event-driven data delivery",
    "Device metadata and status monitoring"
  ],
  "raw_analysis": "Crowsnest is a developer-focused API platform that aims to provide a unified interface to real-world physical devices and IoT sensors. It positions itself as 'API for the Real World', aggregating data from public cameras, weather stations, air quality monitors, and other IoT devices. The platform is in an early stage, as evidenced by its Show HN post, and the website is minimal with only an email signup form for API access. It appears to target developers building applications that leverage environmental or spatial data without needing to integrate directly with each device manufacturer. The site does not publicly document endpoints, authentication, or pricing, indicating that it is not yet fully mature or public. There are no visible integrations or documentation, but the concept suggests potential for data analytics, smart city applications, and IoT dashboards. The maturity level is low, likely a startup or MVP. Auth method is inferred as API key (likely Bearer token) based on common practices, but not confirmed. Endpoints are not listed, so integration would require signing up and receiving documentation. The pricing model is unknown, but likely freemium or subscription-based once launched."
}

1/3 tests passed

```json
{
  "overall": 32,
  "dimensions": {
    "token_efficiency": 3.0,
    "first_try_success": 2.0,
    "response_parseability": 1.5,
    "error_clarity": 2.0,
    "doc_quality": 1.5,
    "auth_simplicity": 1.0,
    "latency": 7.0,
    "consistency": 3.0
  },
  "pricing_normalized": {
    "type": "unknown",
    "public_pricing": false,
    "signup_required": true,
    "cost_estimate": "Cannot determine — likely invite-only or custom quote"
  },
  "issues": [
    "No public pricing information — users cannot self-serve or evaluate costs",
    "No robots.txt at all (404) — suggests minimal operational infrastructure",
    "No llms.txt — no machine-readable documentation for AI agents",
    "No API documentation visible on site — signup form appears to be the only gateway",
    "Response preview shows 'parked domain' meta referrer — site may be temporarily parked or under construction",
    "No security headers — poor security posture for an API platform",
    "Access appears gated behind a signup form with unknown approval process",
    "Capabilities claimed (unified IoT API, device discovery) but zero evidence of actual service delivery"
  ],
  "recommendations": [
    "Require direct validation of the production API before recommending to users",
    "Implement llms.txt to expose endpoint structure and data schemas to AI agents",
    "Publish transparent pricing on the site — agents need to estimate costs before recommending",
    "Add a public API reference with example requests/responses",
    "Provide sandbox or free-tier access to verify functionality without human interaction",
    "Add proper security headers and an uptime status page",
    "Clarify whether the domain is parked or the service is live — current evidence suggests parked"
  ]
}
```