How to Use IBM Cloud pricing records in Manus
Returns published pricing records across plans, with deployment, metric, country, and quantity-tier detail. Use it to collect a service's rate table or build a broader catalog reference.
Prompts to try with IBM Cloud pricing records in Manus
Copy an example into Manus, or ask in your own words.
Use IBM Cloud pricing records to collect Virtual Server for VPC plans available in Dallas and Frankfurt, then compare their published charge units and quantity tiers using United States amounts.
Use IBM Cloud pricing records to look this up and give me the result as a table.
Pull the latest numbers from IBM Cloud pricing records and tell me what changed since last week.
Check IBM Cloud pricing records and summarize what you find in three bullet points.
Pull the newest data from IBM Cloud pricing records and give me the result as a table.
How to set up IBM Cloud pricing records 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 IBM Cloud 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": "globalcatalog-cloud-ibm-com/cloud-pricing/records_list", "input": { "kinds": [ "<kinds>" ] } }'
Then paste one of the prompts above: Manus finds IBM Cloud pricing records on Spiral, shows the price and runs it.
IBM Cloud pricing records providers and prices
Spiral runs IBM Cloud pricing records through Alexandria. Open a card for today's price, with every fee included.
$0.00873 per call.
Settings you can ask for
Ask Manus for any of these in your prompt.
| Setting | Allowed values | Default | Description |
|---|---|---|---|
| Plans per page | 1 to 5 | 2 | Plans priced per page (1..5, default 2). A VPC plan with 13 regions yields ~9,600 records unfiltered. |
Every API field of IBM Cloud Global Catalog pricing (globalcatalog.cloud.ibm.com) · Records list is on its tool page: open its card above.
What can you do with IBM Cloud pricing records in Manus?
Turn IBM Cloud catalog data into a readable product shortlist or deployment comparison. Explain the returned metrics, quantity tiers, and validity dates while keeping global deployment scope separate from regional pricing.
Compare deployment regions
Find an IBM Cloud service, collect its plans, and inspect selected deployments using matching charge units and currencies. Check the catalog revision around the collection before preparing a regional comparison.
Maintain an internal rate reference
Resolve IBM Cloud product names, collect their published pricing records, and inspect individual plans when a charge needs explanation. Include catalog revision checks in each refresh.
Review catalog changes
Compare successive collections to identify changed rates, quantity tiers, or plan coverage. Use catalog search to resolve affected products, inspect individual plans, and check source revisions during collection.
Refresh a workload estimate
Match the workload's IBM Cloud services to catalog entries, collect relevant plans, and verify selected rates and validity dates. Check the catalog revision before updating the estimate's reference data.
Audit charge units
Inspect published metrics and quantity tiers for a service or selected plan. Identify where an estimator must distinguish instance-hours, processor-core-hours, storage units, and request quantities.
Investigate regional pricing gaps
Find the intended IBM Cloud product, examine its pricing records, and inspect a selected deployment. Separate missing published pricing from an assumption that every listed deployment has a rate.
More on IBM Cloud pricing records and Manus
Overview
IBM Cloud pricing records in other agents
Questions about IBM Cloud pricing records in Manus
Can Manus use IBM Cloud pricing records?
Yes. Add Spiral to Manus as an MCP server, and Manus can find and run IBM Cloud pricing records like any built-in tool.
How much does IBM Cloud pricing records 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 IBM Cloud pricing records in Manus?
No. Spiral runs IBM Cloud 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 IBM Cloud pricing records in Manus?
About two minutes: add a custom MCP connector, then sign in to Spiral and approve.
Does Manus wait while IBM Cloud pricing records runs?
IBM Cloud pricing records runs in the background. Manus starts the run, checks on it and gives you the json when it's ready.
What does the IBM Cloud catalog data cover?
It covers public catalog entries, plans, and published list pricing by deployment region, metric, country, and quantity tier. That scope is a public product reference, not an account's usage statement.
Does a global deployment have the same rates everywhere?
A global deployment can have region-specific pricing. IBM documents Cloud Object Storage Standard as one example, so global deployment scope alone does not establish a worldwide rate.
Do effective dates tell me when the data was refreshed?
The effective start and end dates define when a pricing plan applies. They describe the rate's validity period, not a catalog refresh schedule.
Can I request only the records that changed?
This collection has no records change feed because the publisher provides no deltas. Change reviews require comparing collected snapshots.
Start using IBM Cloud pricing records 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


