Muse Image

Advertised as muse-image
Quick reference
Muse Image — TLDR
  • 🆕 Meta's image generation and editing model, served via Meta Model API.
  • 🧠 A reasoning model: plans full layout before drawing anything.
  • 🎯 Anchored composition keeps edits consistent across repeated generations.
  • 🖼 Accepts text prompts plus reference images for editing and composition.
  • 🔧 OpenAI-style image generate and edit endpoints; base64 image output.
  • 📏 Multiple output sizes, including wide formats such as 1536 by 1024.
  • 💬 Self-reflects mid-chain-of-thought, patching drafts or regenerating them.
  • 🌐 Can switch to tool use when factual accuracy matters.
💰 Best price on Antseed
$0.030
per generated image · cheapest seller
🐜 Sellers
1
advertising on Antseed
🔬 Model checks
Not audited yet
no audit of this model so far
📏 Context
—
Provider

Meta Platforms is an American multinational technology company headquartered in Menlo Park, California. Best known for operating Facebook, Instagram, WhatsApp, and Threads, Meta has become one of the most influential players in open-weight AI research through its Llama family of…

Explore 6 more models by Meta Platforms →
About this model

Muse Image is Meta's image generation and editing model, exposed through the Meta Model API under the identifier for its 1.0 release. Unlike conventional diffusion-style endpoints that map a prompt straight to pixels, Meta describes it as a reasoning model: before drawing, it inspects any input frames and maps out the full layout — what goes where, how many elements there are, and how they relate to one another. That planning step is the model's defining architectural idea rather than a post-processing add-on.

The API surface covers three tasks: generating from text, editing existing images, and composing across multiple reference frames. Requests follow OpenAI-compatible image generation and image edit calls, with results returned as base64 data that clients decode to bytes, and with size arguments for formats such as 1536 by 1024 used in multi-panel comic workflows. Meta's own documentation walks through passing several reference files into a single edit call to keep characters and scenery stable across panels, which is what its anchored composition behavior is meant to support.

Meta also reports an emergent behavior it says was not explicitly designed: inside its chain of thought, Muse Image critiques its own drafts and revises them — making a local fix when a small detail is off, regenerating entirely when larger parts are wrong, or invoking tools when factual accuracy is at stake.

This catalog entry lists no earlier Muse Image generation, so there is no same-family predecessor to compare against; the model sits alongside Meta's broader Muse line of multimodal reasoning systems.

Sources
developer.meta.comMuse Image: generate, edit, and compose images on Meta Model API· developer.meta.combuild.nvidia.commuse-glimmer-30b Model by Meta | NVIDIA NIM· build.nvidia.comhuggingface.coMeta is back with Muse Glimmer: local, agentic, multimodal, and open source· huggingface.co

This About section is AI-generated from public sources via VeniceStats + Venice inference, with no human editing. It may contain inaccuracies.

Usage on Antseed · Muse Image
Images generated
5
6.60k tokens · 152.00 excl. image credit
Requests
5
settled calls
Buyers
2
distinct, on this model
Sellers used
1
of 1 advertising
Settled
$0.14
gross USDC, this model

Daily usage · Muse Image · Organic sellers

Sellers serving Muse Image (1)compare on the network explorer →
SellerHealthRep↓SalesImagesRouting$ / imgSave

"Best price" and the seller table are live Antseed catalog data (advertised $/1M tokens — or $ per generated image for unit-billed image models — not settled amounts). Reputation = buyer trust score (0-100, the Antseed SDK's own formula). "Routing" = the SDK's default buyer routing (what the VPR desktop app ships with): a trust ≥ 60 gate on the effective reputation, then cheapest-first among routable sellers; live failover state (per-peer cooldowns) is buyer-side runtime and not included. Model knowledge (TLDR, provider, About) via the VeniceStats enrichment layer. Advertised catalog, not the model used in any specific purchase. "Usage on Antseed" counts only settlements whose buyers share the per-model split on-chain (metadata v2/v3, opt-in), so every usage figure is a lower bound.