Cohere Chat API (Command models) vs Muse Ember

Cohere Chat API (Command models) 67

Hosted lines. status.cohere.com (incident.io) lists each Command model and the endpoints as components (20). Its feed, read on 2 November 2026, shows two incidents in the 90 days from 4 August. 'Multiple Endpoint Disruptions' on 1 September 2026, from 15:41 to 19:47 UTC, degraded the embeddings endpoint, embed-v4.0, two rerank models and command-a-reasoning-08-2025 during a Google Cloud outage, rated minor and partial, and docs loading failed on 5 August. Nothing has been posted since 1 September, so minor incidents only (20). Chat limits are published per model, 20 requests a minute and 1,000 calls a month on a trial key and 500 a minute on a production key for Command A, R, R+ and R7B, while the four newest variants say contact sales (12 of 15). The errors page documents 429 with example messages that say to wait and try again later and links to the rate limits, with no Retry-After header, backoff timing or idempotency key, the reading cohere-embed takes of the same page (8 of 15). cohere.com/slo is titled Service Level Objective and its text is script-drawn, so it was unread and scores as absent (0). The v2 chat endpoint is the default docs version, but the sample response on the chat guide still carries is_experimental and the newest models are not open to production keys (7 of 10).

Muse Ember 40

Model reading, for the surface it's called on, Meta Model API. No status page with readable history, per the meta-model-api listing's 4 November check (0), so no readable incident history (5). Rate limits published per team and per model, 3,000 RPM and 4,000,000 TPM for muse-ember-1.0, read 9 November (15). 429 and 503 with Retry-After, backoff guidance and rate-limit headers, per the meta-model-api listing (15). No SLA found (0). Muse Ember carries no preview label, but the API opened as a public preview in July and no general-availability notice was found, so half, as for the platform (5). 0 + 5 + 15 + 15 + 0 + 5 = 40.

Cohere Chat API (Command models) 72

Model reading. The last dated release on the Chat endpoint is still North Small Translate on 9 September 2026, 54 days before this check. The last Command model is Command A+ on 20 May 2026. Rerank 5 (21 October) and Embed 5 (30 September) aren't chat changes, so we score the 90-day band (20 of 30). The deprecations page defines Active, Legacy, Deprecated and Shutdown and promises email notice, with no minimum notice period (6 of 12). No chat model was retired or announced for retirement in the last 90 days. The newest entry on the page is still two Aya models retired on 4 April 2026 (8 of 8). Dated changelog with four entries since 4 August (27 August, 9 September, 30 September, 21 October), one of them for a chat model (12 of 15). SDK issue replies not sampled (5 of 10). Python SDK 7.2.0 and 7.3.0, TypeScript 8.2.0 (19 October) and 8.3.0, and Go v2.20.0 tagged on 21 October 2026, Java at 1.12.0 (15). The Python SDK is generated from the OpenAPI file and has a CI workflow, whose runs we did not read (6 of 10).

Muse Ember 46

Model reading. Released 9 November 2026 (30). No deprecation policy or notice period found, per the platform reading (0 of 12). Dated launches on the API, the latest Muse Wonder on 12 October and Muse Ember on 9 November (8 of 8). No Model API changelog; a help centre with tickets (8 of 15). No SDK of Meta's own (0 of 15, 0 of 10). 30 + 0 + 8 + 8 + 0 = 46.

Cohere Chat API (Command models) 84

Model reading. Public OpenAPI 3.1 file cohere-openapi.yaml in cohere-ai/cohere-developer-experience, 43 operations, last changed 29 September 2026 (25). docs.cohere.com/llms.txt and a Markdown twin of every page by adding .md, though the llms.txt files list no pages (8 of 10). The v2 chat operation describes each of its 21 request fields with defaults and limits, and says less about when to prefer one option (16 of 20). Enums on tool_choice, safety_mode and thinking.type, numeric bounds on temperature, k, p and priority, with penalties bounded only in prose (12 of 15). Eight request examples on the operation and an errors page with sample messages for each status code, with error bodies carrying a message and no machine code (12 of 15). v1 and v2 live side by side in the path and the changelog is dated, but the OpenAPI file is version 1.0 throughout and its changes are committed as 'Add spec changes' with no per-change note (11 of 15).

Muse Ember 60

Model reading. No OpenAPI file; the Markdown reference is the contract, per the meta-model-api listing (0). llms.txt and Markdown copies of every page (10). The Muse Ember page and choose-a-model page say what to hand it and what not to (hard single-shot coding, knowledge-heavy questions, visual coding), with model ID, inputs, context, max output and effort range (18 of 20). JSON Schema tools and output, reasoning effort an enum, per the platform reading (12 of 15). Curl, Python and TypeScript examples and the platform's error guide (15). A versioned model ID and a dated launch post, with no API changelog (5 of 15). 0 + 10 + 18 + 12 + 15 + 5 = 60.

Cohere Chat API (Command models) 75

Closed service under a published SaaS agreement, MIT SDKs, and the docs say Command A+ weights are on Hugging Face under Apache 2.0, which we did not open (15 of 30). The Enterprise Data Commitments (5 December 2025) and the privacy policy (1 May 2026) agree on 30-day retention and a training opt-out. The SaaS agreement (8 April 2025) does not mention the opt-out and grants an irrevocable right to use and share API data, and the DPA is sent on request (16 of 30). Deprecations page with dated history back to 2024 and lifecycle terms, no minimum notice, and nothing newer than 4 April 2026 on 2 November, read at 15 as cohere-embed reads the same page (15 of 20). The trust centre names nine sub-processors with a location for each, all in the US, and Google Cloud US-Central as the data location, read at 20 as cohere-embed reads the same list (20 of 20).

Muse Ember 53

Editorial half. Closed model under the Model API terms, with clear terms and law; no weights and no parameter count, unlike Muse Spark Open and Muse Glimmer (15). Standard content isn't used for training, retention periods not stated outside zero retention (18 of 30). No deprecation policy or dated notices (0). A subprocessor list linked but not read, no data locations (8 of 20). 15 + 18 + 0 + 8 = 41.

Cohere Chat API (Command models) 35

No x402, MPP or L402 in the docs, the OpenAPI file or the pricing page (0). The docs say Command models are billed per input and output token. The pricing page, read on 2 November 2026, now carries per-unit prices in its own page data, Command R at $0.15 input and $0.60 output and Command R7B at $0.0375 and $0.15 per million tokens, with Command R+ 08-2024 at $2.50 and $10.00 among legacy prices and Command A+ shown as free. No price is published for Command A, Reasoning, Vision or Translate, so the line takes 15 rather than the full 20 (15 of 20). A trial key is created at sign-up and is free with no card (20). Sign-up is in a browser, and a production key needs an Owner to complete a Go to Production form (0).

Muse Ember 20

Published rubric. No payment protocol (0). Per-token prices for both tiers published without a login, read 9 November (20). No free API allowance found; billing needs a card, per the platform reading (0). Browser sign-up (0). 0 + 20 + 0 + 0 = 20.

Cohere Chat API (Command models) 55

Model reading. Bearer keys of two kinds, trial and production. Team roles are Owner and User, only Owners delete production keys, and a production key is shown in full once. No scopes, expiry or per-model restriction was found (18 of 30). Paying customers can switch training off under Data Controls, which implies it is on until they do, trial keys fall under the website terms, and the SaaS agreement grants an irrevocable right to use API data to improve the services and share it with third parties (8 of 20). Logged prompts and generations are deleted after 30 days unless flagged, and zero data retention needs approval (12 of 15). The dashboard shows usage history, and no customer audit log was found (2 of 15). The trust centre lists SOC 2 Type II, ISO 27001, ISO 42001, UK Cyber Essentials, penetration tests on request and a responsible disclosure policy with a bug bounty, per the 9 October check. cohere.com/.well-known/security.txt still answers 404 on 2 November and no public advisories were found, so the line takes 15, as cohere-embed and cohere-north read the same programme (15 of 20).

Muse Ember 64

Platform readings are the meta-model-api listing's of 4 November. Team keys, named, revocable, no scopes (20 of 30). Standard mode only, so content isn't used to train Meta models under the terms, with safety use reserved (17 of 20). Retention 'as needed' with zero retention through sales (10 of 15). Usage dashboard by model, no per-call log (5 of 15). No security.txt on dev.meta.ai, a bug bounty and a security commitments page, no named certification (12 of 20). 20 + 17 + 10 + 5 + 12 = 64.