Muse Ember vs StepFun API

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.

StepFun API 41

Model reading. Bearer API keys, revocable by deletion. Organisations can create one key per project, billed to a project's credit with a per-member cap. No scopes or read-only keys found (20 of 30). Training on API data is not off by default in plain words. The privacy policy (effective 7 August 2026) says StepFun may use and retain data to improve its models, including training and fine-tuning where law and program terms permit, and the terms name early-access programmes as one such case. No opt-out found (5 of 20). No retention period for prompts and outputs and no zero-retention option. IP addresses are kept three years (3 of 15). The console's usage details list each billed call by key, model and date, with export (8 of 15). No security.txt, bug bounty or certification found. A DPA with breach notification exists (5 of 20).

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.

StepFun API 28

No status page read. status.stepfun.ai refused our reader by robots.txt and the shell couldn't connect, so we couldn't establish whether it is a status page or read any history. Scored absent for both lines, with 5 for unreadable history, and named in the open questions (0 + 5). Rate limits published with numbers per tier, from 5 concurrent, 100 RPM and 500,000 TPM to 130, 2,600 and 13,000,000 (15). The error and exception guides say to retry 429, 500, 503 and 504 after a short delay, with no Retry-After header, backoff schedule or idempotency guidance (8 of 15). No SLA found in the terms or pricing (0). Step 5 Preview is labelled a preview (0).

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.

StepFun API 53

No OpenAPI or similar machine-readable contract found. The API reference is Markdown pages (0). llms.txt at platform.stepfun.ai/docs/llms.txt, and every page has a Markdown copy (10). The Chat Completions reference describes each parameter with its default, and the model page lists what Step 5 Preview supports, but little on when not to use an option (12 of 20). Tool definitions take JSON Schema parameters, structured output takes a JSON Schema with strict: true, and reasoning_effort is an enum of low, medium and high. No tool_choice parameter is documented (11 of 15). Worked requests and responses on each page, and an error table of eight codes with causes and fixes, but no error bodies (12 of 15). No API changelog. A model lifecycle page with dated retirements and announcement pages (8 of 15).