Install Jentic One Beta

Connect the Catalog - Products to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Catalog - Products, 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.

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%2Fbigcommerce.com%2Fbigcommerce-catalog-api" | sh

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%2Fbigcommerce.com%2Fbigcommerce-catalog-api" | 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 Catalog - Products API.

Add products to the catalog and update them individually or in batches

Attach images and videos to a product

Set bulk pricing rules and complex rules that determine a product's price

Store custom fields and metafields of structured data on products

Assign products to categories and sales channels

GET STARTED

Start building with Catalog - Products API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Catalog - Products API for, with concrete tasks.

★ Agent-maintained product catalog

An AI agent keeps a BigCommerce catalog current from an external feed: it creates new products, updates prices and descriptions, and uploads images as the source data changes. Because products support batch updates and structured metafields, the agent can push many changes in one pass and attach the extra attributes a storefront needs without a manual spreadsheet import.

Create a product with a title, price, and description, upload its primary image, and assign it to a category

Tiered and rule-based pricing

Wholesale and promotional stores need prices that change with quantity or shopper context. The Catalog API sets bulk pricing rules and complex rules on a product, so an agent can apply quantity-break pricing or conditional rules across a product range in response to a promotion, rather than editing each listing by hand.

Create a bulk pricing rule on a product that discounts orders of 10 or more units

Structured product data for search and channels

Selling across marketplaces needs richer product data than the core fields. Metafields and custom fields store structured attributes on each product, and category and channel assignments control where a product appears, so an agent can enrich listings and publish them to the right sales channels from one place.

Attach a metafield with a material attribute to a product and assign the product to a second sales channel

Key Endpoints

53 endpoints — the bigcommerce catalog api manages the product side of a store: it adds and updates products individually or in batches, attaches images and videos, and holds the bulk pricing rules and complex rules that drive what a shopper pays.

METHOD

PATH

DESCRIPTION

GET

/catalog/products

List all products

POST

/catalog/products

Create a product

PUT

/catalog/products

Update products in batch

GET

/catalog/products/{product_id}

Get a single product

POST

/catalog/products/{product_id}/images

Add a product image

POST

/catalog/products/{product_id}/bulk-pricing-rules

Create a bulk pricing rule

POST

/catalog/products/{product_id}/metafields

Create a product metafield

GET

/catalog/products/{product_id}/reviews

Get a product's reviews

GET

/catalog/products

List all products

POST

/catalog/products

Create a product

PUT

/catalog/products

Update products in batch

GET

/catalog/products/{product_id}

Get a single product

POST

/catalog/products/{product_id}/images

Add a product image

POST

/catalog/products/{product_id}/bulk-pricing-rules

Create a bulk pricing rule

POST

/catalog/products/{product_id}/metafields

Create a product metafield

GET

/catalog/products/{product_id}/reviews

Get a product's reviews

Why Jentic?

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

Setup

Wiring the BigCommerce Catalog API by hand means creating a store API account, scoping its X-Auth-Token, and substituting your store hash into every request path. Through Jentic you install once, import it from the API Directory, store the token once, and your agent calls it.

Permission scoping

The product id travels in the URL path (/catalog/products/{product_id}), so a rule can pin your agent to one product, or allow a chosen set of operations. You choose the operations it may call, so product deletion is not included unless you add it.

Credential isolation

Your BigCommerce store token 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 'create a product' or 'set bulk pricing', and Jentic returns the matching Catalog operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using Catalog - Products API through Jentic.

What authentication does the BigCommerce Catalog API use?

The BigCommerce Catalog API authenticates with a store API account token sent in the X-Auth-Token header, as declared in its OpenAPI spec, and each token carries the OAuth scopes it was granted. Through Jentic the token is stored encrypted by your own Jentic One instance and injected when a call runs, so it never reaches the agent's prompt or logs.

Can I set quantity-based pricing on a product with this API?

Yes. The Catalog API creates bulk pricing rules on a product for quantity breaks and supports complex rules for conditional pricing, so an agent can apply wholesale or promotional pricing across the catalog.

What are the rate limits for the BigCommerce Catalog API?

The OpenAPI spec does not state rate limits. BigCommerce enforces per-plan API quotas documented on its developer portal at developer.bigcommerce.com, so check there before running large batch product updates.

Is there a BigCommerce Catalog MCP server?

You do not need an MCP server to give your agent the BigCommerce Catalog API. Jentic connects it directly from the API Directory: import it, store your store token once, and your agent creates and updates products on demand.

Can I limit what my agent is allowed to do with the BigCommerce Catalog API?

Yes. The product id travels in the URL path, so a rule can pin the agent to one product, or you can allow only the product read operations so the agent can list and inspect products but cannot delete them or rewrite pricing, with every call logged.

How do I add a product with this API through Jentic?

Search Jentic for an intent like 'create a BigCommerce product' and it returns the matching operation with its input schema, then your agent calls it with the store token Jentic injects at runtime. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Bigcommerce Catalog - Products

Browse all Bigcommerce APIs

AI ReadinessAI-Aware (B)67/100

See full scorecard

Official vendor OpenAPI document · agent-readyE CommerceStorefrontapiKey53 EndpointsREST

For Agents

Add and update BigCommerce products in batch, attach images and videos, set bulk and complex pricing rules, manage metafields, and assign products to categories and channels.

Use for: Add a new product to the store catalog, Update the price and description of an existing product, Upload an image for a product listing, Set a bulk pricing rule for wholesale quantities

Not supported: Does not handle orders, checkout, customers, or payment capture. Use for managing the BigCommerce product catalog and its pricing and media only.

The BigCommerce Catalog API manages the product side of a store: it adds and updates products individually or in batches, attaches images and videos, and holds the bulk pricing rules and complex rules that drive what a shopper pays. Products carry custom fields and metafields for structured extra data, can be assigned to categories and sales channels, and expose their customer reviews. It is the product source of truth that a storefront and checkout read from.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: C+Signals: 4

94%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

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

42%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

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

Grade: BSignals: 4

20%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

42%

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.

AI-Readiness & Agent Experience

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

Grade: A-Signals: 4

72%

Description Coverage

Coverage of descriptions across API elements.

42%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

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

73%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

93%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

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

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B-Signals: 1

62%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Catalog - Products to your agent

Capabilities

Start building with Catalog - Products API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Bigcommerce Catalog - Products

Jentic AI Readiness Score

Catalog - Products

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness