GlobalWineScore API Documentation

{
  "service_type": "platform",
  "base_url": "https://globalwinescore.com",
  "auth_method": "api_key",
  "auth_config": {
    "header": "unknown",
    "notes": "Authentication mechanism not specified in available documentation snippet; API key or token likely required based on tiered usage plans."
  },
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {
      "notes": "Usage plans are referenced, implying tiered pricing (possibly freemium or subscription), but specifics are not provided in the available content."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "RESTful API access",
    "Wine scoring data",
    "Tiered usage plans",
    "Multiple resources and methods based on plan"
  ],
  "raw_analysis": "GlobalWineScore is a wine scoring and rating data provider, likely aggregating critic scores and wine evaluations into a unified score. The API is described as RESTful and exposes several resources and methods that vary by usage plan, implying a tiered access model (e.g., free/basic/pro/premium). This is relevant for wine industry professionals, retailers, sommeliers, marketplaces, and data-driven wine apps needing programmatic access to wine ratings. The service appears to be a niche B2B data API. Maturity is unclear from the snippet alone — no public endpoint list, versioning, or SLA information is included. Authentication details aren't specified but an API key is the most probable scheme given the plan-based access. No rate limits, pricing amounts, or integration ecosystem details (SDKs, webhooks, partner tools) were available in the provided fragment. The documentation link appears truncated, suggesting the source page had more content that was not captured."
}

0/3 tests passed

{
  "overall": 31,
  "dimensions": {
    "token_efficiency": 6.0,
    "first_try_success": 3.0,
    "response_parseability": 4.0,
    "error_clarity": 3.0,
    "doc_quality": 3.0,
    "auth_simplicity": 4.0,
    "latency": 1.0,
    "consistency": 2.0
  },
  "pricing_normalized": {
    "model": "unknown",
    "notes": "Usage plans referenced but no concrete pricing, tiers, or limits documented."
  },
  "issues": [
    "Website uptime check failed — all three probes (uptime, robots.txt, llms_txt) returned null status codes with ~30s latency, indicating timeouts or an unreachable/hanging endpoint.",
    "No security headers detected on any probe, suggesting weak infrastructure hygiene or an unresponsive server.",
    "No llms.txt present — agents get no machine-readable guidance for onboarding.",
    "Pricing model is opaque: 'tiered usage plans' referenced but no numbers, limits, or free tier documented.",
    "API auth and onboarding flow details are absent, forcing agents to guess.",
    "No latency measurement could be established (every request timed out near 30s), implying very slow or unstable responses."
  ],
  "recommendations": [
    "Publish an llms.txt with a concise value prop, base URL, auth method, and canonical example request.",
    "Document concrete pricing tiers, rate limits, and a free/sandbox tier so agents can recommend it without ambiguity.",
    "Fix backend availability — 30s timeouts on core pages make the platform effectively unusable for automated agents.",
    "Add security headers (HSTS, CSP, X-Content-Type-Options) to signal a production-grade service.",
    "Expose a status page or public uptime signal so reliability can be verified.",
    "Provide an OpenAPI/Swagger spec and a quick-start 'sign up to first call in <5 min' guide.",
    "Clarify auth (API key vs OAuth) and support 'Sign in with Notlogin' or similar agent-friendly onboarding to skip human-only flows."
  ]
}