WhatsApp Business API

{
  "service_type": "platform",
  "base_url": "https://whatsapp.local",
  "auth_method": "unknown",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {}
  },
  "rate_limits": {},
  "capabilities": [
    "business messaging",
    "customer communication",
    "message templates",
    "webhooks",
    "media messaging"
  ],
  "raw_analysis": "WhatsApp Business API is Meta's enterprise-grade messaging platform that enables businesses to communicate with customers at scale via WhatsApp. It is designed for medium to large businesses, developers, and solution providers (BSPs) who need programmatic access to send and receive messages, automate notifications, and manage customer conversations. The platform is mature and widely adopted, with a robust ecosystem of official Business Solution Providers (BSPs) such as Twilio, MessageBird, and Vonage. Authentication typically involves a Meta Business account, phone number verification, and either a permanent access token or system user token; setup is often mediated through a BSP. The API exposes RESTful endpoints for sending messages (text, media, templates, interactive), receiving inbound messages via webhooks, and managing message templates. Pricing is conversation-based (per 24-hour conversation) and varies by region and conversation category (marketing, utility, authentication, service). Rate limits are applied per phone number and are tiered based on business verification and quality rating. Key integrations include CRM systems, helpdesks (Zendesk, Salesforce), e-commerce platforms, and custom backends. The service is not a standard open REST API in the sense of a public developer API with self-serve keys; access requires approval and often a BSP. The provided URL 'https://whatsapp.local' appears to be a placeholder; the actual API base is graph.facebook.com for the Cloud API or BSP-specific endpoints. No public self-service API endpoint list is available without authentication and business verification."
}

0/3 tests passed

{
  "overall": 15,
  "dimensions": {
    "token_efficiency": 3.0,
    "first_try_success": 1.0,
    "response_parseability": 3.0,
    "error_clarity": 1.0,
    "doc_quality": 1.0,
    "auth_simplicity": 2.0,
    "latency": 1.0,
    "consistency": 1.0
  },
  "pricing_normalized": {
    "model": "unknown",
    "notes": "No pricing information available; cannot normalize"
  },
  "issues": [
    "DNS resolution failed for all checks — domain name could not be resolved (Name or service not known)",
    "Website is unreachable; no HTTP status codes returned",
    "No robots.txt or llms.txt available for agent discovery",
    "No pricing information disclosed",
    "No security headers observed (moot given total unreachability)",
    "Cannot verify capabilities (messaging, webhooks, templates) against live documentation"
  ],
  "recommendations": [
    "Verify the platform domain is correct and currently active before recommending to users",
    "Do not recommend this platform to users in its current state — it appears offline or nonexistent",
    "If the domain is mistyped, re-run checks against the canonical URL",
    "If the platform is deprecated, flag it as unavailable in any catalog",
    "Before reconsidering, require: reachable homepage, published pricing, and llms.txt/robots.txt for agent discoverability"
  ]
}