Spiral gives your agent every tool with one account. Browse the tools →

Muse · Developer

How to Use IBM Cloud pricing records in Muse

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 Muse

Copy an example into Muse, 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.

IBM Cloud pricing recordsMuse
Try asking
  • 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 Muse

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

Use the Muse connector

  1. Create an API key

    Create one under API keys in the Spiral console.

  2. Send Muse this message

    Muse reads Spiral's skill and asks for an API key.

    set up https://spiral.ai/SKILL.md
  3. Give Muse the key

    Paste the key when Muse asks for it, never in the chat itself.

Use the Spiral skill

  1. Send Muse 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.

    npx -y spiral-cli@latest init

Call the Spiral API

  1. Create an API key

    In the console, under API keys.

  2. 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: Muse 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.

AlexandriaDeveloper
IBM Cloud Global Catalog pricing (globalcatalog.cloud.ibm.com) · Records list
globalcatalog-cloud-ibm-com/cloud-pricing/records_list

Settings you can ask for

Ask Muse for any of these in your prompt.

SettingAllowed valuesDefaultDescription
Plans per page1 to 52

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 Muse?

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.

Questions about IBM Cloud pricing records in Muse

Can Muse use IBM Cloud pricing records?

Yes. Add Spiral to Muse as an MCP server, and Muse can find and run IBM Cloud pricing records like any built-in tool.

How much does IBM Cloud pricing records cost in Muse?

$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Muse plan is separate.

Do I need an Alexandria account to use IBM Cloud pricing records in Muse?

You need no Alexandria account. Muse uses one Spiral API key for every tool, and Spiral runs IBM Cloud pricing records on its own Alexandria account.

How long does it take to set up IBM Cloud pricing records in Muse?

About two minutes: create an API key, then send Muse this message, then give Muse the key.

Does Muse wait while IBM Cloud pricing records runs?

IBM Cloud pricing records runs in the background. Muse 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.

Get started

Start using IBM Cloud pricing records in Muse

One Spiral account for every tool your agent needs. No subscription; you pay per run.

Paste this into Muse:

Set up Muse

set up https://spiral.ai/SKILL.md
Are you an AI agent? See setup options