Just Eat UK

{
  "service_type": "platform",
  "base_url": "https://just-eat.co.uk",
  "auth_method": "oauth2",
  "auth_config": {
    "notes": "Just Eat partner APIs use OAuth 2.0 with client credentials for business partners. Consumer-facing integrations vary.",
    "authorization_url": "https://login.just-eat.com",
    "token_url": "https://api.just-eat.com/oauth/token"
  },
  "endpoints": [],
  "pricing_model": {
    "type": "subscription",
    "details": {
      "note": "Pricing dependent on partner type and integration scope; not publicly documented."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "Food ordering and delivery",
    "Restaurant and menu data",
    "Order management for partners",
    "Consumer app integrations",
    "Partner APIs for business services"
  ],
  "raw_analysis": "Just Eat UK is a leading online food delivery marketplace connecting consumers with restaurants. The platform provides APIs for business partners (restaurants, POS systems, delivery providers) and for its own consumer applications. The provided description is minimal and mentions that interaction depends on the services desired. Security details are not specified. Just Eat is a mature, widely used platform in the UK and internationally. It likely offers REST APIs with OAuth 2.0 authentication for partners. No public endpoints were listed, and documentation is not fully available in the provided snippet. The platform is primarily a consumer marketplace with B2B integrations. Pricing model is subscription-based for partners, though exact details are not public. Rate limits are unknown but likely exist. The service category mentions 'security, api', indicating a focus on secure API access for partners."
}

2/3 tests passed

{
  "overall": 52,
  "dimensions": {
    "token_efficiency": 6.0,
    "first_try_success": 4.0,
    "response_parseability": 5.0,
    "error_clarity": 4.0,
    "doc_quality": 4.0,
    "auth_simplicity": 3.0,
    "latency": 9.0,
    "consistency": 8.0
  },
  "pricing_normalized": {
    "type": "subscription",
    "details": {
      "note": "Pricing dependent on partner type and integration scope; not publicly documented"
    }
  },
  "issues": [
    "No public pricing information — agents cannot quote costs to users",
    "No llms.txt (404) — no machine-readable entry point for AI agents",
    "Partner API access appears gated behind business onboarding; no self-serve signup evidence",
    "Auth flow not documented publicly; likely enterprise/partner negotiation required",
    "robots.txt shows test/dev paths, suggesting a complex domain with non-public surfaces",
    "Value prop for AI agents is unclear — primarily a consumer food-ordering site"
  ],
  "recommendations": [
    "Publish llms.txt with a concise overview of capabilities and endpoints",
    "Expose a public developer portal with sandbox API keys and magic-link or OAuth signup",
    "Document pricing tiers or at least a range so agents can set user expectations",
    "Provide structured API specs (OpenAPI) for restaurant/menu/order data",
    "Add a status page and uptime SLA to strengthen consistency signals",
    "Clarify error semantics and rate limits in public docs"
  ]
}