Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / E Commerce / Google / Manufacturer Center API
Manufacturer Center API logo

Google Manufacturer Center API

Browse all Google APIs
41
AI ReadinessFoundational (D-)41/100
See full scorecard
Official vendor OpenAPI document · agent-readyE CommerceStorefrontoauth28 EndpointsREST

For Agents

Submit and manage authoritative manufacturer-supplied product attributes and product certifications for a brand's catalog in Google Manufacturer Center.

Use for: List all products registered under our Manufacturer Center account, Delete a discontinued product from our manufacturer account, Retrieve all certifications currently attached to a manufacturer product, Remove an expired product certification from a product

Not supported: Does not handle retailer offers, ads, or pricing - use for manufacturer-supplied product data and product certifications only.

The Manufacturer Center API lets brand manufacturers submit and maintain authoritative product data and product certifications used across Google's shopping surfaces. Brands push canonical attributes such as GTIN, MPN, brand name, image, product detail, and feature descriptions, plus regulatory or industry certifications, so retailers and Google's shopping experiences show accurate manufacturer-supplied content. The API is scoped per Manufacturer Center account and is distinct from Merchant Center, which is used by retailers to upload their own offers.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Manufacturer Center API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Manufacturer Center API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

1

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Fgoogle-manufacturer-center" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Fgoogle-manufacturer-center" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Manufacturer Center API.

Publish authoritative manufacturer-supplied product attributes such as GTIN, MPN, brand, and feature descriptions

Delete a product from the manufacturer account when it is discontinued

List the products currently registered under a manufacturer account

Manage product certifications including regulatory and industry certifications attached to a product

Retrieve and remove product certifications when they expire or are replaced

Query the manufacturer's catalog state to detect missing or rejected attributes

Use Cases

Patterns agents use Manufacturer Center API for, with concrete tasks.

★ Authoritative product data publication

Brand manufacturers use the API to publish canonical product information such as GTIN, MPN, feature bullets, and product detail attributes so that Google's shopping surfaces and downstream retailers display the manufacturer-approved content. This avoids retailer-by-retailer attribute drift and keeps the brand's voice consistent.

List all products under accounts/12345 and report any whose required brand or gtin attributes are missing

Product certification management

Manage product certifications attached to products in the manufacturer account, including regulatory marks, energy efficiency labels, and industry credentials. The certifications resource lets brands keep documentation current as products are recertified or removed from market.

List productCertifications for product accounts/12345/products/SKU-AB-100 and delete any whose validity period has ended

Catalog hygiene and end-of-life

Run periodic catalog hygiene against Manufacturer Center to delete products that are end-of-life and confirm replacements are in place. Combined with the listing endpoints, this keeps the brand's authoritative catalog current and avoids ghost SKUs surfacing on shopping pages.

For every product in accounts/12345 with a discontinued flag in our internal system, call delete on the matching manufacturer product

Agent integration via Jentic

AI agents responsible for marketplace data quality can use Manufacturer Center through Jentic to audit catalog completeness and remove dead SKUs without holding the brand's OAuth refresh token in their prompt. Jentic also surfaces the certification operations so agents can keep regulatory metadata up to date.

Walk every product in accounts/12345, delete any flagged discontinued in our PIM, and report the deleted SKU list

Key Endpoints

8 endpoints — the manufacturer center api lets brand manufacturers submit and maintain authoritative product data and product certifications used across google's shopping surfaces.

METHOD

PATH

DESCRIPTION

GET

/v1/{+parent}/products

List products in a manufacturer account

DELETE

/v1/{+parent}/products/{+name}

Delete a product from a manufacturer account

GET

/v1/{+parent}/productCertifications

List product certifications

DELETE

/v1/{+name}

Delete a specific resource by name

GET

/v1/{+parent}/products

List products in a manufacturer account

DELETE

/v1/{+parent}/products/{+name}

Delete a product from a manufacturer account

GET

/v1/{+parent}/productCertifications

List product certifications

DELETE

/v1/{+name}

Delete a specific resource by name

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

M

Manufacturer Center API

- Foundational (D-)
41/100
59
Foundational Compliance
56
Developer Experience & Jentic Compatibility
19
AI-Readiness & Agent Experience
94
Agent Usability
63
Security
61
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
59

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: C+Signals: 4
75%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

0%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

60%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

56

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: CSignals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

25%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

19

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4
76%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

0%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

0%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

63

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1
62%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

61

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B-Signals: 1
61%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Manufacturer Center API by hand means setting up Google OAuth 2.0 with the manufacturercenter scope, minting bearer tokens, and paging product listings yourself against the manufacturers.googleapis.com host. Through Jentic you install once, import the Manufacturer Center API from the API Directory, store the OAuth credential once, and your agent calls it.

Permission scoping

The Manufacturer Center API puts the account and product name in the URL path (/v1/{+parent}/products and /v1/{+name}), so a rule can pin your agent to one Manufacturer Center account: it can list products and certifications there and nothing else. You choose the operations it may call, so destructive ones like deleting a product or a certification are not included unless you add them.

Credential isolation

Your Google OAuth credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list Manufacturer Center products' or 'remove a product certification', and Jentic returns the matching Manufacturer Center operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Content API for Shopping

→

Retailer-side offer feed and account API for Merchant Center accounts that resell manufacturer products

Use Content API for Shopping when the agent acts on behalf of a retailer; use Manufacturer Center when it acts for the brand owner

Complementary

Display & Video 360 API

→

Programmatic ad platform that often references manufacturer-supplied product data for product feeds

Choose Display & Video 360 when the agent buys media against the catalog; use Manufacturer Center to maintain the catalog itself

Complementary

DoubleClick Bid Manager API

→

Reports for programmatic campaigns referencing the same product taxonomy

Use DoubleClick Bid Manager when the agent needs campaign reports; use Manufacturer Center for the underlying product attributes

FAQs

Specific to using Manufacturer Center API through Jentic.

What authentication does the Manufacturer Center API use?

The API uses Google OAuth 2.0 with the https://www.googleapis.com/auth/manufacturercenter scope. Through Jentic, the OAuth credentials are held in the encrypted vault and the agent only sees a short-lived scoped bearer token for each call.

Can I list every product under our manufacturer account through this API?

Yes, the products listing endpoint under accounts/{account_id} returns paginated product entries. Use the page token in the response to walk the full catalog.

What are the rate limits for the Manufacturer Center API?

Quotas are managed per Google Cloud project and per Manufacturer Center account in the Cloud Console quotas page. Default per-day and per-minute request quotas apply, and bulk catalog updates should use exponential backoff on 429 responses.

How do I delete an expired product certification through Jentic?

Search Jentic for delete product certification, load the operation that maps to /v1/{+name}, and execute with the certification resource path. Jentic injects the OAuth bearer so the agent only constructs the request body.

Is the Manufacturer Center API free?

Manufacturer Center itself is free for eligible brand manufacturers and the API does not have separate per-call billing; usage is bounded by quota rather than price.

Is this the same API as Merchant Center?

No. Manufacturer Center is for brand manufacturers publishing authoritative data about their own products. Merchant Center is for retailers uploading the offers they sell, which uses the separate Content API for Shopping or the Merchant API.

Can I limit what my agent is allowed to do with the Manufacturer Center API?

Yes. Because your Jentic One instance is self-hosted, your own rules decide which Manufacturer Center operations and credentials the agent can use. Since the account and product are named in the URL path (/v1/{+parent}/products and /v1/{+name}), a rule can pin the agent to a single Manufacturer Center account so it only lists products and certifications there and nothing else. You pick the operations it may call, so destructive ones like deleting a product or a certification stay off the list unless you explicitly add them.

GET STARTED

Start building with Manufacturer Center API

Explore with Jentic One
View OpenAPI Document