Whatsapp Web.Js

{
  "service_type": "platform",
  "base_url": "https://wwebjs.dev",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "free",
    "details": {
      "note": "whatsapp-web.js is an open-source library (MIT) with no cost. Users are responsible for their own WhatsApp account and any associated costs."
    }
  },
  "rate_limits": {
    "note": "No official rate limits imposed by the library. However, WhatsApp Web internal limits may apply. Excessive automation could lead to account restrictions."
  },
  "capabilities": [
    "Send and receive messages (text, media, documents, contacts, locations)",
    "Send and manage group messages",
    "Receive message events (new message, message ack, etc.)",
    "Manage contacts and groups",
    "Send surveys and polls",
    "Send buttons and list messages",
    "Handle incoming messages with customizable filters",
    "Session persistence (save and restore sessions)",
    "Multi-device support (WhatsApp Multi-Device)",
    "QR code authentication",
    "Puppeteer-based browser automation for WhatsApp Web"
  ],
  "raw_analysis": "whatsapp-web.js is an open-source Node.js library that provides a programmatic interface to WhatsApp by automating the WhatsApp Web browser client using Puppeteer. It is designed for developers who need to integrate WhatsApp messaging into their applications, such as for notifications, chatbots, or customer support. Key features include sending/receiving messages, media, location, contacts, group management, and event handling. The library does not expose a traditional REST API but rather a JavaScript API that developers use within their Node.js applications. Authentication is handled via QR code scanning, similar to WhatsApp Web. There are no direct costs for the library, but users must comply with WhatsApp's terms of service. Common use cases include automated messaging, chatbots, and notification systems. The project is actively maintained on GitHub with a significant community. It supports both single-device and multi-device modes. Potential risks include account bans if used for spam or violating WhatsApp policies. The library is mature and widely adopted, with extensive documentation available at wwebjs.dev."
}

1/3 tests passed

{
  "overall": 68,
  "dimensions": {
    "token_efficiency": 8.0,
    "first_try_success": 5.0,
    "response_parseability": 7.0,
    "error_clarity": 6.5,
    "doc_quality": 7.5,
    "auth_simplicity": 4.0,
    "latency": 9.5,
    "consistency": 6.5
  },
  "pricing_normalized": {
    "model": "free",
    "cost": 0,
    "notes": "Open-source MIT library; no platform fees, but users bear their own WhatsApp account risk (ToS, bans)"
  },
  "issues": [
    "Auth is non-trivial: requires QR code scan tied to a personal WhatsApp account, unsuitable for headless agent onboarding",
    "Requires Puppeteer/browser automation — heavy runtime dependency for agents",
    "No official WhatsApp API; violates WhatsApp ToS and risks account bans",
    "No llms.txt or robots.txt — poor machine-discoverability for agents",
    "No hosted API; agents must run and maintain the library themselves",
    "Session persistence needed to avoid repeated QR auth — friction for automation"
  ],
  "recommendations": [
    "Prefer official WhatsApp Business Cloud API for agent use cases requiring reliability and ToS compliance",
    "If recommending whatsapp-web.js, flag the ban risk and browser-automation overhead explicitly",
    "Add llms.txt to docs site to improve agent discoverability",
    "Document session restore patterns prominently for agent-friendly persistence",
    "Expose a thin wrapper API layer to decouple agents from Puppeteer internals"
  ]
}