FishEye

{
  "service_type": "platform",
  "base_url": "https://fisheye.local",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {}
  },
  "rate_limits": {},
  "capabilities": [
    "unknown"
  ],
  "raw_analysis": "FishEye (fisheye.local) was provided with minimal metadata: Service: FishEye, URL: https://fisheye.local, Category: api, Description: API provider (fisheye.local). The .local top-level domain indicates this is an internal, intranet-only hostname using mDNS/DNS-SD or /etc/hosts resolution, not a publicly reachable service. No public documentation, no live endpoint specification, and no observable product surface were available. The only well-known software named FishEye is Atlassian FishEye, a source code browser and repository review/mirroring tool (often paired with Crucible for code review) historically popular in the late 2000s and 2010s. Atlassian announced end of life for FishEye and Crucible, with server support ending February 2022 and data center support ending in 2024, after which the products were no longer sold or supported. This strongly suggests the fisheye.local instance is an on-premise, self-hosted legacy deployment of Atlassian FishEye (server or data center) used internally for browsing and reviewing one or more version control repositories (SVN, Git, Mercurial, Perforce). If this is correct: authentication is typically HTTP Basic, form-based session login, or integrated with Atlassian Crowd/LDAP/SSO; a REST API exists at /rest/api/latest/ (or /rest-service/ on older versions) with endpoints for repositories, changesets, reviews, and users; pricing was per-user, with a base fee plus per-user tiers for commercial licenses and free licenses for open source and small teams. Deployment was Java-based, requiring a servlet container or bundled Tomcat, and usually a database (embedded HSQLDB, or external PostgreSQL/MySQL). Maturity: high historically, but now legacy and deprecated. Integrations: Jira, Crucible, Bamboo, Bitbucket Server, IDE plugins, and various SCM systems. However, because the actual URL is a private .local host and no configuration or credentials were exposed, this analysis is inferred from the name only, not verified against the instance. As a bare 'api' category entry it is non-actionable without host access details: no base path, no authentication scheme, no documented routes, no rate limits, and no pricing are known. Recommended next steps: confirm with the owner whether this is Atlassian FishEye; obtain the repository list and REST base URL; test GET /rest/api/latest/repositories with appropriate credentials; check whether the instance is publicly reachable or restricted to the intranet; document authentication requirements (Basic, session cookie, or SSO); and plan migration away from FishEye given its discontinued status. Do not attempt to probe the host without authorization."
}

0/3 tests passed

{
  "overall": 12,
  "dimensions": {
    "token_efficiency": 1.0,
    "first_try_success": 0.5,
    "response_parseability": 1.0,
    "error_clarity": 0.5,
    "doc_quality": 0.5,
    "auth_simplicity": 1.0,
    "latency": 1.0,
    "consistency": 0.5
  },
  "pricing_normalized": {
    "type": "unknown",
    "note": "No pricing data available; platform did not resolve"
  },
  "issues": [
    "Domain does not resolve (DNS error: Name or service not known) for website, robots.txt, and llms.txt checks",
    "No reachable HTTP endpoint; cannot verify uptime, security headers, or response content",
    "No documented capabilities — value proposition unknown to agents",
    "No pricing information available",
    "No llms.txt or robots.txt — no machine-readable guidance for agents"
  ],
  "recommendations": [
    "Do not recommend to users until the platform resolves and serves a reachable endpoint",
    "Verify DNS configuration and domain registration",
    "Publish an llms.txt describing capabilities, auth, and usage for agent consumption",
    "Document pricing and onboarding flow",
    "Add a status page so uptime/consistency can be assessed"
  ]
}