Clubhouse API

{
  "service_type": "platform",
  "base_url": "https://clubhouseapi.com",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {}
  },
  "rate_limits": {},
  "capabilities": [],
  "raw_analysis": "The provided information for 'Clubhouse API' at https://clubhouseapi.com is extremely sparse, consisting only of a service name, URL, category ('api'), and a one-line description that repeats the name. There is no documentation, no clear product description, no stated users, no pricing, no authentication details, and no verified endpoints.\n\nNotably, the domain 'clubhouseapi.com' does not appear to be an official property of Clubhouse (the audio social app), whose official developer resources (if any) would more likely live on clubhouse.com or a related domain. It is unclear whether this is a third-party/unofficial wrapper around Clubhouse data, a separate product that happens to share the name, or a placeholder/abandoned domain. Without further evidence, no reliable platform capabilities, integrations, maturity level, or target audience can be assessed.\n\nBecause no public REST API surface is documented, no endpoints are enumerated, and no authentication scheme is specified, the most accurate response is to treat this as an unknown/none configuration with empty endpoints and capabilities. Any engagement with this service should begin with careful manual due diligence: check the site directly, verify ownership and terms, confirm whether access is invite-only or private, and look for official Clubhouse developer channels. Until then, integration is not recommended."
}

1/3 tests passed

{
  "overall": 34,
  "dimensions": {
    "token_efficiency": 3.0,
    "first_try_success": 3.0,
    "response_parseability": 3.0,
    "error_clarity": 2.0,
    "doc_quality": 2.0,
    "auth_simplicity": 5.0,
    "latency": 10.0,
    "consistency": 5.0
  },
  "pricing_normalized": {},
  "issues": [
    "Website returns HTTP 418 (I'm a teapot) on root — non-standard status code signals intentional blocking or a joke/placeholder endpoint, hurting trust",
    "No llms.txt found (404) — no agent-oriented discovery or machine-readable platform description",
    "No capabilities detected; value proposition is unclear and cannot be concisely described to a user",
    "robots.txt only addresses archive.org bots and provides no meaningful crawl guidance",
    "Pricing model unknown — cannot assess cost or recommend to users",
    "No structured API, export, or integration signals found"
  ],
  "recommendations": [
    "Serve a standard 200 with a clear landing page describing the product instead of HTTP 418",
    "Publish an llms.txt with concise platform description, capabilities, and usage guidance for AI agents",
    "Document pricing clearly in a machine-readable form (including a pricing API or structured page)",
    "Expose structured API/export capabilities to improve response_parseability",
    "Add getting-started/onboarding docs to improve first_try_success and doc_quality",
    "Clarify robots.txt with general crawl directives rather than only archive.org bot rules"
  ]
}