How to Use AWS product pricing records in Gemini
Returns product and pricing rows from AWS price list files, including product attributes and purchase terms. Use it to analyze catalog rates and usage tiers after identifying the service you need.
Prompts to try with AWS product pricing records in Gemini
Copy an example into Gemini, or ask in your own words.
Use AWS product pricing records for Amazon S3. Summarize the returned storage and request terms, including usage measurements and tier boundaries.
Use AWS product pricing records to look this up and give me the result as a table.
Pull the latest numbers from AWS product pricing records and tell me what changed since last week.
Check AWS product pricing records and summarize what you find in three bullet points.
Pull the newest data from AWS product pricing records and give me the result as a table.
How to set up AWS product pricing records in Gemini
Pick the way that suits you. Each takes about two minutes.
Use the Gemini connector
- Open Connected Apps
On your computer, go to gemini.google.com. At the bottom, click Settings › Connected Apps. If you don't see Connected Apps, click Personal Intelligence first, then Connected Apps.
- Add Spiral as a custom app
Under Custom apps, click Add a custom app and paste this MCP server URL:
https://api.spiral.ai/mcp
- Sign in to Spiral and approve
Follow the on-screen instructions. Spiral opens: sign in, pick the organization and click Authorize. No API key.
Use the Spiral skill
- Send Gemini 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 product pricing records
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/records_list", "input": { "region": "<region>", "version": "<version>", "offer_code": "<offer_code>" } }'
Then paste one of the prompts above: Gemini finds AWS product pricing records on Spiral, shows the price and runs it.
AWS product pricing records providers and prices
Spiral runs AWS product pricing records through Alexandria. Open a card for today's price, with every fee included.
Settings you can ask for
Ask Gemini for any of these in your prompt.
| Setting | Allowed values | Default | Description |
|---|---|---|---|
| Window bytes | 4096 to 8388608 | 4194304 | Bytes requested per page with |
Every API field of AWS Price List Bulk API · Records list is on its tool page: open its card above.
What can you do with AWS product pricing records in Gemini?
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.
More on AWS product pricing records and Gemini
Overview
AWS product pricing records in other agents
Questions about AWS product pricing records in Gemini
Can Gemini use AWS product pricing records?
Yes. Add Spiral to Gemini as an MCP server, and Gemini can find and run AWS product pricing records like any built-in tool.
How much does AWS product pricing records cost in Gemini?
$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Gemini plan is separate.
Do I need an Alexandria account to use AWS product pricing records in Gemini?
No. Spiral runs AWS product pricing records 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 product pricing records in Gemini?
About two minutes: open Connected Apps, then add Spiral as a custom app, then sign in to Spiral and approve.
Does Gemini wait while AWS product pricing records runs?
AWS product pricing records runs in the background. Gemini 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 product pricing records in Gemini
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into Gemini:
set up https://spiral.ai/SKILL.md


