Meta provider (run sessions on Meta's Muse Spark API)
Run Claude-Code-style sessions backed by Meta's Anthropic-compatible Muse Spark API, as an alternative to your Claude account. A Meta session looks and behaves like any other — same approvals, same modes, same cost tracking — and is set up with an API key rather than a sign-in.
On this page
What it is
Omniscio supports spawning Claude-Code-style sessions backed by Meta's Anthropic-compatible API — Meta's Muse Spark Model API (hosted at api.meta.ai) — as an additional provider, alongside claude (the default), codex, gemini, antigravity, deepseek, kimi, glm, and minimax. It is the fifth member of the anthropic-compat family.
Where to find it
Settings → Accounts — the Meta section is visible when Show alternative AI providers is on. That switch is on for fresh installs; if your saved setting is off, turn it on there. Once revealed, Meta appears as a provider in the normal session-creation pickers.
How it behaves
What the user sees
A Meta session looks identical in the sidebar and main pane to a Claude session — same status dots, same streaming bubbles, same Ctrl+Enter to send, same Plan / Auto-Accept / Bypass Permissions modes, same tool-call approval UI. The provider is invisible in normal chat. The only user-visible difference is the Meta icon (its infinity-loop mark in Meta blue, no text label) in the session header.
Tool-call behavior is identical to Claude because the same claude CLI binary is doing the talking — only the model and the upstream endpoint differ. There is no yolo / auto-approve mode like Gemini or Anti-Gravity; the standard Claude approval flow applies.
How to enable
Shown out of the box. Meta is an alternative provider, and the alternative-provider section is visible by default — Settings → Accounts → Show alternative AI providers ships ON (a profile that last saved before 3 Oct 2026 keeps the old Claude-only view until you turn it on). Switch that master OFF and the entire Meta setup section below is hidden in Settings → Accounts; switch it back ON and the Meta panel appears alongside Gemini, Codex, Anti-Gravity, DeepSeek, Kimi, GLM, and MiniMax. With the master off, the per-project "Default provider" radio collapses to a single Claude row and the session header's provider switcher (ChangeProviderButton) hides Meta — Meta effectively does not exist in the UI even if every gate below is configured. Your saved API key and "Allow Meta sessions" toggle are preserved across master-toggle flips.
You need the toggle below plus a way to pay for Meta — your own Meta API key, Omniscio credits, or both, with Meta's supply list (Settings → Accounts → Who pays & who serves) deciding which pays first (note: no binary check — same claude binary as Claude). The opt-in toggle leads and gates the key field — the API key input appears only once Meta is turned on, so a key can't be entered into a disabled provider (when off, a hint keeps the meta-api-key Settings-search anchor landable and a saved key is preserved):
- Settings → Accounts → Allow Meta sessions in any project — opt-in toggle, off by default; same security stance as the Codex/Gemini/DeepSeek/Kimi/GLM/MiniMax spawn guards. Turning it on reveals the key field below.
- Settings → Accounts → Meta → API key — paste a Meta Model API key from the Meta developer portal (US-only public preview at time of writing; $20 in free credits per new account). Encrypted at rest via Electron
safeStorage. Optional when Meta's supply list has an Omniscio credits row (a new user's list has one) — with no key saved, the session runs on your prepaid credits through the gateway. When both are present, the order of Meta's list decides which pays first. See model-vendors.md.
Once both are green, you can launch a Meta session in three ways:
- Per-launch override — on a fresh (zero-message) session, the ChangeProviderButton in the new session's main panel (the launch-config pickers on a fresh session) lets you pick a one-off provider before sending the first message. Non-ready providers appear
aria-disabledwith a short hint — "Add key" or "Set up" — and deep-link to the right Settings panel. - Per-project default — Edit Project dialog (three-dot menu → Edit) has a "Default provider" section listing every enabled provider. Pick Meta and the project's sidebar "+ New Session" button spawns Meta automatically.
- Programmatically — anything that creates a session with
provider: 'meta'(recipes, agent-driven sessions, the CLI control HTTP API). Same readiness gates apply on the backend.
Choosing the model
A fresh Meta session lets you pick the model in the launch-config pickers (next to the provider chooser). The list is registry-driven (MODELS_BY_PROVIDER.meta in provider-models.ts) and offers six ids, newest first:
| Id | What it is |
|---|---|
muse-wonder-1.0 |
Meta's first frontier model (2026-10-12) — strongest on long agentic tasks and coding, 1M context. Bills $4/M input, $20/M output, $0.20/M cache read — about 3-5× Muse Spark, which is why it is listed first but is not the default. Runs on your own Meta key or on Omniscio credits. |
muse-ember-1.0 |
Meta's newest and most efficient model (2026-11-09) — built for the work agents repeat all day: tool calls, coding subtasks, routing and extraction, with text/image/video/audio/PDF input and 1M context. Bills $0.10/M input, $0.50/M output, $0.004/M cache read — 12.5× cheaper on input than Muse Spark — and is not the default, on Meta's own guidance to reach for Spark or Wonder on hard single-shot work. Runs on your own Meta key or on Omniscio credits. |
muse-spark-1.3 |
The default. Meta's current flagship (2026-09-02) — its biggest jump yet on coding and agentic work, 1M context. |
muse-spark-1.2 |
The previous generation, kept pickable for pinning an older checkpoint. |
muse-spark-1.1 |
The original July-2026 flagship. |
muse-spark-1.3-contributor |
The same 1.3 model at a steep discount, in exchange for letting Meta train on your prompts. Runs only on your own Meta API key. Listed last and never the default — see the warning below. |
The three standard-tier Spark ids are 1M-context and bill at the SAME published rate — $1.25/M input, $4.25/M output, $0.15/M cache read. Meta's "almost too cheap to meter" framing for 1.3 is about capability per token, not a price cut: the standard-tier sticker has not moved since 1.1.
Muse Spark Open, Meta's open-weight model (2026-10-15), is not in this list. Meta's Model API does not serve it — Meta's docs say you run the weights yourself or use a hosted provider — so a Meta key cannot run it. Pick it on the OpenRouter engine instead (
meta/muse-spark-open, on your own OpenRouter key or Omniscio credits); see OpenRouter provider.
Use default spawns muse-spark-1.3 rather than omitting the model flag — Meta requires a real Muse id (the shared claude binary's built-in default is a Claude id that Meta's endpoint would reject), so the registry pins one via getProviderDefaultModel. The pin tracks the CURRENT flagship, so it moved 1.1 → 1.3 when 1.3 shipped. Meta has no separate "reasoning effort" knob in Omniscio. A Meta session never inherits your Claude default model (those are Claude ids its endpoint would reject).
The cut-price
-contributortier is offered — read the trade before you pick it. Meta sellsmuse-spark-1.3-contributorat $0.10/M input, $0.20/M output, $0.002/M cached input — roughly 12× cheaper on input than the standard tier — but its own listing states that prompts and outputs on that tier may be used to improve Meta's products, and Meta lists it as text-only where the standard tier is multimodal (inside Omniscio the Meta provider is registered without image support either way —images: falsein its registry capabilities). It is also rate-limited to 100 RPM against the standard tier's 3,000. It is never the default: "Use default" stays on the standard tier, so choosing it is always deliberate. Use it for work you are happy to hand over; keep the standard tier for private code and business data.It runs only on your own Meta API key — never on Omniscio credits. Omniscio credits go through Omniscio's gateway, which only uses tiers that do not train on your prompts, so it has no route for the contributor tier (and OpenRouter, which serves that lane, refuses the tier under the company account's data policy too). Meta's supply list therefore passes over its Omniscio credits row for this model, and the session runs on your own Meta key when that row can serve. With no own Meta key that can serve it, the session is refused before it starts, with a message naming the model and the two fixes: save your own Meta key (and keep its row in Meta's list in Settings → Accounts → Who pays & who serves) — or pick another model, such as Muse Spark 1.3 (the same model at the standard price). Before this check existed, such a session failed silently with an empty turn.
The tier is excluded only from OpenRouter's model picker, where its models arrive as one unlabelled entry among hundreds with nowhere to state that trade (
OPENROUTER_DROP_SUBSTRINGSinmodel-discovery-filters). The Meta picker is a short curated list, so it can say so on the entry itself.
Per-project default
Each project remembers a default provider in the projectDefaultProviders setting (a Record<projectId, ProviderId>). Empty by default — every project falls back to Claude. Change it from the project's three-dot menu → Edit → Default provider radios; the change persists immediately.
When a project's default is set to Meta but Meta isn't ready (toggle off or key missing), an Inbox card names the project and provider and says in plain words what is missing. Its button opens the Settings screen where the gap is fixed, and the card clears itself once the provider is usable. The project's sidebar row itself carries no readiness marker.
Error states and fixes
Two gap codes — fewer than Gemini/Codex because there is no separate binary to check:
| Gap | What it means | Click-to-fix lands you at… |
|---|---|---|
toggle-off |
"Allow Meta sessions" is OFF in Settings | Settings → Accounts → Allow Meta sessions toggle |
key-missing |
No row of Meta's supply list can serve (no Meta key, and no other row ready) | Settings → Accounts → Meta API key field, or Who pays & who serves |
Test your key. The Meta API-key field has a "Test key" button that checks your key against Meta's model list (https://api.meta.ai/v1/models) and returns one plain-language verdict: the key works, Meta rejected it, or Meta could not be reached (offering "Save anyway"). It proves the key is accepted — so a mistyped or revoked key surfaces before you spawn a session — but it does not check your credit balance or a particular model; those surface on the first turn, named by the handling below.
Retired / unavailable model. If a session's selected model is no longer accepted by Meta — either Omniscio has removed it from the picker or the vendor killed a still-listed id server-side — Omniscio surfaces a clear "this Meta model is no longer available — open the model picker and choose another" and parks the session as needs_you / recovery_failed, instead of silently retrying the rejected request into the generic placeholder-stuck give-up loop. This shares the same anthropic-compat guards the DeepSeek/Kimi/GLM/MiniMax siblings use. See provider-spawn-model-availability-contract.md.
The real reason, not a blanket "model unavailable." A Meta rejection arrives the same way regardless of cause — a synthetic placeholder with zero output — so when the rejection is not about the model (the account ran out of credit, the conversation outgrew the context window, the key became invalid, or you hit a rate limit), Omniscio reads Meta's actual error off that placeholder and surfaces the specific cause + fix: out of balance → top up the account, then resend; conversation too long → start a fresh session; bad/expired key → check the Meta key in Settings; rate-limited → wait a moment, then resend. This shares the exact classifyAnthropicCompatPlaceholderError path the DeepSeek/Kimi/GLM/MiniMax siblings use.
Cost tracking
Spend is recorded on the session itself: the claude CLI reports each turn's usage in its stream-json output, Omniscio re-prices it (below) and adds it to the session's running cost (sessions.cost_usd). The Stats → Spend views group that spend by the session's provider (meta), so Meta spend shows separately from Claude/Codex/Gemini. Meta session turns are not written to api_cost_log.
Cost is re-priced, not taken verbatim. The claude binary computes its total_cost_usd from its OWN (Claude) price table, which has no Muse Spark row — so it would bill Muse Spark at Claude rates. Meta is therefore costReporting: 'estimated', and Omniscio recomputes each turn's cost from the token counts × Meta's real per-M rate ($1.25 / 1M input, $4.25 / 1M output; model-pricing.ts MODEL_PRICING) via repriceAnthropicCompatTurnCost — the same token-pricing path its anthropic-compat siblings use. See central-ai-spend-contract.md.
Telemetry: every successful Meta spawn fires the spawn_non_claude_session feature event, recording { provider: 'meta', engine: 'anthropic-compat' } — no session ID, project ID, or prompt content.
Related
Related — minimax-provider.md
- minimax-provider.md — same shape (Anthropic-compat, no binary, spawn-env redirect), different vendor + key
- glm-provider.md — another
anthropic-compatsibling - kimi-provider.md — another
anthropic-compatsibling - deepseek-provider.md — the other
anthropic-compatsibling - switching-providers.md — the unified session-provider guide
- model-vendors.md — who pays for a Meta session (the supply list)
- provider-registry-contract.md — the DeepSeek + Kimi + GLM + MiniMax + Meta (
anthropic-compat) invariants
Last verified 2026-10-12