Spiral gives your agent every tool with one account. Browse the tools →

Muse · LLMReleased 2026-10-28

How to Use Particle-1 in Muse

Particle-1 is built for debugging, code changes, and data engineering. Post-trained on DeepSeek V4.1 Flash, it targets fewer reasoning and tool-call tokens while keeping task accuracy close to that model.

Prompts to try with Particle-1 in Muse

Copy an example into Muse, or ask in your own words.

Use Particle-1 to analyze the compiler error and code pasted above. Rank three likely causes and give me the smallest check for each.

Particle-1Muse
Try asking
  • Use Particle-1 to review the React component pasted above for broken row selection. Propose a correction and describe the regression tests.

  • Use Particle-1 to compare the SQL transformations pasted above. Explain where product IDs change type and suggest checks for failed joins.

  • Use Particle-1 to turn the feature request above into an implementation plan. List acceptance criteria, likely edge cases, and required verification.

  • Use Particle-1 with low reasoning effort to explain the short function pasted above in five sentences, including its inputs, return value, and failure behavior.

How to set up Particle-1 in Muse

Pick the way that suits you. Each takes about two minutes.

Use the Muse connector

  1. Create an API key

    Create one under API keys in the Spiral console.

  2. Send Muse this message

    Muse reads Spiral's skill and asks for an API key.

    set up https://spiral.ai/SKILL.md
  3. Give Muse the key

    Paste the key when Muse asks for it, never in the chat itself.

Use the Spiral skill

  1. Send Muse this message

    Your agent reads Spiral's skill and sets itself up.

    set up https://spiral.ai/SKILL.md
  2. Sign in or paste a key

    Approve Spiral in the browser, or give the agent a key from the console.

Use the Spiral CLI

  1. Install and sign in

    Installs the Spiral CLI, signs you in and adds its skill to your coding agents.

    npx -y spiral-cli@latest init

Call the Spiral API

  1. Create an API key

    In the console, under API keys.

  2. Run Particle-1

    One request; the result comes back by polling or a webhook.

    curl https://api.spiral.ai/v1/runs \
      -H "Authorization: Bearer $SPIRAL_API_KEY" \
      -H "Content-Type: application/json" \
      -H "Idempotency-Key: $(uuidgen)" \
      -d '{
        "provider": "openrouter",
        "model": "particle-ai/particle-1",
        "input": {
          "messages": [
            {
              "role": "system"
            }
          ]
        }
      }'

Then paste one of the prompts above: Muse finds Particle-1 on Spiral, shows the price and runs it.

Particle-1 providers and prices

Spiral runs Particle-1 through OpenRouter. Open a card for today's price, with every fee included.

OpenRouterLLM
Particle AI: Particle-1
particle-ai/particle-1

Settings you can ask for

Ask Muse for any of these in your prompt.

SettingAllowed valuesDefaultDescription
Seeda whole number
Min p0 to 1
Top ka whole number from 0
Top p0 to 1
Logprobson or off
Max tokens1 to 131072

The most output tokens to generate.

Temperature0 to 2
Top logprobs0 to 20
Presence penalty-2 to 2
Reasoning effortnone, minimal, low, medium, high, xhigh, or maxhigh

How much the model reasons.

Frequency penalty-2 to 2
Repetition penalty0 to 2

Every API field of Particle AI: Particle-1 is on its tool page: open its card above.

What can you do with Particle-1 in Muse?

Turn pasted code, error traces, and requirements into a focused engineering plan with Particle-1. Ask for evidence behind each diagnosis and a short verification checklist.

Fix a failing build

Use Particle-1 to inspect compiler errors, identify the cause, propose a targeted fix, and verify the build.

Repair a React interaction

Ask Particle-1 to correct broken navigation or row selection and check the affected behavior.

Correct dbt transformations

Have Particle-1 trace inconsistent types or key generation through a dbt project and propose tests.

Implement a codebase change

Give Particle-1 a concrete requirement and acceptance criteria, then request an implementation with regression checks.

Plan a debugging session

Provide an error trace and relevant code. Ask Particle-1 for ranked hypotheses and checks that distinguish them.

Triage recurring engineering failures

Use Particle-1 to review incoming build errors or data-job failures and draft investigation steps.

Produce structured engineering reports

Ask Particle-1 for JSON summaries of errors, proposed fixes, and verification evidence, then validate the results.

Questions about Particle-1 in Muse

Can Muse use Particle-1?

Yes. Add Spiral to Muse as an MCP server, and Muse can find and run Particle-1 like any built-in tool.

How much does Particle-1 cost in Muse?

Up to $0.002667 per run at the default inputs. $0.078 per 1M input tokens, $0.65 per 1M output tokens. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Muse plan is separate.

Do I need an OpenRouter account to use Particle-1 in Muse?

You need no OpenRouter account. Muse uses one Spiral API key for every tool, and Spiral runs Particle-1 on its own OpenRouter account.

How long does it take to set up Particle-1 in Muse?

About two minutes: create an API key, then send Muse this message, then give Muse the key.

Does Muse wait while Particle-1 runs?

Particle-1 runs in the background. Muse starts the run, checks on it and gives you the text, json when it's ready.

What is Particle-1 best suited for?

Particle-1 focuses on software engineering and data engineering. Its published evaluations cover terminal tasks, React fixes, dbt projects, and codebase changes.

How does Particle-1 compare with DeepSeek V4.1 Flash?

Particle-1 is post-trained on DeepSeek V4.1 Flash to use fewer tokens. Particle reports 28.4% to 52.2% fewer output tokens across four engineering benchmarks, with pass rates within the base model's confidence intervals.

How much context and output can Particle-1 handle?

The context window holds 1,048,576 tokens across the prompt and completion. The output ceiling is 131,072 tokens, including reasoning.

When should I reduce Particle-1's reasoning?

Consider lower effort for straightforward explanations or narrow edits, and compare results on representative tasks. Reasoning is enabled by default and consumes part of the output allowance.

Can I rely on Particle-1 to match a JSON schema?

Validate the result before your application uses it. Particle's documentation distinguishes valid JSON from guaranteed compliance with your application's schema.

Get started

Start using Particle-1 in Muse

One Spiral account for every tool your agent needs. No subscription; you pay per run.

Paste this into Muse:

Set up Muse

set up https://spiral.ai/SKILL.md
Are you an AI agent? See setup options