[Integrations](https://spiral.ai/integrations) › [Muse](https://spiral.ai/integrations/muse) › [AWS price file metadata](https://spiral.ai/integrations/muse/aws-price-file-metadata)

# How to Use AWS price file metadata in Muse

Returns source file metadata and columns for an AWS pricing publication. Use it to inspect the publication and CSV layout before importing product rows or reviewing a changed source file.

|  |  |
| --- | --- |
| Model | AWS price file metadata |
| Available through | Alexandria |
| Category | Finance |
| Price | $0.00873 per call. |
| Returns | json |
| Runs | In the background |
| Setup | About 2 minutes, with a Spiral API key |

## Prompts to try with AWS price file metadata in Muse

- Use AWS price file metadata for Amazon EC2. Explain the returned publication information and columns in plain English.
- Use AWS price file metadata to look this up and give me the result as a table.
- Pull the latest numbers from AWS price file metadata and tell me what changed since last week.
- Check AWS price file metadata and summarize what you find in three bullet points.
- Pull the newest data from AWS price file metadata and give me the result as a table.

## How to set up AWS price file metadata 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.

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

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

### Call the Spiral API

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

2. **Run AWS price file metadata**: 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": "pricing-us-east-1-amazonaws-com/cloud-pricing/source_status",
    "input": {
      "region": "<region>",
      "version": "<version>",
      "offer_code": "<offer_code>"
    }
  }'
```

Then paste one of the prompts above: Muse finds AWS price file metadata on Spiral, shows the price and runs it.

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

## AWS price file metadata tools and prices

- [AWS Price List Bulk API · Source status](https://spiral.ai/tools/alexandria/pricing-us-east-1-amazonaws-com/cloud-pricing/source_status) (Alexandria): $0.00873 per call.

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| offer_code |  | — | Offer code from offers_list, e.g. `AmazonEC2`, `AmazonRDS`, `AmazonS3` (the `offerCode` key of the offer index and the `serviceCode` CSV column). Pattern: ^[A-Za-z0-9]{2,64}$. |
| savings_plan_offer |  | — | Savings plan offer family from offers_list `savings_plan_offer`: `AWSComputeSavingsPlan`, `AWSDatabaseSavingsPlans` or `AWSMachineLearningSavingsPlans`. Pattern: ^[A-Za-z0-9]{2,64}$. |

## What can you do with AWS price file metadata in Muse?

Produce an AWS catalog research brief with service coverage and publication context. A chat app can explain what AWS publishes, which regional files are available, and how the catalog's product terms should be interpreted.

### Build an AWS catalog for an internal estimator

Discover published services, inventory their regional files and available versions, inspect source layouts, and import product rows. Keep the catalog publication alongside the estimator's assumptions.

### Prepare a weekly AWS catalog change digest

Compare service discovery results, regional coverage, publication history, source metadata, and collected rows with the previous run. Report catalog additions and changed product terms separately.

### Create a planning baseline for a cloud migration

Identify the AWS services under consideration, map their published regional coverage, and collect relevant product terms. Include publication history and source metadata so reviewers can identify the catalog used for the plan.

### Document the inputs to a procurement review

Assemble the service identifiers, regional file references, publication history, source layout, and product rows behind an AWS catalog comparison. Give reviewers enough evidence to trace each comparison to its source publication.

### Inspect Amazon S3 usage tiers

Inspect the price file's columns, then collect Amazon S3 product rows and separate storage and request terms by usage measurement and tier boundaries.

### Review publication activity before refreshing an import

Check Amazon EC2 publication history and inspect the current source metadata. Use the results to decide whether the existing catalog import needs review.

## Overview

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

## AWS price file metadata in other agents

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

## More Muse guides

- [npm publisher packages](https://spiral.ai/integrations/muse/npm-publisher-packages)
- [AWS pricing publication history](https://spiral.ai/integrations/muse/aws-pricing-publication-history)
- [npm package version details](https://spiral.ai/integrations/muse/npm-package-version-details)
- [AWS pricing region coverage](https://spiral.ai/integrations/muse/aws-pricing-region-coverage)
- [npm package search](https://spiral.ai/integrations/muse/npm-package-search)
- [AWS pricing service catalog](https://spiral.ai/integrations/muse/aws-pricing-service-catalog)

## Questions about AWS price file metadata in Muse

**Can Muse use AWS price file metadata?**

Yes. Add Spiral to Muse as an MCP server, and Muse can find and run AWS price file metadata like any built-in tool.

**How much does AWS price file metadata cost in Muse?**

$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 plan is separate.

**Do I need an Alexandria account to use AWS price file metadata in Muse?**

You need no Alexandria account. Muse uses one Spiral API key for every tool, and Spiral runs AWS price file metadata on its own Alexandria account.

**How long does it take to set up AWS price file metadata in Muse?**

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

**Does Muse wait while AWS price file metadata runs?**

AWS price file metadata runs in the background. Muse starts the run, checks on it and gives you the json when it's ready.

**How often does AWS update the catalog?**

Price list files can change at any time. AWS sends a notification when it updates a file, so a daily check can span multiple publications.

**How far back does the publication history go?**

The service version index lists the historical publications available for that service, with effective start and end dates. Check the returned versions to establish the periods represented for Amazon EC2, Amazon S3, or another service.

**Is the catalog limited to US East?**

AWS publishes regional indexes that link to pricing for the specified service, period, and region. Use the service's regional index to establish coverage rather than treating the pricing host's location as the coverage boundary.

**Does one product row describe every usage tier?**

AWS price dimensions include pricing tier limits and usage measurement. A tiered service therefore needs its applicable dimensions considered together when interpreting catalog rates.

**What identifies the currently active historical version?**

In an AWS service version index, a version without an effective end date is the currently active version. The effective period is separate from the index's publication timestamp.

