google-merchant-api

google-merchant-api is a skill for Claude Code from biggora/claude-plugins-registry. It costs 179 tokens per session (4,502 once invoked), scanned A, original, MIT.

A programming interface for managing Google Merchant Center, the service where online retailers submit product information for Google Shopping. It covers products, inventory, promotions, feeds, and reports through current or legacy Google APIs.

In plain words
What is it for?
Use it to authenticate with Google, upload and update products, manage inventory and promotions, work with product data sources, and retrieve merchant reports.
Why use it?
It lets software maintain shopping data automatically instead of requiring every product and stock update to be entered by hand. New integrations should use the current Merchant API.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the project-delivery-orchestrator plugin — 34 skills, 1 command, 5 agents shipped together

Good fit Use it to authenticate with Google, upload and update products, manage inventory…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/biggora/claude-plugins-registry/google-merchant-api
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add biggora/claude-plugins-registry --skill google-merchant-api
Clone the repo
git clone --depth 1 https://github.com/biggora/claude-plugins-registry

Made for: Claude Code.

Or install project-delivery-orchestrator, the plugin that ships this one along with the rest of its 34 skills, 1 command, 5 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for google-merchant-api

README.md
[![agentmods](https://agentmods.dev/badge/skills/biggora/claude-plugins-registry/google-merchant-api.svg)](https://agentmods.dev/skills/biggora/claude-plugins-registry/google-merchant-api)
Your own site
<a href="https://agentmods.dev/skills/biggora/claude-plugins-registry/google-merchant-api"><img src="https://agentmods.dev/badge/skills/biggora/claude-plugins-registry/google-merchant-api.svg" alt="Measured on agentmods" height="20"></a>
Per session 179 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,502 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00179 $0.04502
Opus 5 $0.00089 $0.02251
Sonnet 5 $0.00036 $0.00900
Haiku 4.5 $0.00018 $0.00450

Measured 6d ago against content hash a31896fce415, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

google-merchant-api scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

response = requests.post(
src/skills/google-merchant-api/SKILL.md · 571 lines

How it starts

The opening of the file, as written. The whole thing — 571 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Google Merchant API

Programmatically manage Google Merchant Center accounts, products, inventory, promotions, and more.

API Landscape

Google provides two APIs for Merchant Center. The Merchant API (v1) is the current standard. The Content API for Shopping (v2.1) is the legacy API, sunsetting August 18, 2026.

Aspect Merchant API (v1) Content API for Shopping (v2.1)
Base URL https://merchantapi.googleapis.com https://shoppingcontent.googleapis.com
Transport gRPC (default) + REST REST only
Status Active, GA Sunset August 18, 2026
Design Modular sub-APIs Monolithic
Batching Async / HTTP batching customBatch methods

Always prefer the Merchant API for new integrations. Only use Content API if maintaining legacy code or if a feature hasn't migrated yet.

Authentication

Both APIs use Google OAuth 2.0. Two approaches:

Service Account (server-to-server)

Best for automated backends. Create a service account in Google Cloud Console, download the JSON key, and grant it access in Merchant Center.

// Node.js with google-auth-library
const { GoogleAuth } = require('google-auth-library');

const auth = new GoogleAuth({
  keyFile: 'service-account-key.json',
  scopes: ['https://www.googleapis.com/auth/content'],
});
const client = await auth.getClient();
const token = await client.getAccessToken();
# Python with google-auth
from google.oauth2 import service_account

credentials = service_account.Credentials.from_service_account_file(
    'service-account-key.json',
    scopes=['https://www.googleapis.com/auth/content']
)

OAuth 2.0 Client (user-interactive)

Best for apps acting on behalf of merchants. Requires consent flow.

// Node.js OAuth2 flow
const { OAuth2Client } = require('google-auth-library');

const oauth2Client = new OAuth2Client(
  CLIENT_ID,
  CLIENT_SECRET,
  REDIRECT_URI
);

// Generate auth URL
const authUrl = oauth2Client.generateAuthUrl({
  access_type: 'offline',
  scope: ['https://www.googleapis.com/auth/content'],
});

// Exchange code for tokens
const { tokens } = await oauth2Client.getToken(code);
oauth2Client.setCredentials(tokens);

Read the full file on GitHub · 571 lines

Files

What ships with it

8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 6d ago First seen · 571 lines · 179 tokens per session scan A a31896fce415

Subscribe to this mod's changes

google-merchant-api is a skill published in the GitHub repository biggora/claude-plugins-registry (2 stars, last pushed 8d ago), licensed MIT. It adds 179 tokens to every session and 4,502 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

convex-billing

Add Stripe billing/payments to the Convex app via @convex-dev/stripe (checkout + webhook + gating).

openclaw/clawhub · 29 tokens

cloudbase-wechat-integration

A guide for connecting CloudBase applications to WeChat services, including payments, official accounts, and user identity.

TencentCloudBase/CloudBase-AI-Toolkit · 94 tokens

commerce-app-business-config

Manage custom business configuration in an Adobe Commerce app. Use when the user wants to add, modify, or remove merchant-configurable settings (config fields, admin config, store configuration) exposed through Commerce Admin. Creates typed config fields (text, password, email, url, tel, boolean, list) in…

adobe/skills · 80 tokens

baselinker-webhooks

Receive BaseLinker (Base.com) webhooks. Use when building a BaseLinker order or warehouse callback receiver, because BaseLinker is not a normal webhook source: deliveries arrive as HTTP HEAD requests with NO body, the entire payload is in the query string (observed params: orderid, state), there is NO signature…

hookdeck/webhook-skills · 131 tokens

tiktok-shop-webhooks

Receive and verify TikTok Shop webhooks. Use when setting up TikTok Shop webhook handlers, debugging Authorization-header signature verification, or handling events like ORDERSTATUSCHANGE, PACKAGEUPDATE, RECIPIENTADDRESSUPDATE, PRODUCTSTATUSCHANGE, or SELLERDEAUTHORIZATION.

hookdeck/webhook-skills · 59 tokens

gplay-purchase-verification

Server-side purchase verification for in-app products and subscriptions using Google Play Developer API. Use when implementing receipt validation in your backend.

hanamizuki/solopreneur · 32 tokens