Head to head · LLM inference · October 2026 research run

Inkling 2 Small vs Muse Spark Open

Muse Spark Open scores 53.4 (D) on agent readiness against Inkling 2 Small's 52.1 (D), and leads in 3 of 7 scored categories. Inkling 2 Small leads on schema & documentation, security & auth, maintenance & community and transparency & trust. Both do llm inference.

Best model APIs and inference for AI agents · All 596 models comparisons

Which one, for what

Inkling 2 Small D

Best for Developers who want a capable multimodal open-family model through an OpenAI-compatible API today, or to fine-tune it on Tinker, and who can live with a beta surface until the weights are published.

Ahead on

  • Schema & documentation, 70 against 61
  • Security & auth, 57 against 44
  • Maintenance & community, 75 against 60
  • Transparency & trust, 64 against 53

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

Serverless inference and the OpenAI-compatible API are both labelled beta, with a waitlist for higher throughput

Muse Spark Open D

Best for A team with a four-GPU Blackwell node, or two to four Mac Studios, that wants a 1M-token multimodal coding and agent model on its own hardware with no prompts leaving it.

Ahead on

  • Reliability, 42 against 30
  • Agent ergonomics, 69 against 62
  • Payments & pricing, 50 against 20

Also in its favour

  • No key needed to call it

Watch for

The NVFP4 checkpoint (about 537 GB) serves on four B300 GPUs and the BF16 one (about 1.65 TB) on eight

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Payments & pricing Muse Spark Open +30

Inkling 2 Small 20

Published rubric. No payment protocol (0). Per-million-token prices for serverless inference and training published without a login on 6 November (20). No free tier listed, and the quickstart asks for payment details before training, per the tinker listing (0). Sign-up is a browser flow (0). 0 + 20 + 0 + 0 = 20.

Muse Spark Open 50

Self-hosted rule. Nothing to buy from Meta, and the licence grants use free of charge. The Model as a Service clause asks for a separate agreement only from licensee groups above $20M gross revenue in 12 months (20). Free to run with no card (20). Meta's own weights need a manually reviewed Hugging Face form with legal name and date of birth, or, since the 4 November re-read of Get the model, a signed-in download from Meta's own page, so an agent can't get them alone. The ungated GGUF quantisations from ggml-org and Unsloth that Meta's docs point to download without approval (the Unsloth repository is ungated on 4 November), so part of the line (10 of 20). No payment protocol (0). Hosted copies at $1.25 input and $4.25 output per million tokens need each provider's own account and are not graded. 20 + 20 + 10 + 0 = 50.

Maintenance & community Inkling 2 Small +15

Inkling 2 Small 75

Model reading. Released 5 November 2026 (30). Churn and notice in place of release counts: Inkling, Inkling-Small (30 July) and Inkling 2 Small in about four months, and a deprecations page with dated retirements and a promise to 'aim to give advance notice' by email, with no stated period, per the tinker listing (10 of 20). A public changelog and a support address and Discord, per the tinker listing (10 of 15). Current official SDKs, Tinker's Python SDK and the OpenAI-compatible endpoint (15). SDK and cookbook CI, per the tinker listing (10). 30 + 10 + 10 + 15 + 10 = 75.

Muse Spark Open 60

Read for an open-weight model released three weeks ago. Released on 15 October 2026 (30). One release, BF16 and NVFP4 on the same day, with no history of revisions, successors or notice periods, and Meta Model API has no deprecation policy either (6 of 20). None of the 29 replies counted by script on 4 November across the BF16 repository's discussions came from Meta. Feedback goes to the discussions or museoss@meta.com, and Meta's docs and developer blog carry dated posts (8 of 25). Day-one support in vLLM, SGLang, TensorRT-LLM, Transformers, llama.cpp, MLX and Unsloth with Meta's own recipes, though SGLang's is a dev image and TensorRT-LLM's a feature branch (12 of 15). Current dependencies (Transformers 5.19), but no CI visible to us (4 of 10). 30 + 6 + 8 + 12 + 4 = 60.

Security & auth Inkling 2 Small +13

Inkling 2 Small 57

Platform readings are the tinker listing's. Revocable API keys from the console, with no per-key scopes found (20). Org, team and project permissions with no read-only role (5). The model returns its own completions, no third-party content (10). get_audit_log() for admins (15). security.txt with a reporting address and no stated acknowledgement time (7). For the model reading, Tinker's terms commit not to use Customer Content for training, recorded under transparency. 20 + 5 + 10 + 15 + 7 = 57.

Muse Spark Open 44

Read as software the owner runs. No account or key to run it. Meta's weights need manual approval on Hugging Face and an access token, and server authentication is the owner's to add (12 of 30). An agent model that calls whatever tools the operator gives it. The card recommends human-in-the-loop confirmation for irreversible actions and Meta reports agentic-risk evaluations, but nothing in the model or template enforces an approval (8 of 20). The chat template neutralises special-token sequences and media placeholders in caller text and wraps tool results in <tool_output>, and the card advises protecting internal assistant messages and layering defences against adversarial input. No indirect prompt-injection results are published (10 of 15). No call log of its own. Visibility depends on the serving stack (5 of 15). Weights are safetensors that load through Transformers' own classes from 5.19, and Meta published cyber, chemical, biological and misalignment evaluations. dev.meta.ai/.well-known/security.txt answers 404 (re-read on 4 November), research.meta.ai per the 15 October check, and no security route is on the card or in the docs, only museoss@meta.com and the Hugging Face discussions (9 of 20). 12 + 8 + 10 + 5 + 9 = 44.

Reliability Muse Spark Open +12

Inkling 2 Small 30

Model reading, for the surface it's called on, Tinker's serverless inference and OpenAI-compatible API. No status page found, per the tinker listing's checks of 1 October and 4 November (0), so no readable incident history (5). The only published limit is the in-flight sample cap of 2,000, per the tinker listing's 1 October check; the OpenAI-compatible page gives no numbers and says higher or more stable throughput needs the waitlist (10). The SDK retries sampling with stable request IDs, per the tinker listing's reading of the SDK repository; the OpenAI-compatible page has no retry guidance (15). No SLA found (0). Serverless inference is 'currently in beta' on the models and pricing page and the OpenAI-compatible API is labelled Beta, read 6 November (0). 0 + 5 + 10 + 15 + 0 + 0 = 30.

Muse Spark Open 42

Read with the local-software lines, since the owner serves the weights. Meta's weights come from two Hugging Face repositories gated with manual review. The docs state Python 3.10 or later, Transformers 5.19 or later, Docker images for SGLang and vLLM and the GPUs for each checkpoint (4 × B300 for NVFP4, 8 × B300 for BF16), but SGLang's image is a dev tag and TensorRT-LLM's support sits on a feature branch (13 of 20). No CI or test suite of Meta's for the model was found. github.com/meta-models answered 403 to our fetcher, so its repositories are unchecked (0 of 25). On 4 November the BF16 repository's discussions page lists 13 open threads from 15 October to 1 November, 10 discussions and 3 pull requests (one a draft). A script counted 29 replies across the seven threads with replies, six discussions and the draft pull request, none from the repository owner or a Meta member, and their text wasn't read, so crash reports weren't separated from other posts (15 of 25, held from 15 October and flagged). No changelog, version tags or revision notes, and the commit history needs gated access (2 of 15). Released as a final checkpoint with no preview label from Meta, and both repositories unchanged since 15 October, though runtime support ships as launch-specific images and a branch, and Groq lists it as a preview (12 of 15). 13 + 0 + 15 + 2 + 12 = 42.

Transparency & trust Inkling 2 Small +11

Inkling 2 Small 64

Editorial half. Closed for now under the Tinker Terms of Use and the Model Acceptable Use Policy, per the model card, with Apache 2.0 weights promised the week after launch (15). Terms commit not to use Customer Content for training, keep it only as needed, with a DPA and deletion on request; the privacy notice wasn't re-read, per the tinker listing (15). Dated deprecation notices with no stated period (15). The DPA annex names Google Cloud, Cloudflare, WorkOS and OpenAI with service and location (15). 15 + 15 + 15 + 15 = 60.

Muse Spark Open 53

Weights are downloadable under the Muse Model Licence, which is clear and broad in its grant but not an OSI licence. It adds a display requirement, a separate agreement before Model as a Service by a licensee group above $20M gross revenue, and a Usage Policy with field-of-use limits (military, nuclear, espionage, critical infrastructure, heavy machinery) and an age limit of 18. It has no regional exclusion and no governing-law clause. Training code and data aren't released (18 of 30). Inputs stay on the owner's hardware, and Meta's docs say self-hosting keeps 'every prompt and response' inside the owner's infrastructure. The access form's details, and a download from Meta's own page after signing in, go to Meta under its general privacy policy, which we didn't read, and the training data is described in outline only (20 of 30). No deprecation policy, dated notices or versioning found (0 of 20). The Get the model page says everything runs offline once the weights land, and safetensors weights carry no code. No other telemetry statement, and Meta's download form records name, date of birth, country and IP location (12 of 20). 18 + 20 + 0 + 12 = 50.

Schema & documentation Inkling 2 Small +9

Inkling 2 Small 70

Model reading. No OpenAPI file of its own; the OpenAI-compatible chat and completions endpoints and the typed Python SDK are the contract, as the tinker listing reads it (15). llms.txt on the docs host, per the tinker listing's 1 October check (10). The model card states intended use (agentic and tool-use systems, coding assistants, chatbots, RAG), inputs, outputs and limitations, and the launch post its benchmarks (16 of 20). Model IDs, context lengths and the reasoning_effort values (none to xhigh, or 0.0 to 0.99) are documented; the tool-call format and structured output aren't, for this model (8 of 15). A Python example and an HTTP 400 for models without reasoning_effort, with no error page (6 of 15). A dated Tinker changelog and a model deprecations page, per the tinker listing (15). 15 + 10 + 16 + 8 + 6 + 15 = 70.

Muse Spark Open 61

Read for a model the owner serves. No specification of its own. The contract is the Jinja chat template, which renders OpenAI-format tools with additionalProperties: false added and rejects bad values, plus the OpenAI-compatible servers in vLLM and SGLang with the muse parsers (10 of 25). dev.meta.ai/llms.txt lists the Muse Spark Open overview and seven pages under it, plus three cookbook pages, each with a Markdown copy (10). The card lists seven intended uses and six limitations, the docs say when to pick BF16 or NVFP4 and which reasoning strength suits which task, and the Usage Policy states what is out of scope (17 of 20). reasoning_effort is an enum of four values and anything else returns an error, and tools take JSON Schema. Structured output is documented only for TensorRT-LLM's response_format, not in the prompting guide or for vLLM and SGLang (11 of 15). curl and Python examples for every runtime and hosted provider, the rendered prompt for each case, and the template's own error messages, but no error reference for a served model (11 of 15). One release, with no changelog or version scheme beyond the licence's version line, Muse Spark Open (2 of 15). 10 + 10 + 17 + 11 + 11 + 2 = 61.

Score by category

CategoryWeight this runInkling 2 SmallMuse Spark OpenEdge
Reliability16%203042Muse Spark Open +12
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27061Inkling 2 Small +9
Agent ergonomics13%16.26269Muse Spark Open +7
Security & auth14%17.55744Inkling 2 Small +13
Payments & pricing10%12.52050Muse Spark Open +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87560Inkling 2 Small +15
Transparency & trust7%8.86453Inkling 2 Small +11
Negative events≤1500
TotalD 52.1/100D 53.4/100

Facts side by side

FactInkling 2 SmallMuse Spark Open
KindModel APIModel API
VendorThinking Machines LabMeta
Hosted endpointhttps://tinker.thinkingmachines.dev/services/tinker-prod/oai/api/v1no (local only)
TransportsHTTP
AuthAPI keyNone
PricingPay per useFree
x402nono
LicenceProprietary for now, used through Tinker under the Tinker Terms of Use and Thinking Machines' Model Acceptable Use Policy, per the model card. Thinking Machines says it will publish the weights under Apache 2.0 the week after launch, once outside safety testing is doneMuse Model Licence (source-available weights, not an OSI licence), free of charge with an attribution notice, a separate agreement with Meta before Model as a Service by a licensee group above $20M gross revenue, and the Muse Spark Open Usage Policy
Read-only variant documentednono
llms.txtyesyes
Last release2026-11-052026-10-15
Terms last updatednot read yet2026-10-15
Privacy policy last updatednot read yetno document linked
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetnot found in the text
Terms or service can change without noticenot read yetnot found in the text
Arbitration or class-action waivernot read yetnot found in the text

How the scores have moved

Verdicts

Inkling 2 Small

A new multimodal mixture-of-experts model from Thinking Machines, callable today through Tinker's OpenAI-compatible endpoint at $0.30 and $1.00 per million tokens, with strong vendor-reported coding and agent scores. Tinker's serverless inference is beta, with no status page or SLA, and the weights aren't public yet.

Muse Spark Open

Muse Spark Open runs on the owner's hardware in seven runtimes, with OpenAI-compatible servers in vLLM and SGLang, standard tool calls, a 1M-token context and Meta's own serving docs. Serving the 537 GB NVFP4 checkpoint takes four B300 GPUs, Meta's download is gated by manual review, and the licence adds attribution and a revenue threshold for model resellers.

Before you call either

Inkling 2 Small

  1. Call https://tinker.thinkingmachines.dev/services/tinker-prod/oai/api/v1 with an OpenAI client and TINKER_API_KEY, using /chat/completions
  2. The serverless model ID is thinkingmachines/Inkling-2-Small:peft:262144:sampling-nvfp4, per Tinker's pricing page. The OpenAI page's examples use your own checkpoint paths, so confirm it before relying on it
  3. Pass reasoning_effort as none to xhigh or 0.0 to 0.99 (default 0.9); reasoning arrives in reasoning_content unless separate_reasoning is false
  4. Keep images between 40 and 4096 px a side, per the model card
  5. Validate JSON yourself, since structured output and the tool-call format aren't documented
  6. Plan for a move to open weights. When they publish, the open-weights listing will carry sizes and runtimes

Muse Spark Open

  1. Start vLLM or SGLang with --reasoning-parser muse --tool-call-parser muse (vLLM also --enable-auto-tool-choice), or tool calls come back as raw text
  2. Set reasoning_effort to low or medium for short tasks. The default is xhigh, reasoning can't be turned off, and other values return an error
  3. Stop only on <|eot|> and end of text. Stopping on <|eom|> cuts off tool calls and final answers
  4. Stream long generations and leave max_tokens room for reasoning, or content can come back empty with finish_reason length
  5. Don't call Meta Model API for this model. Use a self-hosted server or a hosted provider's model string, such as meta-models/muse-spark-open

Questions

Which is better for AI agents, Inkling 2 Small or Muse Spark Open?

Muse Spark Open scores 53.4 (D) on agent readiness against Inkling 2 Small's 52.1 (D), and leads in 3 of 7 scored categories. Inkling 2 Small leads on schema & documentation, security & auth, maintenance & community and transparency & trust.

Do Inkling 2 Small and Muse Spark Open need an API key?

Inkling 2 Small needs an API key. Muse Spark Open needs no key.

Can an agent call Inkling 2 Small and Muse Spark Open without installing anything?

Inkling 2 Small has a hosted endpoint at https://tinker.thinkingmachines.dev/services/tinker-prod/oai/api/v1. No hosted endpoint is listed for Muse Spark Open.

Other comparisons with Inkling 2 Small or Muse Spark Open

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.