Xcrawl API

{
  "service_type": "platform",
  "base_url": "https://xcrawl.ai",
  "auth_method": "unknown",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {
      "note": "No public pricing information available at https://xcrawl.ai"
    }
  },
  "rate_limits": {},
  "capabilities": [
    "unknown - no public documentation or feature list available",
    "possibly AI-related based on category tag 'ai'"
  ],
  "raw_analysis": "Xcrawl API (https://xcrawl.ai) appears to be a service registered primarily via a benchmark URL submission mechanism. The only available description is an auto-generated placeholder, and no public documentation, API reference, authentication details, or pricing information could be retrieved from the domain. The service is categorized under 'ai', suggesting it may be an AI-focused web crawling or data extraction platform, but this cannot be confirmed. No endpoints, SDKs, or integration options are publicly documented. The platform's maturity, target audience, and business model are all unknown. Integration feasibility is low without further discovery — likely requires direct outreach to the provider or discovery through the benchmark framework that registered it."
}

2/3 tests passed

{
  "overall": 58,
  "dimensions": {
    "token_efficiency": 7.0,
    "first_try_success": 5.0,
    "response_parseability": 6.0,
    "error_clarity": 4.0,
    "doc_quality": 4.0,
    "auth_simplicity": 5.0,
    "latency": 6.0,
    "consistency": 6.0
  },
  "pricing_normalized": {
    "model": "unknown",
    "notes": "No public pricing tiers found at xcrawl.ai; agents cannot estimate cost without contacting sales or manual signup."
  },
  "issues": [
    "No public pricing — agents cannot recommend based on cost or compare to alternatives",
    "Missing llms.txt (404) — agent-friendly discovery path absent",
    "No structured API/feature list surfaced; capabilities marked 'unknown'",
    "Security headers absent on main page — minor trust signal gap",
    "Robots.txt content-signal language exists but usage terms unclear for agent access"
  ],
  "recommendations": [
    "Publish llms.txt with endpoint schemas, auth flow, rate limits, and sample requests",
    "Expose a public pricing page with tiered plans and free trial credits",
    "Add OpenAPI/Swagger spec so agents can introspect and call endpoints deterministically",
    "Provide a machine-readable capabilities doc (JSON or markdown) at a stable URL",
    "Support magic-link or API-key onboarding without human sales touch",
    "Add security headers (CSP, HSTS) to signal platform maturity",
    "Publish a status page and uptime SLA for consistency checks"
  ]
}