How to Use AWS price file metadata in Manus
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.
Prompts to try with AWS price file metadata in Manus
Copy an example into Manus, or ask in your own words.
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 Manus
Pick the way that suits you. Each takes about two minutes.
Use the Manus connector
- Add a custom MCP connector
In Manus open Settings › Connectors (or the connectors icon under the chat box), then Add connectors › Custom MCP and Add MCP by URL. Name it Spiral, set Transport to HTTP and paste this Server URL:
https://api.spiral.ai/mcp
- Sign in to Spiral and approve
Manus asks you to sign in the first time it uses Spiral. Spiral opens: sign in, pick the organization and click Authorize. No API key. Spiral gives the connection its own key; Manus never sees it, and you can remove it under Settings › Connected apps in the console.
Use the Spiral skill
- Send Manus 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 price file metadata
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/source_status", "input": { "region": "<region>", "version": "<version>", "offer_code": "<offer_code>" } }'
Then paste one of the prompts above: Manus finds AWS price file metadata on Spiral, shows the price and runs it.
AWS price file metadata providers and prices
Spiral runs AWS price file metadata through Alexandria. Open a card for today's price, with every fee included.
What can you do with AWS price file metadata in Manus?
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.
More on AWS price file metadata and Manus
Overview
AWS price file metadata in other agents
Questions about AWS price file metadata in Manus
Can Manus use AWS price file metadata?
Yes. Add Spiral to Manus as an MCP server, and Manus can find and run AWS price file metadata like any built-in tool.
How much does AWS price file metadata cost in Manus?
$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Manus plan is separate.
Do I need an Alexandria account to use AWS price file metadata in Manus?
No. Spiral runs AWS price file metadata 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 price file metadata in Manus?
About two minutes: add a custom MCP connector, then sign in to Spiral and approve.
Does Manus wait while AWS price file metadata runs?
AWS price file metadata runs in the background. Manus 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 price file metadata in Manus
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into Manus:
set up https://spiral.ai/SKILL.md


