Cloud-RF API

{
  "service_type": "platform",
  "base_url": "https://cloudrf.com",
  "auth_method": "api_key",
  "auth_config": {
    "header": "key",
    "key_type": "API2.0"
  },
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {}
  },
  "rate_limits": {},
  "capabilities": [
    "radio link design and simulation",
    "RF propagation modeling",
    "API-based programmatic access for link analysis"
  ],
  "raw_analysis": "Cloud-RF is a specialized API platform for RF (radio frequency) engineering, primarily aimed at telecom engineers, network planners, and wireless system designers. It provides APIs to build and test radio links for any radio, covering aspects like path loss, signal strength, and feasibility. The platform is mature enough to offer API version 2.0 (called 'API2.0'), with authentication via an API key sent in a request header named 'key'. The main web interface provides a link calculator tool, and the API extends this to allow integration into custom applications or workflows. The service supports a community of users, and given its niche focus, it likely operates on a subscription model based on usage or plan tiers, but no public pricing details are available from the given content. There is no explicit list of endpoints, rate limits, or integration details provided. Integration possibilities might include exporting link designs, batch processing, or pairing with other network planning tools. The raw JSON output for analysis is not specified, but likely includes link parameters such as frequency, distance, antenna gains, and terrain data. Overall, this is a domain-specific API for radio link planning, with moderate maturity indicated by a versioned API and documented authentication system."
}

2/3 tests passed

{
  "overall": 48,
  "dimensions": {
    "token_efficiency": 5.0,
    "first_try_success": 4.0,
    "response_parseability": 7.0,
    "error_clarity": 5.0,
    "doc_quality": 5.0,
    "auth_simplicity": 5.0,
    "latency": 6.5,
    "consistency": 7.0
  },
  "pricing_normalized": {},
  "issues": [
    "No LLM-friendly endpoint (/llms.txt returning 404)",
    "Pricing model unknown; may hinder agent recommendations",
    "Auth and onboarding complexity not verifiable from basic checks",
    "Potential niche domain (radio link design) may limit general usefulness"
  ],
  "recommendations": [
    "Provide clear pricing documentation and API details",
    "Consider adding an LLM-friendly overview page or /llms.txt",
    "Simplify sign-up with SSO or API keys to reduce onboarding friction",
    "Enhance error messaging and docs for API usage constraints"
  ]
}