[Integrations](https://spiral.ai/integrations) › [Grok](https://spiral.ai/integrations/grok) › [Google Cloud SKU group directory](https://spiral.ai/integrations/grok/google-cloud-sku-group-directory)

# How to Use Google Cloud SKU group directory in Grok

Lists published Google Cloud SKU groups used in contracts and cost management. Use it to find the right category before retrieving the SKUs it contains.

|  |  |
| --- | --- |
| Model | Google Cloud SKU group directory |
| Available through | Alexandria |
| Category | E-commerce |
| Price | $0.00873 per call. |
| Returns | json |
| Runs | In the background |
| Setup | About 2 minutes, no API key |

## Prompts to try with Google Cloud SKU group directory in Grok

- Use Google Cloud SKU group directory to find the published BigQuery categories and explain which names relate to storage or analysis.
- Use Google Cloud SKU group directory to look this up and give me the result as a table.
- Pull the latest numbers from Google Cloud SKU group directory and tell me what changed since last week.
- Check Google Cloud SKU group directory and summarize what you find in three bullet points.
- Pull the newest data from Google Cloud SKU group directory and give me the result as a table.

## How to set up Google Cloud SKU group directory in Grok

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

### Use the Grok connector

1. **Add a custom connector**: In Grok open Settings › Connect Apps, then Add a custom connector. Name it Spiral, paste this URL, leave Headers empty and click Add MCP.

```text
https://api.spiral.ai/mcp
```

2. **Sign in to Spiral and approve**: Grok opens Spiral: sign in, pick the organization and click Authorize. Spiral gives the connection its own API key; Grok never sees it, and you can remove the connection under Settings › Connected apps.

3. **Check that it is connected**: Connect Apps › Custom shows Spiral as Connected. It works in every Grok chat and Grok bot.

### Use the Spiral skill

1. **Send Grok 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.

```bash
npx -y spiral-cli@latest init
```

### Call the Spiral API

1. **Create an API key**: In the console, under API keys.

2. **Run Google Cloud SKU group directory**: One request; the result comes back by polling or a webhook.

```bash
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": "cloudbilling-googleapis-com/cloud-pricing/sku_groups",
    "input": {
      "limit": 100
    }
  }'
```

Then paste one of the prompts above: Grok finds Google Cloud SKU group directory on Spiral, shows the price and runs it.

Setup guide in the docs: https://spiral.ai/docs/quickstarts/grok

## Google Cloud SKU group directory tools and prices

- [Google Cloud SKU list prices · Sku groups](https://spiral.ai/tools/alexandria/cloudbilling-googleapis-com/cloud-pricing/sku_groups) (Alexandria): $0.00873 per call.

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| limit | 1 to 1000 | 100 | limit |
| offset | 0 to … | 0 | offset |

## What can you do with Google Cloud SKU group directory in Grok?

Produce a Google Cloud resource comparison with the relevant SKU descriptions, regional boundaries, and public pricing context. A chat app can explain the returned catalog evidence and identify which exact SKUs need closer review.

### Maintain an E2 cost reference

Check catalog status, find the On-Demand E2 VMs category in the directory, and collect its SKU IDs. Search for relevant descriptions, reconcile them against the Compute Engine catalog, and retrieve exact SKU prices for the reference.

### Review regional storage options

Check source status and discover storage categories in the directory. Collect their SKUs, search for the storage descriptions under review, compare the service catalog's regional coverage, and look up exact prices for the shortlist.

### Build a BigQuery SKU reference

Check catalog status, locate BigQuery categories, and collect the SKUs they contain. Use description search and the service catalog to organize the results, then retrieve exact public prices for selected analysis and storage SKUs.

### Investigate catalog changes

Compare source status and saved directory results, then inspect affected categories. Reconcile their SKU IDs with service listings and description searches, and retrieve exact prices to separate category changes from pricing changes.

### Map published contract categories

Find a named Google Cloud category in the directory and collect its SKU IDs. Use the resulting list to review category scope alongside a contract, keeping negotiated rates separate.

## Overview

- [Alexandria](https://spiral.ai/providers/alexandria)
- [All Grok guides](https://spiral.ai/integrations/grok)

## Google Cloud SKU group directory in other agents

- [Amp](https://spiral.ai/integrations/amp/google-cloud-sku-group-directory)
- [ChatGPT](https://spiral.ai/integrations/chatgpt/google-cloud-sku-group-directory)
- [Claude](https://spiral.ai/integrations/claude-desktop/google-cloud-sku-group-directory)
- [Claude Code](https://spiral.ai/integrations/claude-code/google-cloud-sku-group-directory)
- [Cline](https://spiral.ai/integrations/cline/google-cloud-sku-group-directory)
- [Codex](https://spiral.ai/integrations/codex/google-cloud-sku-group-directory)
- [Cursor](https://spiral.ai/integrations/cursor/google-cloud-sku-group-directory)
- [Devin](https://spiral.ai/integrations/devin/google-cloud-sku-group-directory)
- [dots](https://spiral.ai/integrations/dots/google-cloud-sku-group-directory)
- [Factory Droid](https://spiral.ai/integrations/factory-droid/google-cloud-sku-group-directory)
- [Gemini](https://spiral.ai/integrations/gemini/google-cloud-sku-group-directory)
- [Gemini CLI](https://spiral.ai/integrations/gemini-cli/google-cloud-sku-group-directory)
- [Google Antigravity](https://spiral.ai/integrations/antigravity/google-cloud-sku-group-directory)
- [goose](https://spiral.ai/integrations/goose/google-cloud-sku-group-directory)
- [Grok Build](https://spiral.ai/integrations/grok-build/google-cloud-sku-group-directory)
- [Hermes](https://spiral.ai/integrations/hermes/google-cloud-sku-group-directory)
- [Instinct](https://spiral.ai/integrations/instinct/google-cloud-sku-group-directory)
- [Manus](https://spiral.ai/integrations/manus/google-cloud-sku-group-directory)
- [Muse](https://spiral.ai/integrations/muse/google-cloud-sku-group-directory)
- [Muse Code](https://spiral.ai/integrations/muse-code/google-cloud-sku-group-directory)
- [n8n](https://spiral.ai/integrations/n8n/google-cloud-sku-group-directory)
- [Notion](https://spiral.ai/integrations/notion/google-cloud-sku-group-directory)
- [OpenClaw](https://spiral.ai/integrations/openclaw/google-cloud-sku-group-directory)
- [opencode](https://spiral.ai/integrations/opencode/google-cloud-sku-group-directory)
- [Perplexity](https://spiral.ai/integrations/perplexity/google-cloud-sku-group-directory)
- [Raycast](https://spiral.ai/integrations/raycast/google-cloud-sku-group-directory)
- [VS Code](https://spiral.ai/integrations/vscode/google-cloud-sku-group-directory)
- [Windsurf](https://spiral.ai/integrations/windsurf/google-cloud-sku-group-directory)
- [Zapier](https://spiral.ai/integrations/zapier/google-cloud-sku-group-directory)

## More Grok guides

- [Google Cloud SKU group contents](https://spiral.ai/integrations/grok/google-cloud-sku-group-contents)
- [Google Cloud SKU price](https://spiral.ai/integrations/grok/google-cloud-sku-price)
- [Google Cloud SKU catalog status](https://spiral.ai/integrations/grok/google-cloud-sku-catalog-status)
- [Google Cloud SKU search](https://spiral.ai/integrations/grok/google-cloud-sku-search)
- [Google Books ISBN lookup](https://spiral.ai/integrations/grok/google-books-isbn-lookup)
- [Google Cloud service SKU catalog](https://spiral.ai/integrations/grok/google-cloud-service-sku-catalog)

## Questions about Google Cloud SKU group directory in Grok

**Can Grok use Google Cloud SKU group directory?**

Yes. Add Spiral to Grok as an MCP server, and Grok can find and run Google Cloud SKU group directory like any built-in tool.

**How much does Google Cloud SKU group directory cost in Grok?**

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

**Do I need an Alexandria account to use Google Cloud SKU group directory in Grok?**

No. Spiral runs Google Cloud SKU group directory on its own Alexandria account. You sign in to Spiral once and never paste a key.

**How long does it take to set up Google Cloud SKU group directory in Grok?**

About two minutes: add a custom connector, then sign in to Spiral and approve, then check that it is connected.

**Does Grok wait while Google Cloud SKU group directory runs?**

Google Cloud SKU group directory runs in the background. Grok starts the run, checks on it and gives you the json when it's ready.

**Does this catalog include negotiated Google Cloud prices?**

The catalog contains public SKU pricing. Google directs customers with custom contract pricing to its separate Pricing API for applicable contract prices.

**Does a SKU apply to every Google Cloud region?**

Google distinguishes global, regional, and multiregional SKUs. Global SKUs have an empty geographic taxonomy region list because they apply across all Google Cloud regions.

**Can I estimate usage by multiplying everything by one rate?**

Google's pricing formulas can contain multiple usage tiers. Total cost applies each tier to its corresponding usage, so one rate can give the wrong estimate.

**How do I know a service catalog collection is complete?**

Google's SKU listings are paginated. At the publisher level, an empty continuation token marks the end of the results; the first response alone does not establish completeness.

**What time boundary applies to Google's historical catalog queries?**

The underlying Catalog API requires each historical pricing time range to fit within one calendar month in the America/Los_Angeles time zone. That publisher capability does not establish historical access through these endpoints.

