[Integrations](https://spiral.ai/integrations) › [Muse Code](https://spiral.ai/integrations/muse-code) › [NASA POWER climate averages](https://spiral.ai/integrations/muse-code/nasa-power-climate-averages)

# How to Use NASA POWER climate averages in Muse Code

Returns monthly climate averages for temperature, precipitation, solar radiation, and other weather measures over a predefined reference period. Use it to put a recent season in context and identify departures from typical conditions.

|  |  |
| --- | --- |
| Model | NASA POWER climate averages |
| Available through | Alexandria |
| Category | Listings |
| Price | $0.00873 per call. |
| Returns | json |
| Runs | In the background |
| Setup | About 2 minutes, no API key |

## Prompts to try with NASA POWER climate averages in Muse Code

- Use NASA POWER climate averages for Phoenix, Arizona, at 33.45, -112.07. Add a monthly solar radiation baseline chart to the project and label the returned reference period.
- Use NASA POWER climate averages to look this up and give me the result as a table. Save the result in ./assets.
- Pull the latest numbers from NASA POWER climate averages and tell me what changed since last week.
- Check NASA POWER climate averages and summarize what you find in three bullet points.
- Pull the newest data from NASA POWER climate averages and give me the result as a table.

## How to set up NASA POWER climate averages in Muse Code

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

### Use Spiral's MCP server

1. **Install Muse Code**

```bash
curl -fsSL https://dev.meta.ai/install.sh | bash
```

2. **Ask Muse to add the server**: Start `muse` and ask:

```text
Add the Spiral MCP server at https://api.spiral.ai/mcp
```

3. **Sign in**: In your terminal, run:

```bash
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.

```bash
npx -y spiral-cli@latest init
```

### Call the Spiral API

1. **Create an API key**: In the console, under API keys.

2. **Run NASA POWER climate averages**: One request; the result comes back by polling or a webhook.

```bash
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": "power-larc-nasa-gov/weather-history/climate_normals",
    "input": {
      "geometry": {}
    }
  }'
```

Then paste one of the prompts above: Muse Code finds NASA POWER climate averages on Spiral, shows the price and runs it.

Setup guide in the docs: https://spiral.ai/docs/quickstarts/muse-code

## NASA POWER climate averages tools and prices

- [NASA POWER · Climate normals](https://spiral.ai/tools/alexandria/power-larc-nasa-gov/weather-history/climate_normals) (Alexandria): $0.00873 per call.

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| parameters |  | — | POWER climatology parameter codes (`list_parameters` with temporal `climatology`). Default: T2M, T2M_MAX, T2M_MIN, PRECTOTCORR, ALLSKY_SFC_SW_DWN, RH2M, WS2M. |

## What can you do with NASA POWER climate averages in Muse Code?

Build a crop-weather report that combines NASA POWER's documented measures with the project's study locations. A coding agent can turn the results into tables and charts while preserving the difference between daily events, monthly history, climate averages, and modeled soil wetness.

### Review a completed growing season

Build a season review for a point near Ames, Iowa. Select documented measures, examine daily heat and rainfall, compare monthly conditions across years, add the climate baseline, and describe root-zone wetness through the season.

### Explain persistent dry conditions

Investigate a point near Fresno, California, using daily rainfall, monthly history, climate averages, and root-zone wetness. Check definitions and units before describing whether low rainfall coincided with sustained soil drying.

### Compare crop sourcing regions

Prepare a weather context brief for representative points near Ribeirão Preto and Londrina, Brazil. Compare rainfall, heat, seasonal baselines, and root-zone wetness using consistently defined measures.

### Prepare environmental inputs for crop research

Assemble documented weather inputs for a crop study near Toowoomba, Australia. Use daily records for event timing, monthly records for seasonal comparisons, climate averages for context, and root-zone wetness as an additional environmental measure.

### Check solar resource seasonality

Compare monthly solar radiation near Phoenix, Arizona, across several years and against climate averages. Inspect daily values during unusually weak months and use the parameter definitions to keep the radiation measures and units consistent.

### Add weather context to building energy analysis

Compare an existing building's energy records with temperature history near Chicago, Illinois. Use daily temperatures to examine particular periods, monthly history for seasonal comparisons, and climate averages to describe how unusual the weather was.

## Overview

- [Alexandria](https://spiral.ai/providers/alexandria)
- [All Muse Code guides](https://spiral.ai/integrations/muse-code)

## NASA POWER climate averages in other agents

- [Amp](https://spiral.ai/integrations/amp/nasa-power-climate-averages)
- [ChatGPT](https://spiral.ai/integrations/chatgpt/nasa-power-climate-averages)
- [Claude](https://spiral.ai/integrations/claude-desktop/nasa-power-climate-averages)
- [Claude Code](https://spiral.ai/integrations/claude-code/nasa-power-climate-averages)
- [Cline](https://spiral.ai/integrations/cline/nasa-power-climate-averages)
- [Codex](https://spiral.ai/integrations/codex/nasa-power-climate-averages)
- [Cursor](https://spiral.ai/integrations/cursor/nasa-power-climate-averages)
- [Devin](https://spiral.ai/integrations/devin/nasa-power-climate-averages)
- [dots](https://spiral.ai/integrations/dots/nasa-power-climate-averages)
- [Factory Droid](https://spiral.ai/integrations/factory-droid/nasa-power-climate-averages)
- [Gemini](https://spiral.ai/integrations/gemini/nasa-power-climate-averages)
- [Gemini CLI](https://spiral.ai/integrations/gemini-cli/nasa-power-climate-averages)
- [Google Antigravity](https://spiral.ai/integrations/antigravity/nasa-power-climate-averages)
- [goose](https://spiral.ai/integrations/goose/nasa-power-climate-averages)
- [Grok](https://spiral.ai/integrations/grok/nasa-power-climate-averages)
- [Grok Build](https://spiral.ai/integrations/grok-build/nasa-power-climate-averages)
- [Hermes](https://spiral.ai/integrations/hermes/nasa-power-climate-averages)
- [Instinct](https://spiral.ai/integrations/instinct/nasa-power-climate-averages)
- [Manus](https://spiral.ai/integrations/manus/nasa-power-climate-averages)
- [Muse](https://spiral.ai/integrations/muse/nasa-power-climate-averages)
- [n8n](https://spiral.ai/integrations/n8n/nasa-power-climate-averages)
- [Notion](https://spiral.ai/integrations/notion/nasa-power-climate-averages)
- [OpenClaw](https://spiral.ai/integrations/openclaw/nasa-power-climate-averages)
- [opencode](https://spiral.ai/integrations/opencode/nasa-power-climate-averages)
- [Perplexity](https://spiral.ai/integrations/perplexity/nasa-power-climate-averages)
- [Raycast](https://spiral.ai/integrations/raycast/nasa-power-climate-averages)
- [VS Code](https://spiral.ai/integrations/vscode/nasa-power-climate-averages)
- [Windsurf](https://spiral.ai/integrations/windsurf/nasa-power-climate-averages)
- [Zapier](https://spiral.ai/integrations/zapier/nasa-power-climate-averages)

## More Muse Code guides

- [Montgomery County permit search](https://spiral.ai/integrations/muse-code/montgomery-county-permit-search)
- [NASA POWER daily weather history](https://spiral.ai/integrations/muse-code/nasa-power-daily-weather-history)
- [Montgomery County permit details](https://spiral.ai/integrations/muse-code/montgomery-county-permit-details)
- [NASA POWER monthly weather history](https://spiral.ai/integrations/muse-code/nasa-power-monthly-weather-history)
- [Montana address and road updates](https://spiral.ai/integrations/muse-code/montana-address-and-road-updates)
- [NASA POWER root-zone soil wetness](https://spiral.ai/integrations/muse-code/nasa-power-root-zone-soil-wetness)

## Questions about NASA POWER climate averages in Muse Code

**Can Muse Code use NASA POWER climate averages?**

Yes. Add Spiral to Muse Code as an MCP server, and Muse Code can find and run NASA POWER climate averages like any built-in tool.

**How much does NASA POWER climate averages 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 NASA POWER climate averages in Muse Code?**

No. Spiral runs NASA POWER climate averages on its own Alexandria account. You sign in to Spiral once and never paste a key.

**How long does it take to set up NASA POWER climate averages in Muse Code?**

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

**Does Muse Code wait while NASA POWER climate averages runs?**

NASA POWER climate averages runs in the background. Muse Code starts the run, checks on it and gives you the json when it's ready.

**How much geographic detail does NASA POWER provide?**

NASA POWER serves worldwide weather and solar data on source grids. NASA lists meteorology at 0.5 by 0.625 degrees and solar data at 1 by 1 degree, so a location query should not be interpreted as a measurement taken inside an individual field.

**How recent is NASA POWER data?**

NASA reports typical delays of two to three days for meteorological data and five to seven days for solar data. These are archive availability delays, so the latest weather and solar dates can differ.

**How far back does the weather record go?**

NASA documents daily coverage beginning January 1, 1981. The start date depends on the measure, so that date does not establish the history available for every solar or derived parameter.

**Can historical values change?**

Yes. NASA replaces recent meteorological products with improved climate-quality products within two to three months, so an earlier download and a later download can contain different values for the same dates.

**Is every weather measure available at every time scale?**

No. NASA explicitly states that parameter availability varies by community and temporal level, so availability in daily history does not establish availability in monthly history or climate averages.

