Patchman-engine API

{
  "service_type": "platform",
  "base_url": "https://redhat.local:patchman-engine",
  "auth_method": "unknown",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {
      "note": "Patchman is a Red Hat Insights service hosted on cloud.redhat.com; pricing is bundled with Red Hat subscriptions (RHEL subscription includes Insights)."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "Patch/errata management for RHEL systems",
    "Filtering via filter[name] query parameters",
    "Integration with Red Hat Insights on cloud.redhat.com",
    "System vulnerability and package update tracking",
    "Advisory/errata reporting"
  ],
  "raw_analysis": "Patchman-engine API is the backend API for the Patch application within Red Hat Insights, hosted on cloud.redhat.com. It is a Red Hat internal/enterprise service focused on patch and errata management for Red Hat Enterprise Linux (RHEL) systems. The base URL provided (https://redhat.local:patchman-engine) appears to be a local/development instance rather than the public production endpoint, given the 'redhat.local' hostname and non-standard port-style path.\n\nThe service is mature and vendor-backed (Red Hat), used by enterprise customers and managed through the Red Hat Insights platform. Authentication is not described in the provided text; in production, access is typically via Red Hat SSO/OAuth or platform identity headers (e.g., x-rh-identity), but this cannot be confirmed from the given description. The only documented API detail is support for filter[name] query parameters, with filter syntax documented in the RedHatInsights/patchman GitHub repository.\n\nNo explicit endpoints, rate limits, or pricing details are provided. Pricing is effectively tied to Red Hat subscriptions rather than a standalone paid API. The platform integrates with Red Hat Insights and the broader Red Hat Hybrid Cloud Console. This analyzer cannot fetch live documentation from the local URL, so the analysis is based solely on the supplied description and known Red Hat Insights context.\n\nKey limitations: no public REST API base URL, no auth details, no endpoint list, and no explicit rate-limit documentation in the provided content."
}

0/3 tests passed

```json
{
  "overall": 34,
  "dimensions": {
    "token_efficiency": 6.0,
    "first_try_success": 3.0,
    "response_parseability": 4.0,
    "error_clarity": 3.0,
    "doc_quality": 4.0,
    "auth_simplicity": 2.0,
    "latency": 8.0,
    "consistency": 4.0
  },
  "pricing_normalized": {
    "model": "bundled_with_subscription",
    "note": "Patchman is a Red Hat Insights service; cost is bundled with RHEL subscriptions, not sold standalone. No independent pricing tier."
  },
  "issues": [
    "All three automated checks failed with 'Invalid port: patchman-engine' — the platform appears to be an internal Red Hat component, not a directly addressable web property.",
    "No standalone signup, API key issuance, or self-service onboarding path exists; access requires a Red Hat subscription and cloud.redhat.com account.",
    "No public robots.txt or llms.txt signals, indicating no agent-discovery affordances.",
    "Authentication is gated behind Red Hat account/SSO — no magic link, no agent-friendly identity flow.",
    "Documentation is scattered across Red Hat product docs; no single quickstart for programmatic access.",
    "Value prop is specific (RHEL errata/vulnerability tracking) but only relevant to a narrow audience already inside Red Hat's ecosystem."
  ],
  "recommendations": [
    "If recommending to users, only suggest Patchman for existing RHEL + Red Hat Insights customers; do not present as a general-purpose tool.",
    "For agent access, direct users to the Red Hat Insights API rather than a 'patchman' endpoint, as Patchman is not publicly addressable.",
    "Require the user to already have cloud.redhat.com credentials before any automation attempt; there is no fallback.",
    "Avoid for greenfield or multi-cloud agent workflows — the subscription lock-in and opaque auth make it unsuitable unless already adopted.",
    "If the user needs patch/errata management without Red Hat lock-in, recommend alternatives (e.g., OSV, GitHub Dependabot, Snyk) that expose open, self-serve APIs."
  ]
}
```