How to Use Firecrawl developer search in Muse Code
Firecrawl developer search returns ranked passages from public repository issues, merged pull requests, READMEs, and curated docs. Use it to investigate an error or check an API contract with source evidence.
Prompts to try with Firecrawl developer search in Muse Code
Copy an example into Muse Code, or ask in your own words.
Read package.json, then use Firecrawl developer search to investigate React hydration errors for our installed React version in facebook/react. Return the relevant passages and source URLs before proposing a patch.
Inspect our Next.js middleware, then use Firecrawl developer search to find documentation and merged pull requests about redirect loops in vercel/next.js. Explain which findings apply to our installed version.
Read our Pydantic models and dependency version, then use Firecrawl developer search to find pydantic/pydantic passages about migrating validators from version 1 to version 2. Draft the changes supported by those sources.
Inspect our SQLAlchemy session handling, then use Firecrawl developer search to find sqlalchemy/sqlalchemy passages explaining MissingGreenlet with AsyncSession. Connect the retrieved explanation to the relevant code.
Read our HTTP retry code, then use Firecrawl developer search to find urllib3/urllib3 documentation about Retry behavior for HTTP 429 responses. Compare the passages with our implementation.
How to set up Firecrawl developer search in Muse Code
Pick the way that suits you. Each takes about two minutes.
Use Spiral's MCP server
- Install Muse Code
curl -fsSL https://dev.meta.ai/install.sh | bash
- Ask Muse to add the server
Start muse and ask:
Add the Spiral MCP server at https://api.spiral.ai/mcp
- Sign in
In your terminal, run:
muse mcp login spiral
Use the Spiral skill
- Send Muse Code this message
Your agent reads Spiral's skill and sets itself up.
set up https://spiral.ai/SKILL.md
- Sign in or paste a key
Approve Spiral in the browser, or give the agent a key from the console.
Use the Spiral CLI
- 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
- Create an API key
In the console, under API keys.
- Run Firecrawl developer search
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": "firecrawl", "model": "firecrawl/developer-search", "input": { "query": "<query>" } }'
Then paste one of the prompts above: Muse Code finds Firecrawl developer search on Spiral, shows the price and runs it.
Firecrawl developer search providers and prices
Spiral runs Firecrawl developer search through Firecrawl. Open a card for today's price, with every fee included.
Settings you can ask for
Ask Muse Code for any of these in your prompt.
| Setting | Allowed values | Default | Description |
|---|---|---|---|
| K | 1 to 100 | 10 | |
| Fork | on or off | Include or exclude forks. Applies to repository results only; sending it with no | |
| Skills | only | Set to | |
| Archived | on or off | Include or exclude archived repositories. Applies to repository results only; sending it with no | |
| Passages | 1 to 5 | 1 | |
| Max stars | a whole number from 0 | Upper bound on repository stars. Applies to repository results only; sending it with no | |
| Min stars | a whole number from 0 | Lower bound on repository stars. Applies to repository results only; sending it with no |
Every API field of Firecrawl Developer Search · Code and Docs is on its tool page: open its card above.
What can you do with Firecrawl developer search in Muse Code?
Build a dependency fix with passages from the project's docs, issues, and merged pull requests. A coding agent can compare that evidence with the installed version and the code it needs to change.
Investigate a dependency error
Search an error message with the library name, then compare issue reports and merged pull request passages for explanations and possible fixes.
Check an API contract
Find README and documentation passages that describe a method's return value, default behavior, or required arguments before implementing a call.
Prepare a dependency upgrade
Search for a named library, target version, and changed behavior. Use the returned passages and source links to assemble an upgrade checklist.
Explain why behavior changed
Compare documentation with merged pull request passages to identify the reasoning behind an API or framework change.
Draft a support answer with evidence
Turn relevant documentation and issue passages into an answer that links each explanation to its public source.
Review recurring dependency problems
Repeat searches for a specific public project's error or compatibility problem and compare the returned passages with earlier findings.
More on Firecrawl developer search and Muse Code
Overview
Firecrawl developer search in other agents
Questions about Firecrawl developer search in Muse Code
Can Muse Code use Firecrawl developer search?
Yes. Add Spiral to Muse Code as an MCP server, and Muse Code can find and run Firecrawl developer search like any built-in tool.
How much does Firecrawl developer search cost in Muse Code?
$0.003492 per 10 results. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Muse Code plan is separate.
Do I need a Firecrawl account to use Firecrawl developer search in Muse Code?
No. Spiral runs Firecrawl developer search on its own Firecrawl account. You sign in to Spiral once and never paste a key.
How long does it take to set up Firecrawl developer search in Muse Code?
About two minutes: install Muse Code, then ask Muse to add the server, then sign in.
Does Muse Code wait while Firecrawl developer search runs?
Firecrawl developer search runs in the background. Muse Code starts the run, checks on it and gives you the json when it's ready.
What material does Firecrawl developer search cover?
It covers public repository issues, merged pull requests, READMEs, and curated documentation sites. The documentation coverage is a selected index of sites.
How many results can one search return?
A search can return up to 100 ranked results. The default is 10.
Does it return source passages or just links?
It returns matched passages in Markdown alongside source links. Tables and code blocks survive in the passage text.
Does an empty search mean the documentation has no answer?
A requested documentation source can be absent from the index. When its indexed flag is false, nothing from that source can match, regardless of the question.
Can a successful search still be incomplete?
Yes. A partial response means the deadline passed before every search stage finished, so it contains only the work completed by that point.
Start using Firecrawl developer search in Muse Code
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into Muse Code:
set up https://spiral.ai/SKILL.md


