The SMS Works API

{
  "service_type": "platform",
  "base_url": "https://thesmsworks.co.uk",
  "auth_method": "unknown",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {
      "model_note": "Pay only for delivered texts; failed messages are refunded"
    }
  },
  "rate_limits": {},
  "capabilities": [
    "SMS sending",
    "SMS API for developers",
    "Delivery status tracking / refunds for failed messages",
    "Programmatic messaging integration"
  ],
  "raw_analysis": "The SMS Works is a UK-based SMS gateway/platform targeted at developers and businesses needing programmatic SMS delivery. Its primary offering is a REST-like HTTP API for sending text messages, with an emphasis on low cost and reliability. A notable billing characteristic is that customers are charged only for successfully delivered messages, with failed messages refunded—this is a meaningful differentiator versus many SMS providers that bill on submission rather than delivery.\n\nMaturity and audience: The service positions itself squarely at the developer/AI/automation category, suggesting SDKs/client libraries, documentation, and integration with common development stacks are likely. It is a commercial subscription/pay-as-you-go service rather than a free tool.\n\nIntegrations: Details beyond the core API are not provided in the source. Typical offerings from platforms like this include SDKs in multiple languages (PHP, Python, Node.js, etc.), webhooks for delivery receipts and inbound messages, and possibly plugins for platforms like WordPress or Zapier. None of these are confirmed here.\n\nGaps: The provided content does not disclose the exact authentication method (commonly an API key or JWT for this class of service), endpoint paths, versioning scheme, rate limits, pricing tiers per message, or coverage/sender-ID regulations. The base_url listed is the marketing site; the API likely lives on a separate subdomain (e.g., api.thesmsworks.co.uk) that is not provided.\n\nAssessment: This is a legitimate, functional SMS API platform with a clear developer focus and a delivery-based billing model. It is not a platform lacking a public API—it is explicitly an API-first product. The main limitation for integration planning is the absence of concrete technical specifics (auth, endpoints, limits) in the provided text, which would come from the official API documentation."
}

2/3 tests passed

```json
{
  "overall": 66,
  "dimensions": {
    "token_efficiency": 8.5,
    "first_try_success": 7.0,
    "response_parseability": 7.0,
    "error_clarity": 6.0,
    "doc_quality": 6.5,
    "auth_simplicity": 6.5,
    "latency": 9.0,
    "consistency": 7.5
  },
  "pricing_normalized": {
    "model": "usage-based",
    "notes": "Pay only for delivered SMS; failed messages refunded. No concrete per-message or tiered figures available."
  },
  "issues": [
    "No llms.txt — agents have no machine-readable product/API summary to consume.",
    "Pricing is underspecified; without concrete rates agents cannot estimate cost for users.",
    "robots.txt allows all but sitemap URL is malformed (missing scheme), reducing crawl reliability.",
    "Docs/limitations quality not verifiable from the checks; error handling semantics for the API are unclear.",
    "No visible evidence of a self-serve API key flow (magic link, etc.) — onboarding friction unknown."
  ],
  "recommendations": [
    "Publish an llms.txt with concise API capabilities, auth method, and endpoint summaries.",
    "Add explicit pricing tables (per-message tiers by country/volume) to the site and docs.",
    "Fix sitemap URL in robots.txt to include https:// scheme.",
    "Document API error codes, rate limits, and delivery-failure/refund semantics clearly.",
    "Expose a quickstart (sign up → API key → first SMS) with copy-paste examples; support SSO/magic-link for agent-assisted signup.",
    "Ensure stable uptime and surface a status page for reliability signals."
  ]
}
```