Meta API Setup: Auth and muse-spark-1.1 Model Configuration

This page covers how to configure authentication and select the muse-spark-1.1 reasoning model for the Meta API provider. It is intended for developers using the bundled OpenClaw plugin.

Read this when

  • You want to use Meta with OpenClaw
  • You need the MODEL_API_KEY env var or CLI auth choice

The Meta API relies on the OpenAI-compatible Responses API (POST /v1/responses) for the muse-spark-1.1 reasoning model. This provider is included as a bundled OpenClaw plugin.

PropertyValue
Provider idmeta
Pluginbundled provider
Auth env varMODEL_API_KEY
Onboarding flag--auth-choice meta-api-key
Direct CLI flag--meta-api-key <key>
APIResponses API (openai-responses)
Base URLhttps://api.meta.ai/v1
Default modelmeta/muse-spark-1.1
Default reasoninghigh (reasoning.effort)

Getting started

Set the API key

openclaw onboard --auth-choice meta-api-key
openclaw onboard --non-interactive --accept-risk \
  --auth-choice meta-api-key \
  --meta-api-key "$MODEL_API_KEY"
export MODEL_API_KEY=<key>

Verify models are available

openclaw models list --provider meta

Shows the static muse-spark-1.1 catalog entry. When MODEL_API_KEY is unresolved, openclaw models status --json reports the missing credential under auth.unusableProfiles.

Non-interactive setup

openclaw onboard --non-interactive --accept-risk \
  --mode local \
  --auth-choice meta-api-key \
  --meta-api-key "$MODEL_API_KEY"

Built-in catalog

Model refNameReasoningContext windowMax output
meta/muse-spark-1.1Muse Spark 1.1yes1,048,576131,072

Capabilities:

  • Text + image input
  • Tool calling and streaming
  • Reasoning effort: minimal, low, medium, high, xhigh (default: high)
  • Stateless encrypted reasoning replay (store: false, include: ["reasoning.encrypted_content"])

Warning

muse-spark-1.1 does not accept reasoning.effort: "none". OpenClaw maps --thinking off to minimal for this provider.

Manual config

{
  env: { MODEL_API_KEY: "<key>" },
  agents: {
    defaults: {
      model: { primary: "meta/muse-spark-1.1" },
      models: {
        "meta/muse-spark-1.1": { alias: "Muse Spark 1.1" },
      },
    },
  },
}

Note

If the Gateway runs as a daemon (launchd, systemd, Docker), make sure MODEL_API_KEY is available to that process, for example in ~/.openclaw/.env or through env.shellEnv. A key exported only in an interactive shell will not help a managed service unless the env is imported separately.

Smoke test

export MODEL_API_KEY=<key>
pnpm test:live -- extensions/meta/meta.live.test.ts

Live tests use muse-spark-1.1 against POST /v1/responses.