{
 "categories": [
  "communications",
  "developer-tools"
 ],
 "deployment": "saas",
 "evidence": [
  {
   "date": "2026-10-08",
   "fact": "homepage",
   "note": "Sinch presents messaging, voice, and email APIs, plus verification, for builders and teams.",
   "source": "https://www.sinch.com/",
   "tier": "declared"
  },
  {
   "date": "2026-10-08",
   "fact": "license",
   "note": "The pricing page describes pay-as-you-go SMS and Voice API pricing. Functions pricing starts free and then charges for compute time.",
   "source": "https://sinch.com/pricing/",
   "tier": "declared"
  },
  {
   "date": "2026-10-08",
   "fact": "modalities.api.exists",
   "note": "The Conversation getting-started guide sends a text message with POST https://us.conversation.api.sinch.com/v1/projects/{project}/messages:send.",
   "source": "https://developers.sinch.com/docs/conversation/getting-started",
   "tier": "declared"
  },
  {
   "date": "2026-10-08",
   "fact": "modalities.api.kinds[0]",
   "note": "Sinch documents HTTPS calls that send a bearer token, including GET https://numbers.api.sinch.com/v1/projects/{project}/availableNumbers.",
   "source": "https://developers.sinch.com/docs/identity-access-management/authenticate/oauth2",
   "tier": "declared"
  },
  {
   "date": "2026-10-08",
   "fact": "modalities.api.auth[0]",
   "note": "The token endpoint is POST https://auth.sinch.com/oauth2/token with grant_type=client_credentials and HTTP Basic using the key ID and key secret. API calls then send Authorization: Bearer.",
   "source": "https://developers.sinch.com/docs/identity-access-management/authenticate/oauth2",
   "tier": "declared"
  },
  {
   "date": "2026-10-08",
   "fact": "modalities.api.auth[1]",
   "note": "The getting-started send uses HTTP Basic with the access key and access key secret, and says to use a short-lived OAuth 2.0 token in production.",
   "source": "https://developers.sinch.com/docs/conversation/getting-started",
   "tier": "declared"
  },
  {
   "date": "2026-10-08",
   "fact": "modalities.api.coverage",
   "note": "The opened guide covers Conversation send and inbound callbacks. The OAuth page also shows a Numbers call. Voice, Verification, and other Sinch products were not given the same endpoint pass, so coverage stays partial.",
   "source": "https://developers.sinch.com/docs/conversation/getting-started",
   "tier": "declared"
  },
  {
   "date": "2026-10-08",
   "fact": "modalities.sdk.exists",
   "note": "Sinch Skills document SDK installation and client initialization for Node.js, Python, Java, and .NET, and name the Node.js package @sinch/sdk-core.",
   "source": "https://developers.sinch.com/docs/ai-support/sinch-skills",
   "tier": "declared"
  },
  {
   "date": "2026-10-08",
   "fact": "modalities.sdk.official",
   "note": "The skills page is Sinch developer documentation and describes those SDKs as the Sinch SDK set for products that have SDK support.",
   "source": "https://developers.sinch.com/docs/ai-support/sinch-skills",
   "tier": "declared"
  },
  {
   "date": "2026-10-08",
   "fact": "modalities.sdk.languages",
   "note": "The Conversation getting-started guide offers Node, Java, .NET, and Python tabs for the send and inbound-message samples.",
   "source": "https://developers.sinch.com/docs/conversation/getting-started",
   "tier": "declared"
  },
  {
   "date": "2026-10-08",
   "fact": "modalities.mcp.first_party",
   "note": "The sinch/sinch-mcp-server README titles the project Sinch MCP Server, Developer Preview, and documents npm @sinch/mcp with tools for Conversation, Voice, Verification, Numbers, RCS, and WhatsApp. RCS must be enabled by contacting Sinch. Single-tenant HTTP mode does not authenticate inbound callers.",
   "source": "https://github.com/sinch/sinch-mcp-server",
   "tier": "declared"
  },
  {
   "date": "2026-10-08",
   "fact": "modalities.mcp.verdict",
   "note": "The server is published from the Sinch GitHub repository as a developer preview. It executes API tools. It is not described as a Sinch-hosted production endpoint.",
   "source": "https://github.com/sinch/sinch-mcp-server",
   "tier": "declared"
  },
  {
   "date": "2026-10-08",
   "fact": "modalities.cli.exists",
   "note": "Sinch documents npm install -g @sinch/cli, sinch auth login with project ID, key ID, and key secret, and CI variables SINCH_PROJECT_ID, SINCH_KEY_ID, and SINCH_KEY_SECRET.",
   "source": "https://developers.sinch.com/docs/functions/cli/installation",
   "tier": "declared"
  },
  {
   "date": "2026-10-08",
   "fact": "modalities.extensibility.webhooks",
   "note": "Conversation API clients can register up to five webhooks per app in the portal or at POST /v1/projects/{project}/webhooks. Triggers include MESSAGE_INBOUND and MESSAGE_DELIVERY.",
   "source": "https://developers.sinch.com/docs/conversation/callbacks",
   "tier": "declared"
  },
  {
   "date": "2026-10-08",
   "fact": "modalities.data_access.export[0]",
   "note": "The token endpoint returns a JSON body with access_token, token_type, expires_in, and scope.",
   "source": "https://developers.sinch.com/docs/identity-access-management/authenticate/oauth2",
   "tier": "declared"
  },
  {
   "date": "2026-10-08",
   "fact": "modalities.agent_docs.llms_txt",
   "note": "Opened https://developers.sinch.com/llms.txt. It is a plain-text map of Sinch developer documentation, starting with the Numbers API.",
   "source": "https://developers.sinch.com/llms.txt",
   "tier": "declared"
  },
  {
   "date": "2026-10-08",
   "fact": "verdict.scores.api",
   "note": "OAuth client-credentials tokens, bearer calls, and a documented Numbers request are a practical production path. Coverage of every Sinch product was not established on the opened pages, so the score stays at 8.",
   "source": "https://developers.sinch.com/docs/identity-access-management/authenticate/oauth2",
   "tier": "declared"
  },
  {
   "date": "2026-10-08",
   "fact": "verdict.scores.mcp",
   "note": "The official server executes messaging, voice, verification, and number tools, but the README marks it a developer preview and the single-tenant HTTP mode performs no inbound authentication.",
   "source": "https://github.com/sinch/sinch-mcp-server",
   "tier": "declared"
  },
  {
   "date": "2026-10-08",
   "fact": "verdict.scores.cli",
   "note": "sinch conversation send and the apps, contacts, messages, and webhooks commands support --json, and deletes support --non-interactive. The opened command page is the Conversation surface, and the install page says legacy voice v1 uses a separate application key.",
   "source": "https://developers.sinch.com/docs/functions/cli/commands/conversation",
   "tier": "declared"
  },
  {
   "date": "2026-10-08",
   "fact": "freshness.watch[0].url",
   "note": "Opened the Sinch MCP README. Developer preview. npm @sinch/mcp. Conversation, Voice, Verification, Numbers, RCS, WhatsApp, and a Mailgun email section.",
   "source": "https://github.com/sinch/sinch-mcp-server",
   "tier": "declared"
  },
  {
   "date": "2026-10-08",
   "fact": "freshness.watch[1].url",
   "note": "Opened the OAuth 2.0 access-token page, including the token endpoint, Basic key exchange, and bearer calls.",
   "source": "https://developers.sinch.com/docs/identity-access-management/authenticate/oauth2",
   "tier": "declared"
  },
  {
   "date": "2026-10-08",
   "fact": "freshness.watch[2].url",
   "note": "Opened the sinch conversation command page, including send, apps, webhooks, and --json output.",
   "source": "https://developers.sinch.com/docs/functions/cli/commands/conversation",
   "tier": "declared"
  },
  {
   "date": "2026-10-08",
   "fact": "freshness.watch[3].url",
   "note": "Opened the Sinch developer llms.txt documentation map.",
   "source": "https://developers.sinch.com/llms.txt",
   "tier": "declared"
  }
 ],
 "freshness": {
  "last_verified": "2026-10-08",
  "volatility": "high",
  "watch": [
   {
    "type": "mcp",
    "url": "https://github.com/sinch/sinch-mcp-server"
   },
   {
    "type": "docs",
    "url": "https://developers.sinch.com/docs/identity-access-management/authenticate/oauth2"
   },
   {
    "type": "docs",
    "url": "https://developers.sinch.com/docs/functions/cli/commands/conversation"
   },
   {
    "type": "docs",
    "url": "https://developers.sinch.com/llms.txt"
   }
  ]
 },
 "homepage": "https://www.sinch.com/",
 "id": "sinch",
 "license": "commercial",
 "modalities": {
  "agent_docs": {
   "llms_txt": true
  },
  "api": {
   "auth": [
    "oauth2-client-credentials",
    "basic"
   ],
   "coverage": "partial",
   "docs": "https://developers.sinch.com/docs/conversation/getting-started",
   "exists": true,
   "kinds": [
    "rest"
   ]
  },
  "cli": {
   "exists": true
  },
  "computer_use": {
   "issues": [],
   "viability": "unknown"
  },
  "data_access": {
   "export": [
    "json"
   ],
   "import": []
  },
  "extensibility": {
   "scripting": [],
   "webhooks": true
  },
  "integrations": {
   "make": "unknown",
   "n8n": "unknown",
   "power_automate": "unknown",
   "zapier": "unknown"
  },
  "mcp": {
   "first_party": true,
   "third_party": [],
   "verdict": "official"
  },
  "rpa": {
   "drivability": "unknown",
   "notes": "No repeatable UI probe was run. Conversation, Numbers, Voice, and Verification calls are documented as HTTP, and the developer-preview MCP server calls those APIs from a local or self-hosted process.\n",
   "ui_stack": [],
   "vendor_support": []
  },
  "sdk": {
   "exists": true,
   "languages": [
    "javascript",
    "java",
    "dotnet",
    "python"
   ],
   "official": true
  }
 },
 "name": "Sinch",
 "platforms": [
  "web"
 ],
 "related": {
  "alternatives": [
   "twilio",
   "telnyx",
   "infobip",
   "mailgun"
  ],
  "our_products": []
 },
 "schema_version": 1,
 "score_version": 1,
 "status": "active",
 "vendor": "Sinch",
 "verdict": {
  "best_path": "api",
  "scores": {
   "api": 8,
   "cli": 7,
   "computer_use": null,
   "integrations": null,
   "mcp": 6,
   "overall": 8,
   "rpa": null
  },
  "summary": "Sinch communications APIs are automatable today through documented REST calls. This record is Conversation messaging, Voice, Verification, and Numbers. It is not Mailgun or Mailjet. Production requests use a short-lived OAuth 2.0 bearer token from https://auth.sinch.com/oauth2/token. The token request is HTTP Basic with the access key ID and key secret and grant_type=client_credentials. The documented example returns expires_in 3600, and the page says tokens are typically one hour.     A Numbers example sends Authorization: Bearer to numbers.api.sinch.com. The Conversation getting-started guide also uses HTTP Basic with the same key pair for a test POST to https://us.conversation.api.sinch.com/v1/projects/{project}/messages:send, and it recommends OAuth for production. Inbound Conversation events are webhooks, at most five per app, created in the portal or by POST /webhooks. Official SDK material covers Node.js, Java, .NET, and Python. The sinch CLI (npm @sinch/cli) logs in with a project key pair, accepts SINCH_PROJECT_ID, SINCH_KEY_ID, and SINCH_KEY_SECRET in CI, and can send Conversation messages with --json. Sinch publishes a developer-preview MCP server as npm @sinch/mcp from github.com/sinch/sinch-mcp-server. Its tools send messages, place calls, start verification, and rent numbers. The same README lists Mailgun email tools, which stay on the Mailgun record. RCS must be enabled by contacting Sinch. The server runs locally or on a host you operate. Single-tenant HTTP mode does not authenticate callers. SMS and Voice pricing on the opened pricing page is pay-as-you-go. https://developers.sinch.com/llms.txt is a documentation map. Zapier, Make, Power Automate, and n8n were not opened. Computer-use viability is unassessed. The REST API scores 8 and is the best path. The CLI scores 7. The MCP preview scores 6.\n"
 }
}