Vonage Integration Suite

{
  "service_type": "platform",
  "base_url": "https://integrate.vonage.com",
  "auth_method": "api_key",
  "auth_config": {
    "note": "Vonage Integration Suite API requires application subscription via Vonage dashboard; uses Vonage API key/secret or JWT authentication for API access.",
    "subscription_required": true,
    "dashboard_url": "https://dashboard.nexmo.com"
  },
  "endpoints": [
    {
      "name": "Call Control",
      "description": "Control active calls (hangup, transfer, mute, etc.) via Vonage Integration Suite API",
      "type": "REST",
      "authenticated": true
    },
    {
      "name": "Call Event Webhooks",
      "description": "Receive webhook callbacks for call events (answered, ringing, completed, etc.)",
      "type": "webhook",
      "authenticated": false
    },
    {
      "name": "Vonage Integration Suite Portal",
      "description": "Web-based portal for managing integrations and configurations",
      "url": "https://integrate.vonage.com",
      "type": "web_ui"
    }
  ],
  "pricing_model": {
    "type": "subscription",
    "details": {
      "note": "Part of Vonage Communications Platform; usage-based pricing on Vonage APIs. Integration Suite may require specific plan or enterprise agreement.",
      "pricing_url": "https://www.vonage.com/communications-apis/pricing/"
    }
  },
  "rate_limits": {
    "note": "Vonage API standard rate limits apply; exact limits depend on account tier and API. Typically documented per endpoint in Vonage developer docs."
  },
  "capabilities": [
    "call_control",
    "webhooks_for_call_events",
    "integration_suite_portal",
    "protocol_agnostic_telephony_control",
    "event_subscription",
    "application_subscription_management",
    "real-time_call_manipulation"
  ],
  "raw_analysis": "Vonage Integration Suite is a platform within the Vonage Communications Platform (formerly Nexmo) that provides APIs for call control and webhook-based call event notifications. The URL integrate.vonage.com appears to be the web portal for the Integration Suite, built as a single-page Angular application (ng-csp, ui-view, md-progress-linear indicate AngularJS with Angular Material). Access to the API requires an application to subscribe to the VonageIntegrationSuite API suite through the Vonage dashboard.\n\nTarget audience: Enterprise developers and businesses integrating telephony/call control into their applications, contact centers, and communication workflows. It is not a standalone consumer tool but part of Vonage's CPaaS offering.\n\nMaturity: Vonage (acquired by Ericsson) is a major CPaaS provider with mature APIs, extensive documentation, and global telephony infrastructure. The Integration Suite appears to be an enterprise-focused product, likely well-maintained.\n\nIntegrations: Fits into Vonage's ecosystem alongside Voice API, SMS API, Verify, etc. Webhooks enable event-driven integrations with external systems. No public REST API surface is exposed directly at integrate.vonage.com—it is the portal UI; the actual API is accessed via Vonage API endpoints (api.nexmo.com / api.vonage.com) after subscription.\n\nAuthentication: Uses Vonage API key/secret or JWT-based auth. The portal itself uses session-based login.\n\nPricing: Subscription/usage-based, consistent with Vonage's CPaaS model; exact pricing for Integration Suite may require contacting sales or checking enterprise plans."
}

3/3 tests passed

{
  "overall": 56,
  "dimensions": {
    "token_efficiency": 6.0,
    "first_try_success": 5.0,
    "response_parseability": 6.5,
    "error_clarity": 5.0,
    "doc_quality": 6.5,
    "auth_simplicity": 6.0,
    "latency": 9.5,
    "consistency": 7.5
  },
  "pricing_normalized": {
    "type": "subscription_plus_usage",
    "pricing_url": "https://www.vonage.com/communications-apis/pricing/",
    "note": "Part of Vonage Communications Platform; usage-based pricing on Vonage APIs. Integration Suite may require specific plan or enterprise agreement."
  },
  "issues": [
    "Website appears to be an Angular SPA — robots.txt and llms.txt return HTML with 200 status, indicating soft-404s that mislead agents expecting plain-text responses",
    "No dedicated llms.txt or machine-readable capability manifest — agents must scrape SPA HTML",
    "Auth flow not documented in provided data; Vonage Integration Suite typically requires Vonage account signup with enterprise SSO options, not magic-link",
    "Pricing is opaque — no normalized per-unit or tier details, requires navigating separate page",
    "Capabilities listed are inferred; no discoverable API spec (OpenAPI/AsyncAPI) surfaced",
    "Part of a larger platform (Vonage) — agents must disambiguate from Vonage API products"
  ],
  "recommendations": [
    "Publish a real llms.txt and robots.txt with proper content-type and non-HTML payloads so agent crawlers get accurate signals",
    "Expose an OpenAPI/AsyncAPI spec at a well-known path (e.g., /.well-known/openapi.json) for webhooks and call-control endpoints",
    "Document auth (API key, JWT, or SSO) in a concise machine-readable format near the docs root",
    "Provide a normalized pricing table (per-minute, per-event, per-seat tiers) so agents can compute cost without parsing marketing pages",
    "Hydrate SPA routes with prerendered HTML or a text-only fallback for non-browser clients",
    "Add a clear status/uptime page link and error code reference to improve error_clarity",
    "Clarify the distinction between Integration Suite (contact-center/agent-desktop product) and Vonage API platform in top-level docs to reduce token-heavy disambiguation"
  ]
}