The Water Linked Underwater GPS API

{
  "service_type": "platform",
  "base_url": "https://waterlinked.com",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [
    {
      "path": "/api/",
      "method": "GET",
      "description": "Root API endpoint for the Water Linked Underwater GPS. Used as a discovery/health check endpoint per vendor recommendation."
    }
  ],
  "pricing_model": {
    "type": "unknown",
    "details": {
      "note": "Water Linked is a hardware manufacturer (underwater positioning/acoustics). The API is tied to a physical Underwater GPS product, not a SaaS subscription. Pricing is hardware-driven."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "underwater positional tracking (acoustics-based GPS)",
    "REST API served by the local Underwater GPS device",
    "likely exposes position, depth, heading, and heading/attitude data for subsea assets (ROV/AUV/divers)",
    "on-premise / vessel-local device API rather than a cloud service"
  ],
  "raw_analysis": "Water Linked is a Norwegian company building acoustic underwater positioning hardware (Underwater GPS). The provided listing describes 'The Water Linked Underwater GPS API' — importantly, this API is served by the physical Underwater GPS device on the vessel/ROV deployment, not by the public waterlinked.com website. The public site (waterlinked.com) is a marketing/corporate site for the hardware vendor.\n\nThe snippet explicitly recommends: 'If \"GET /api/\" times out, the Underwater GPS ...' — strongly implying the base URL for API calls is the device's IP address on the local network (or a tethered link), not the waterlinked.com domain. The listed URL (https://waterlinked.com) is therefore best treated as the vendor homepage rather than the API base.\n\nAuth: The product is a local embedded device; typical deployments use no authentication, or a simple shared-secret/on-device config. No public OAuth/key scheme is documented in the listing.\n\nEndpoints: /api/ is the only one we can infer with confidence. Real-world Water Linked API surfaces (based on the product family) expose JSON over HTTP from the device, covering things like position, heading, and acoustic fix quality, plus a WebSocket or polling stream for live position updates.\n\nAudience: marine robotics engineers, ROV/AUV operators, survey teams, and integrators building subsea navigation stacks.\n\nMaturity/Integrations: Established hardware vendor with a documented local API; integrations are typically with ROS, QGroundControl, survey software, and custom Python/C++ client code on the operator's laptop or control computer.\n\nRecommendation: Do NOT treat https://waterlinked.com as a machine-readable API base. Any integration must target the on-device IP (e.g. http://<underwater-gps-ip>/api/...) discovered via the product's setup flow. Because the platform is hardware-coupled and network-local, automated platform probing from the public internet is not meaningful."
}

2/3 tests passed

{
  "overall": 42,
  "dimensions": {
    "token_efficiency": 5.0,
    "first_try_success": 4.0,
    "response_parseability": 5.0,
    "error_clarity": 4.0,
    "doc_quality": 5.0,
    "auth_simplicity": 3.0,
    "latency": 7.0,
    "consistency": 5.0
  },
  "pricing_normalized": {
    "model": "hardware",
    "note": "No SaaS pricing tier. Water Linked sells physical Underwater GPS/positioning hardware. API is bundled with the device, not a metered or subscription service. Agents cannot recommend a price without hardware quote context."
  },
  "issues": [
    "Not a software/API platform in the traditional sense — it's a hardware product (Underwater GPS) with a local, vessel-side REST API. Agents recommending it to users expecting a cloud API will mislead.",
    "Weak first-try onboarding for agents: no self-serve signup; you need the physical device to exercise the API.",
    "No llms.txt (404) — reduced machine-readable discoverability for AI agents.",
    "Authentication flow unclear from public surface; likely device-local network auth with no documented agent-friendly path.",
    "Token-inefficiency for agent purposes: value prop requires explaining subsea acoustics hardware, not a crisp API integration story.",
    "Documentation quality not fully assessable from checks alone, but no clear getting-started/agent-friendly docs surfaced."
  ],
  "recommendations": [
    "Publish an llms.txt and a machine-readable API reference (OpenAPI) for the Underwater GPS local REST API, even if gated.",
    "Add a clear 'For Developers / Integrators' landing page stating the API is device-local, the auth model, and example endpoints (position, depth, heading).",
    "Provide a sandbox/simulator or sample JSON fixtures so agents and integrators can validate without hardware.",
    "Document practical limits (range, update rate, accuracy) and prerequisites so agents can set user expectations accurately.",
    "If targeting agent discoverability, add a concise value-prop page differentiating this from cloud SaaS positioning APIs.",
    "Expose a status/changelog page for consistency signals."
  ]
}