Bandwidth

{
  "service_type": "platform",
  "base_url": "https://bandwidth.com",
  "auth_method": "unknown",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {}
  },
  "rate_limits": {},
  "capabilities": [
    "voice calling",
    "messaging (SMS/MMS)",
    "911 access",
    "phone number management",
    "SIP trunking",
    "call control",
    "programmable communications"
  ],
  "raw_analysis": "Bandwidth is a communications platform as a service (CPaaS) provider. It offers APIs for voice, messaging, and emergency services (911). The platform targets businesses needing to integrate voice and messaging capabilities into their applications.\n\nThe company is well-established in the CPaaS space, competing with Twilio, Vonage, and others. It provides a RESTful API for developers, but specific endpoint details were not provided in the input. Authentication likely uses API keys or tokens via HTTP headers.\n\nBandwidth is publicly traded (NASDAQ: BAND), indicating a mature, enterprise-grade service. Typical use cases include call centers, appointment reminders, two-factor authentication, and emergency calling.\n\nThe platform supports multiple integration methods, including direct API calls and SDKs for various programming languages. Without explicit endpoint documentation, I cannot list specific endpoints, but common ones would include /messages, /calls, and /numbers.\n\nPricing is usage-based, typical for CPaaS, with rates per minute for voice and per message for SMS. No rate limits were provided.\n\nGiven the lack of explicit API details in the input, I have marked auth_method and pricing_model as unknown, but the platform is clearly a communications API provider with the listed capabilities."
}

0/3 tests passed

{
  "overall": 18,
  "dimensions": {
    "token_efficiency": 5.0,
    "first_try_success": 1.0,
    "response_parseability": 3.0,
    "error_clarity": 1.0,
    "doc_quality": 3.0,
    "auth_simplicity": 2.0,
    "latency": 2.0,
    "consistency": 1.0
  },
  "pricing_normalized": {},
  "issues": [
    "All 3 health checks failed with SSL certificate expired — platform is currently unreachable via HTTPS, blocking any agent onboarding or evaluation.",
    "No accessible robots.txt or llms.txt, so agents cannot discover machine-readable guidance or API entry points.",
    "No security headers observed; TLS/security posture is degraded.",
    "Pricing model is unknown — no public pricing page reachable, meaning agents cannot inform users about cost.",
    "Capabilities overlap with Twilio-like CPaaS but no public API docs, auth docs, or SDK references were retrievable."
  ],
  "recommendations": [
    "Renew the TLS certificate immediately; without a valid cert, agents will hard-fail before any capability check.",
    "Publish a well-formed /llms.txt and /robots.txt describing endpoints, auth flow, and rate limits for agent consumption.",
    "Expose a public pricing page with per-minute SMS/voice and number rental costs in structured (JSON) form.",
    "Add OAuth2/magic-link onboarding and document it, so agents can complete signup without human intervention.",
    "Provide an OpenAPI spec and error-code reference to improve parseability and error clarity."
  ]
}