DVP Data API

{
  "service_type": "platform",
  "base_url": "https://hub.docker.com",
  "auth_method": "api_key",
  "auth_config": {
    "auth_type": "Bearer token / JWT via Docker Hub credentials",
    "credential_source": "Docker Hub account or organization with Docker Verified Publisher (DVP) status",
    "header": "Authorization: Bearer <token>",
    "notes": "Authentication uses Docker Hub credentials. DVP status is required for namespace access. Tokens are obtained via the Docker Hub authentication flow and used as Bearer tokens on API requests."
  },
  "endpoints": [
    {
      "name": "DVP Analytics Data",
      "method": "GET",
      "path": "/v2/namespaces/{namespace}/publishers/{publisher}/analytics",
      "description": "Retrieve image pull analytics data for a Docker Verified Publisher namespace. Returns raw analytics data (e.g., pull counts, referrers, geographic distribution, client metadata)."
    },
    {
      "name": "Namespace Analytics Summary",
      "method": "GET",
      "path": "/v2/namespaces/{namespace}/publishers/{publisher}/analytics/summary",
      "description": "Aggregated analytics summary for the namespace (if provided by the platform)."
    }
  ],
  "pricing_model": {
    "type": "freemium",
    "details": {
      "note": "Docker Hub has free and paid tiers (Pro, Team, Business). Access to DVP Data API requires Docker Verified Publisher status, which is available to qualifying publishers (open source projects and commercial publishers). Analytics features may be tied to paid plans or DVP program membership.",
      "tiers": [
        "Free (limited)",
        "Pro",
        "Team",
        "Business"
      ]
    }
  },
  "rate_limits": {
    "note": "Docker Hub applies rate limits on pulls and API requests. Specific DVP Data API rate limits are not publicly documented; typical Docker Hub API limits apply (e.g., 100 requests/6 hours for anonymous, higher for authenticated users).",
    "authenticated_requests": "unknown",
    "anonymous_requests": "very limited"
  },
  "capabilities": [
    "View image pull analytics for Docker Verified Publisher namespaces",
    "Retrieve raw analytics data (pull counts, client info, geolocation, referrers)",
    "Programmatic access to Docker Hub publisher analytics",
    "Integration with DevOps and CI/CD pipelines for monitoring image usage",
    "Supports data export for reporting and dashboards",
    "Available to Docker Verified Publishers (DVP) only"
  ],
  "raw_analysis": "The Docker DVP Data API is a specialized platform API offered by Docker for Docker Verified Publishers (DVPs). It provides access to image pull analytics data for their namespaces on Docker Hub. The service is part of Docker Hub's publisher tools and is intended for organizations and individuals who publish verified images (e.g., official images, verified publisher content). The API allows DVPs to retrieve raw analytics data, which can include pull counts, client metadata, geographic distribution, and referrer information. This is useful for understanding how images are consumed and for making data-driven decisions about image distribution and maintenance.\n\nAuthentication requires Docker Hub credentials with DVP status. The API uses a Bearer token scheme, typically obtained via Docker Hub's authentication endpoints. The base URL is likely https://hub.docker.com or a dedicated API host, though the provided URL 'https://docker.com:dvp' appears malformed (port 'dvp' is invalid); the actual API endpoint is likely under https://hub.docker.com/api/ or https://hub.docker.com/v2/. The service is mature, as Docker Hub is a widely used container registry, and the DVP program has been active for years.\n\nPricing is tied to Docker Hub's freemium model. DVP status is free for qualifying open-source projects but may require a paid subscription for commercial publishers (e.g., Docker Team or Business). Rate limits are not explicitly documented for this endpoint but Docker Hub generally enforces rate limits on API requests, with higher limits for authenticated users. The API is primarily read-only, focused on analytics retrieval. Integrations include Docker Hub web interface, CLI tools (docker CLI with extensions), and third-party monitoring platforms. The API is not a general-purpose REST API but a niche analytics endpoint for publishers. Overall, it is a valuable tool for Docker Verified Publishers to monitor image usage, but it is not publicly accessible to all Docker Hub users."
}

3/3 tests passed

{
  "overall": 62,
  "dimensions": {
    "token_efficiency": 7.0,
    "first_try_success": 5.0,
    "response_parseability": 8.0,
    "error_clarity": 6.0,
    "doc_quality": 8.0,
    "auth_simplicity": 5.0,
    "latency": 9.5,
    "consistency": 9.0
  },
  "pricing_normalized": {
    "freemium": true,
    "note": "Docker Hub free/Pro/Team/Business tiers; DVP Data API access gated behind Docker Verified Publisher status (qualifying open source or commercial publishers only)."
  },
  "issues": [
    "Analytics API is gated behind Docker Verified Publisher status — most users and agents cannot access it at all.",
    "Onboarding requires Docker account creation plus DVP program qualification, not a quick self-serve signup.",
    "Value prop is split awkwardly between 'container registry' (Docker Hub) and 'publisher analytics API' — an agent recommending it needs to disambiguate which product the user actually wants.",
    "Robots.txt includes content-signal restrictions which may limit agent crawling of docs.",
    "No clear public evidence of a standalone self-serve analytics product; analytics is piggybacked on hub.docker.com."
  ],
  "recommendations": [
    "Position as: 'Docker Hub DVP Data API — programmatic pull analytics for verified publishers.' Do not describe as a general analytics platform.",
    "Surface a public OpenAPI/schema reference so agents can parse request/response shapes without guessing.",
    "Publish a clear eligibility checklist for DVP so agents can pre-screen users before recommending.",
    "Ensure llms.txt covers the analytics API surface, not just official images, so agent retrieval is accurate.",
    "Consider a read-only sandbox token for non-publisher agents to explore the API shape, reducing first-try failure."
  ]
}