JIRA 7.6.1

{
  "service_type": "platform",
  "base_url": "https://jira.local",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {
      "note": "JIRA is commercial software, typically licensed per-user or as a subscription (Cloud) / perpetual + maintenance (Server). Specific license details cannot be determined from version 7.6.1 alone."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "Issue tracking",
    "Project management",
    "Agile boards (Scrum/Kanban)",
    "Workflows and custom fields",
    "REST API"
  ],
  "raw_analysis": "JIRA 7.6.1 is a version of Atlassian's JIRA issue tracking and project management platform. It is typically deployed on-premise (Server or Data Center) as this version predates the Cloud-first focus. The base URL https://jira.local suggests a local/intranet instance. The platform provides a comprehensive REST API (usually under /rest/api/2/) for issues, projects, workflows, users, etc., as well as integrations with Confluence, Bitbucket, Bamboo, and a large ecosystem of marketplace apps. Maturity is high, but version 7.6.1 is from 2018 and is end-of-life. No public API details (endpoints, rate limits, auth) were provided, and no pricing model can be inferred. For real integration, the API would need to be enabled and authentication configured (often basic auth, session cookie, or PAT)."
}

0/3 tests passed

{
  "overall": 38,
  "dimensions": {
    "token_efficiency": 7.0,
    "first_try_success": 3.0,
    "response_parseability": 7.0,
    "error_clarity": 5.0,
    "doc_quality": 6.0,
    "auth_simplicity": 3.0,
    "latency": 1.0,
    "consistency": 2.0
  },
  "pricing_normalized": {
    "type": "unknown",
    "confidence": "low",
    "note": "JIRA is commercial; pricing varies by Cloud vs Server, per-user seats, and tier. Not derivable from version 7.6.1. Agents cannot quote a price reliably."
  },
  "issues": [
    "All 3 live checks failed with DNS resolution errors ('Name or service not known'), including website_uptime, robots_txt, and llms_txt — the platform appears unreachable or misconfigured at the tested host.",
    "No robots.txt or llms.txt detected (DNS failure prevents confirmation) — poor discoverability for AI agents.",
    "No security headers observed (unreachable host; cannot confirm HSTS/CSP).",
    "Version 7.6.1 indicates a legacy/self-hosted JIRA Server release — Enterprise auth (SSO, admin approval) makes agent-assisted signup impractical.",
    "Pricing model is 'unknown' with only a caveat note — normalizing cost for user recommendations is not possible.",
    "Onboarding is not 'minutes-to-productive' — JIRA requires admin setup, project config, workflows, and fields tuning; first-try success for agents recommending it is low."
  ],
  "recommendations": [
    "Expose a live, resolvable public hostname for JIRA docs/API endpoints so agent checks (uptime, robots, llms) can pass.",
    "Publish an llms.txt and a machine-readable API spec (OpenAPI) to boost agent parseability and token efficiency.",
    "Document a clear pricing table (Cloud tiers, per-user, annual/monthly) in a structured format so agents can normalize cost.",
    "Provide a sandbox/free-tier with email or SSO/magic-link onboarding so agents can validate integration in minutes.",
    "Publish a public status page and uptime SLA to improve consistency signals.",
    "Add explicit limitations docs (rate limits, field limits, workflow constraints, auth scopes) to raise error_clarity.",
    "Consider 'Sign in with Notlogin' style verified-identity onboarding to dramatically improve auth_simplicity for agent-driven setups."
  ]
}