[Integrations](https://spiral.ai/integrations) › [Claude Code](https://spiral.ai/integrations/claude-code) › [AWS pricing publication history](https://spiral.ai/integrations/claude-code/aws-pricing-publication-history)

# How to Use AWS pricing publication history in Claude Code

Lists available AWS price list versions and their effective periods. Use it to identify historical publications and distinguish a new catalog publication from the period its rates cover.

|  |  |
| --- | --- |
| Model | AWS pricing publication history |
| Available through | Alexandria |
| Category | Finance |
| Price | $0.00873 per call. |
| Returns | json |
| Runs | In the background |
| Setup | About 2 minutes, no API key |

## Prompts to try with AWS pricing publication history in Claude Code

- Use AWS pricing publication history for AmazonS3 and add a report of available versions and effective periods to this project's catalog review output.
- Use AWS pricing publication history to look this up and give me the result as a table. Save the result in ./assets.
- Pull the latest numbers from AWS pricing publication history and tell me what changed since last week.
- Check AWS pricing publication history and summarize what you find in three bullet points.
- Pull the newest data from AWS pricing publication history and give me the result as a table.

## How to set up AWS pricing publication history in Claude Code

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

### Use Spiral's MCP server

1. **Add the hosted server**: This adds Spiral to the current project. Add `--scope user` to use it in every project.

```bash
claude mcp add --transport http spiral https://api.spiral.ai/mcp
```

2. **Sign in**: Start `claude`, type `/mcp`, choose spiral and Authenticate. Sign in to Spiral in the browser and click Authorize. No API key.

### Use the Spiral skill

1. **Send Claude 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 AWS pricing publication history**: 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/versions_list",
    "input": {
      "offer_code": "<offer_code>"
    }
  }'
```

Then paste one of the prompts above: Claude Code finds AWS pricing publication history on Spiral, shows the price and runs it.

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

## AWS pricing publication history tools and prices

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

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| limit | 1 to 2000 | 500 | Versions per page. |
| order | newest_first, oldest_first | newest_first | Sort order by version id. |
| 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}$. |
| continuation |  | — | Cursor from the previous page (`meta.page.next_cursor`). |
| 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 pricing publication history in Claude Code?

Build a traceable AWS catalog import for your project's estimator. A coding agent can work through service discovery, regional coverage, publication history, file metadata, and product rows to make the import reflect AWS's published catalog.

### 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.

### 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 Claude Code guides](https://spiral.ai/integrations/claude-code)

## AWS pricing publication history in other agents

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

## More Claude Code guides

- [AWS price file metadata](https://spiral.ai/integrations/claude-code/aws-price-file-metadata)
- [AWS pricing region coverage](https://spiral.ai/integrations/claude-code/aws-pricing-region-coverage)
- [npm publisher packages](https://spiral.ai/integrations/claude-code/npm-publisher-packages)
- [AWS pricing service catalog](https://spiral.ai/integrations/claude-code/aws-pricing-service-catalog)
- [npm package version details](https://spiral.ai/integrations/claude-code/npm-package-version-details)
- [AWS product pricing records](https://spiral.ai/integrations/claude-code/aws-product-pricing-records)

## Questions about AWS pricing publication history in Claude Code

**Can Claude Code use AWS pricing publication history?**

Yes. Add Spiral to Claude Code as an MCP server, and Claude Code can find and run AWS pricing publication history like any built-in tool.

**How much does AWS pricing publication history cost in Claude 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 Claude Code plan is separate.

**Do I need an Alexandria account to use AWS pricing publication history in Claude Code?**

No. Spiral runs AWS pricing publication history on its own Alexandria account. You sign in to Spiral once and never paste a key.

**How long does it take to set up AWS pricing publication history in Claude Code?**

About two minutes: add the hosted server, then sign in.

**Does Claude Code wait while AWS pricing publication history runs?**

AWS pricing publication history runs in the background. Claude Code 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.

