API & OpenRouter
Muse Wonder API access: Meta vs OpenRouter setup guide
Connect to muse-wonder-1.0 on Meta or meta/muse-wonder on OpenRouter. Compare endpoints, API keys, billing and setup failures.
Last verified · Independent editorial guide
For Meta, use https://api.meta.ai/v1 and model muse-wonder-1.0 with a Meta API key. For OpenRouter, use https://openrouter.ai/api/v1 and meta/muse-wonder with an OpenRouter key. Wonder Full is not a public API option.
Choose the provider before copying a model ID
Editorial synthesis · Cited sources· Last verified
Meta and OpenRouter manage separate accounts, API keys, credits and billing. The model names and base URLs differ. A Meta key is not an OpenRouter key, even when the underlying model family is the same.
Meta’s official guide demonstrates the Responses API. The OpenRouter example here uses Chat Completions. Match the endpoint, request shape and model ID to the provider you actually selected.
Run a small, server-side request first
Editorial synthesis · Cited sources· Last verified
Create a project or account with the selected provider, confirm billing and regional eligibility, then create a key in that provider’s dashboard. Store it as a server environment variable and install the OpenAI Python package for the examples below.
Send a short prompt before connecting tools, long histories or autonomous loops. Inspect returned usage and your provider’s billing page before expanding the workload. This guide never asks you to paste a key into this site.
Troubleshoot the boundary that failed
Editorial synthesis · Cited sources· Last verified
For authentication errors, confirm the key belongs to the base URL you are calling. For model-not-found errors, check the provider-specific model ID and your account’s access. Increasing reasoning effort does not select Wonder Full.
For rate limits, respect Retry-After and use bounded backoff. For a schema error, check whether your client is sending a Responses or Chat Completions body. OpenRouter routing and provider policies can differ from direct Meta access.
Two providers, two complete examples
import os
from openai import OpenAI
client = OpenAI(
base_url="https://api.meta.ai/v1",
api_key=os.environ["MODEL_API_KEY"],
)
response = client.responses.create(
model="muse-wonder-1.0",
input="Explain this codebase's architecture.",
)
print(response.output_text)Keep your API key on the server. This example needs your own Meta API access and the OpenAI Python package.
import os
from openai import OpenAI
client = OpenAI(
base_url="https://openrouter.ai/api/v1",
api_key=os.environ["OPENROUTER_API_KEY"],
)
response = client.chat.completions.create(
model="meta/muse-wonder",
messages=[{"role": "user", "content": "Explain this codebase's architecture."}],
)
print(response.choices[0].message.content)Keep your API key on the server. This example needs your own Meta API access and the OpenAI Python package.
Frequently asked questions
Editorial synthesis · Cited sources· Last verified
What is the OpenRouter model ID?
The listed model ID is meta/muse-wonder. Direct Meta uses muse-wonder-1.0.
Can I call Muse Wonder Full through the API?
The checked Meta documentation lists Full only through eligible Muse Code subscriptions, not the public Model API.
Can I reuse the same key for Meta and OpenRouter?
No. Use credentials issued by the service in your base URL. Keep both keys on your own server.
Sources and verification
Provider pricing, model capabilities and access are distinguished from independent evaluations. The date records an editorial check; data is not refreshed automatically.