WhatPulse

{
  "service_type": "platform",
  "base_url": "https://developer.whatpulse.org/#web-api",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "freemium",
    "details": {
      "free_tier": "Basic account with limited features",
      "premium_tier": "WhatPulse Plus subscription",
      "description": "The client application is free to use, but advanced features and higher API rate limits require a paid subscription."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "Measure keyboard and mouse usage",
    "System metrics monitoring (CPU, memory, network)",
    "Application usage tracking",
    "Web API for accessing user stats and leaderboards",
    "Client API for integrating with the WhatPulse client"
  ],
  "raw_analysis": "WhatPulse is a desktop application that tracks keyboard and mouse usage, providing statistics on typing speed, clicks, and overall system usage. It also monitors system metrics like CPU, memory, and network activity. The platform is aimed at individual users who want to quantify their computer activity, as well as competitive users who enjoy leaderboards. It has been around since 2004, so it is mature. The developer portal offers two main API types: the Web API for accessing user data, and the Client API for interacting with the client application. The Web API is documented at the provided URL and includes endpoints for retrieving user stats, but the documentation does not specify authentication methods, but likely requires an API key. The platform is freemium; the basic client is free, but a paid 'WhatPulse Plus' subscription offers additional features. Integrations are limited to the official client and community scripts; no major third-party services are integrated. The developer documentation is hosted on a modern Docusaurus site, indicating active development. No rate limits are documented; they may be imposed on the API but not publicly specified."
}

3/3 tests passed

```json
{
  "overall": 62,
  "dimensions": {
    "token_efficiency": 7.0,
    "first_try_success": 5.5,
    "response_parseability": 6.5,
    "error_clarity": 5.0,
    "doc_quality": 6.5,
    "auth_simplicity": 5.0,
    "latency": 7.5,
    "consistency": 7.0
  },
  "pricing_normalized": {
    "free_tier": "Basic features free",
    "premium": "WhatPulse Plus subscription",
    "model": "Freemium",
    "api_access": "Limited on free tier"
  },
  "issues": [
    "Website has no dedicated llms.txt file - returns the same HTML page for robots.txt and llms.txt checks, indicating these are not real endpoints",
    "API requires client software installation and account tracking, making it niche and hardware-dependent",
    "Core value proposition (keyboard/mouse metrics) has limited general utility for most users",
    "Auth requires account creation and may need client app pairing - not as simple as SSO or magic link",
    "Free tier has limited API rate limits, which could frustrate agent-based integrations"
  ],
  "recommendations": [
    "Clarify whether llms.txt is actually implemented - all three checks returned identical HTML suggesting missing dedicated endpoints",
    "Provide clearer API documentation on rate limits and authentication for developers",
    "Add SSO or OAuth support for easier onboarding",
    "Consider making the client API more accessible without requiring the full desktop application"
  ]
}
```