How to Use AWS pricing publication history in Cursor
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.
Prompts to try with AWS pricing publication history in Cursor
Copy an example into Cursor, or ask in your own words.
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 Cursor
Pick the way that suits you. Each takes about two minutes.
Use Spiral's MCP server
- Add the hosted server
Use Add to Cursor on the console's Agents & MCP page, or add this to .cursor/mcp.json (one project) or ~/.cursor/mcp.json (every project):
{ "mcpServers": { "spiral": { "url": "https://api.spiral.ai/mcp" } } } - Sign in
Open Cursor Settings › MCP, click Connect next to spiral, sign in to Spiral and click Authorize. No API key. Spiral then shows as connected, with its tools listed.
Use the Spiral skill
- Send Cursor 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 AWS pricing publication history
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": "pricing-us-east-1-amazonaws-com/cloud-pricing/versions_list", "input": { "offer_code": "<offer_code>" } }'
Then paste one of the prompts above: Cursor finds AWS pricing publication history on Spiral, shows the price and runs it.
AWS pricing publication history providers and prices
Spiral runs AWS pricing publication history through Alexandria. Open a card for today's price, with every fee included.
Settings you can ask for
Ask Cursor for any of these in your prompt.
| Setting | Allowed values | Default | Description |
|---|---|---|---|
| Limit | 1 to 2000 | 500 | Versions per page. |
| Order | newest_first or oldest_first | newest_first | Sort order by version id. |
Every API field of AWS Price List Bulk API · Versions list is on its tool page: open its card above.
What can you do with AWS pricing publication history in Cursor?
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.
More on AWS pricing publication history and Cursor
Overview
AWS pricing publication history in other agents
Questions about AWS pricing publication history in Cursor
Can Cursor use AWS pricing publication history?
Yes. Add Spiral to Cursor as an MCP server, and Cursor can find and run AWS pricing publication history like any built-in tool.
How much does AWS pricing publication history cost in Cursor?
$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Cursor plan is separate.
Do I need an Alexandria account to use AWS pricing publication history in Cursor?
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 Cursor?
About two minutes: add the hosted server, then sign in.
Does Cursor wait while AWS pricing publication history runs?
AWS pricing publication history runs in the background. Cursor 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.
Start using AWS pricing publication history in Cursor
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into Cursor:
set up https://spiral.ai/SKILL.md


