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

Muse Code · Maps & Reviews

How to Use Wildfire Risk to Communities place summary in Muse Code

Returns a named place's published risk classes, exposure fractions, metrics, and percentile ranks. Use it for a community or county briefing after identifying the place.

Prompts to try with Wildfire Risk to Communities place summary in Muse Code

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

Use Wildfire Risk to Communities place summary for Boulder County, Colorado, and build a report table showing risk classes, exposure fractions, and percentile ranks.

Wildfire Risk to Communities place summaryMuse Code
Try asking
  • Use Wildfire Risk to Communities place summary for Sonoma County, California, and add separate columns for annual burn probability and consequences if a fire occurs.

  • Use Wildfire Risk to Communities place summary to look this up and give me the result as a table. Save the result in ./assets.

  • Pull the latest numbers from Wildfire Risk to Communities place summary and tell me what changed since last week.

  • Check Wildfire Risk to Communities place summary and summarize what you find in three bullet points.

How to set up Wildfire Risk to Communities place summary in Muse Code

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

Use Spiral's MCP server

  1. Install Muse Code
    curl -fsSL https://dev.meta.ai/install.sh | bash
  2. Ask Muse to add the server

    Start muse and ask:

    Add the Spiral MCP server at https://api.spiral.ai/mcp
  3. Sign in

    In your terminal, run:

    muse mcp login spiral

Use the Spiral skill

  1. Send Muse Code 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 Wildfire Risk to Communities place summary

    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": "alexandria",
        "model": "wildfirerisk-org/wildfire-risk/place_summary",
        "input": {
          "id": "<id>"
        }
      }'

Then paste one of the prompts above: Muse Code finds Wildfire Risk to Communities place summary on Spiral, shows the price and runs it.

Wildfire Risk to Communities place summary providers and prices

Spiral runs Wildfire Risk to Communities place summary through Alexandria. Open a card for today's price, with every fee included.

AlexandriaMaps & Reviews
USFS Wildfire Risk to Communities · Place summary
wildfirerisk-org/wildfire-risk/place_summary

What can you do with Wildfire Risk to Communities place summary in Muse Code?

Build a planning report that connects named communities with modeled wildfire risk and geographic comparisons. A coding agent can turn those results into tables and map annotations in your project.

Prioritize county outreach

Find the county, compare its communities, and prepare place summaries for outreach planning. Sample the mapped landscape around proposed meeting areas to give organizers local geographic context.

Prepare a grant risk appendix

Locate the applicant community, collect its published risk summary, and compare it with nearby communities. Add mapped risk for the proposed project boundary as supporting landscape context.

Compare proposed growth areas

Screen proposed development polygons, identify their jurisdictions, and collect community summaries. Compare those communities within their counties to explain the regional context for a land use workshop.

Review landscapes around public facilities

Find the communities containing public facilities, sample the surrounding mapped risk, and compare community summaries and rankings. Use the results to organize follow-up local assessments.

Build a community comparison brief

Resolve similarly named places before comparing their published risk metrics and rankings. Explain differences between annual burn probability and consequences if a fire occurs.

Prepare tribal planning context

Find the relevant tribal area, collect its published summary, and inspect mapped risk across a proposed planning boundary. Keep the named jurisdiction and the project polygon clear in the resulting brief.

Explain a county ranking

Pair a county's published summary with a national county comparison. Show the underlying risk measures so readers can distinguish likelihood from potential consequences.

Create a place directory for planners

Resolve community names to source identifiers and attach their published risk summaries. Give planners a consistent starting point for reviewing communities across a service region.

Questions about Wildfire Risk to Communities place summary in Muse Code

Can Muse Code use Wildfire Risk to Communities place summary?

Yes. Add Spiral to Muse Code as an MCP server, and Muse Code can find and run Wildfire Risk to Communities place summary like any built-in tool.

How much does Wildfire Risk to Communities place summary cost in Muse Code?

$0.00873 per call. 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 an Alexandria account to use Wildfire Risk to Communities place summary in Muse Code?

No. Spiral runs Wildfire Risk to Communities place summary on its own Alexandria account. You sign in to Spiral once and never paste a key.

How long does it take to set up Wildfire Risk to Communities place summary in Muse Code?

About two minutes: install Muse Code, then ask Muse to add the server, then sign in.

Does Muse Code wait while Wildfire Risk to Communities place summary runs?

Wildfire Risk to Communities place summary runs in the background. Muse Code starts the run, checks on it and gives you the json when it's ready.

Which parts of the United States are covered?

The national raster datasets cover the contiguous United States, Alaska, and Hawaii. Their published spatial resolution is 30 meters.

How recent are the wildfire conditions behind the data?

The 2024 burn probability rasters reflect landscape conditions at the end of 2020. A recent lookup therefore does not mean the underlying vegetation or modeled likelihood has been refreshed recently.

Does Wildfire Likelihood show today's fire danger?

It describes annual burn probability from modeling. It does not incorporate currently forecast weather or current fire danger conditions.

Does a 30-meter pixel provide a home-level assessment?

Burn probability was originally modeled at 270 meters and resampled to 30 meters. The finer grid does not supply an independently modeled assessment of an individual building.

How do Risk to Homes and Wildfire Consequence differ?

Risk to Homes includes wildfire likelihood as well as intensity and generalized damage to a home. Wildfire Consequence describes potential damage conditional on a fire occurring, without annual burn probability.

Get started

Start using Wildfire Risk to Communities place summary 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 Muse Code

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