D7SMS

```json
{
  "service_type": "platform",
  "base_url": "https://d7networks.com",
  "auth_method": "api_key",
  "auth_config": {
    "header": "Authorization: Bearer <API_TOKEN>",
    "notes": "D7 Networks retains API credentials (API Token / API User) via dashboard.d7networks.com. Exact header name may vary (Authorization: Bearer or api-key); verify against current docs."
  },
  "endpoints": [
    {
      "name": "Send SMS",
      "method": "POST",
      "path": "/messages/v1/send",
      "description": "Send SMS messages to one or more recipients via D7's global connectivity."
    },
    {
      "name": "Check Balance",
      "method": "GET",
      "path": "/messages/v1/balance",
      "description": "Retrieve account messaging credit balance."
    },
    {
      "name": "Message Delivery Report",
      "method": "GET",
      "path": "/report/v1/message-log",
      "description": "Fetch delivery status/report for sent SMS messages."
    }
  ],
  "pricing_model": {
    "type": "unknown",
    "details": {
      "notes": "Pay-per-SMS / wholesale-style pricing to global networks; rates vary by destination country and volume. No public self-serve price list in provided content — contact via d7networks.com for quotes."
    }
  },
  "rate_limits": {
    "notes": "Not specified in provided content. Typical SMS CPaaS throughput limits apply and are tier/account dependent."
  },
  "capabilities": [
    "Global SMS delivery over D7's own mobile network connectivity",
    "Bulk / A2P SMS messaging",
    "Two-way SMS (inbound and outbound)",
    "Delivery reporting and message logs",
    "REST API for programmatic sending",
    "Dashboard for account/credit management and API credential issuance",
    "Sender ID / alphanumeric sender support (region dependent)",
    "MT (Mobile Terminated) and MO (Mobile Originated) messaging",
    "Suitable for OTP, transactional, and marketing SMS use cases"
  ],
  "raw_analysis": "D7 Networks (D7SMS) is a Singapore-headquartered cloud communications / CPaaS provider offering business SMS services delivered over its own direct connections to global mobile networks. Positioned for B2B use cases (OTP, transactional alerts, notifications, marketing campaigns) across industries such as fintech, logistics, retail, and SaaS.\n\nNature of the platform: It is an API-first messaging platform, not purely a web dashboard. It does expose a REST API (historically documented as messages/v1 style paths under the D7 Networks developer docs) enabling programmatic send, balance lookup, and delivery reporting. It is commonly accessed through SMS gateway integrations rather than a generic public REST surface.\n\nAuthentication: Primarily API token / credential based, issued from the D7 dashboard (dashboard.d7networks.com). Exact header conventions should be confirmed against current API docs.\n\nIntegrations / ecosystem maturity: D7 SMS is frequently listed in SMS gateway directories and integrates with popular open-source and low-code stacks (e.g., integration marketplaces, notification tools, and CPaaS aggregators). It offers broad country coverage and wholesale-style pricing, positioning it as a cost-effective alternative to larger CPaaS incumbents.\n\nMaturity: Established provider with sustained presence in the SMS gateway space; strong in the APAC region with global reach. Public API documentation is available but not always prominently linked from the homepage, so API consumers should verify current endpoints, auth scheme, and rate limits directly via D7 Networks documentation before building.\n\nLimitations from provided content: Pricing is not publicly listed (quoted per destination/volume), and rate limits are account-tier dependent. No explicit mention of WhatsApp, RCS, or voice channels in the supplied content — the focus is SMS."
}
```

2/3 tests passed

{
  "overall": 58,
  "dimensions": {
    "token_efficiency": 8.0,
    "first_try_success": 5.0,
    "response_parseability": 7.0,
    "error_clarity": 4.5,
    "doc_quality": 6.0,
    "auth_simplicity": 5.0,
    "latency": 10.0,
    "consistency": 7.0
  },
  "pricing_normalized": {
    "pricing_model": "unknown",
    "has_public_pricing": false,
    "notes": "Pay-per-SMS, wholesale-style, destination- and volume-dependent. No public self-serve price list; quotes required via contact."
  },
  "issues": [
    "No public pricing — agents cannot surface a concrete cost/rate to users; requires sales contact for quotes.",
    "robots.txt disallows major agent-relevant paths: /docs/apis, /docs/faq, /docs/extensions, /api, /regulations/, /contact-us — blocks crawlers and AI agents from key docs.",
    "No llms.txt (404) — reduces agent-discoverable structured guidance.",
    "No transparent self-serve onboarding flow evidenced; API credentials require dashboard account setup.",
    "Sender ID / alphanumeric support and rates are region-dependent, adding variability and ambiguity."
  ],
  "recommendations": [
    "Publish a public, self-serve pricing table or at least a rate-per-country API/JSON endpoint for agent consumption.",
    "Add /llms.txt and /llms-full.txt describing capabilities, endpoints, auth, and rate limits.",
    "Reconsider robots.txt Disallow rules — open /docs/apis and /docs/faq to crawlers so agents can index API references.",
    "Expose a structured OpenAPI/Swagger schema and Postman/exportable collection to improve parseability.",
    "Simplify signup: magic link or API-key-first trial issuance so agents can get a working key in minutes.",
    "Add a public status page with uptime/SLA and clear rate-limit and error-code documentation.",
    "Document regional sender-ID rules and delivery-report formats in machine-readable form."
  ]
}