Locations

{
  "service_type": "platform",
  "base_url": "https://whapi.com",
  "auth_method": "unknown",
  "auth_config": {},
  "endpoints": [
    {
      "name": "Locations API",
      "path": "/locations",
      "method": "GET",
      "description": "Collection of methods that support geographical information. First method is an address lookup service for UK addresses."
    }
  ],
  "pricing_model": {
    "type": "unknown",
    "details": {}
  },
  "rate_limits": {},
  "capabilities": [
    "Geographical information services",
    "UK address lookup",
    "Address validation for new customer onboarding"
  ],
  "raw_analysis": "The 'Locations' service is exposed via whapi.com (a UK-based API gateway/aggregator, likely 'WHAPI' - possibly a WhatsApp/Whapi branded multi-service platform or a UK government-adjacent API hub). The only clearly documented capability is a UK address lookup service, intended to support things like new customer registration and address entry/validation. The URL format 'https://whapi.com:locations' is malformed (colon instead of a path separator), which suggests this listing may be auto-generated or scraped from a catalog rather than a curated API spec. There is no public REST documentation, auth scheme, or pricing information visible in the provided description. Maturity is unclear — the service appears to be a small, niche collection of geographical utilities rather than a full platform. Integrations are not described. As a 'platform' assessment, it currently offers very narrow functionality (UK address lookups) and would need to be evaluated directly with Whapi for auth, quotas, and SLA details before production use."
}

0/3 tests passed

{
  "overall": 18,
  "dimensions": {
    "token_efficiency": 4.0,
    "first_try_success": 1.0,
    "response_parseability": 2.0,
    "error_clarity": 1.0,
    "doc_quality": 1.0,
    "auth_simplicity": 3.0,
    "latency": 8.0,
    "consistency": 1.0
  },
  "pricing_normalized": {
    "model": "unknown",
    "notes": "No pricing information available; cannot normalize."
  },
  "issues": [
    "All endpoint checks failed with DNS resolution error '[Errno -5] No address associated with hostname' — the platform's domain appears unresolvable or offline.",
    "No reachable website, robots.txt, or llms.txt endpoints, meaning no discoverable documentation, auth flow, or API surface for agents.",
    "No structured data, API docs, or integration details could be verified.",
    "Pricing model is unknown, preventing cost-based recommendations.",
    "Cannot confirm uptime, security headers, or stability due to total unreachability."
  ],
  "recommendations": [
    "Verify the correct domain/URL for this geographical information service and re-run checks.",
    "If the platform is genuinely offline, do not recommend until it is reachable.",
    "Once reachable, publish llms.txt and robots.txt so agents can discover capabilities.",
    "Provide public API documentation with structured (JSON) address lookup formats for agent parseability.",
    "Clarify pricing tiers and expose a simple auth mechanism (API key or magic link) to reduce onboarding friction."
  ]
}