Catalog Inventory

Name: Catalog Inventory API
Brand: Catalog Inventory
Availability: InStock

★ Only Publicly Available OpenAPI DocumentE CommerceInventorybasic38 EndpointsREST

For Agents

Programmatically perform a graphql query, return this api document in json format. Covers 38 operations with basic authentication.

Connect the Catalog Inventory to your agent

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

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Inventory API.

Perform a GraphQL Query

Return this API document in JSON format

List ServiceCredentialTypes

Show an existing ServiceCredentialType

GET STARTED

Start building with Catalog Inventory API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Catalog Inventory API for, with concrete tasks.

★ E-Commerce Operations

Use the Catalog Inventory to perform e commerce operations programmatically. The API provides 38 endpoints covering core functionality including perform a graphql query, return this api document in json format, list servicecredentialtypes.

Call POST /graphql to perform a graphql query

Automated Graphql Management

Automate graphql operations by combining multiple Catalog Inventory endpoints. Agents can return this api document in json format and then list servicecredentialtypes in a single workflow.

Call GET /openapi.json to return this api document in json format, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Catalog Inventory endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle basic tokens manually.

Search Jentic for 'perform a graphql query', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

38 endpoints — catalog inventory provides programmatic access to e commerce functionality.

METHOD

PATH

DESCRIPTION

POST

/graphql

Perform a GraphQL Query

GET

/openapi.json

Return this API document in JSON format

GET

/service_credential_types

List ServiceCredentialTypes

GET

/service_credential_types/{id}

Show an existing ServiceCredentialType

GET

/service_credentials

List ServiceCredentials

GET

/service_credentials/{id}

Show an existing ServiceCredential

GET

/service_instances

List ServiceInstances

GET

/service_instances/{id}

Show an existing ServiceInstance

POST

/graphql

Perform a GraphQL Query

GET

/openapi.json

Return this API document in JSON format

GET

/service_credential_types

List ServiceCredentialTypes

GET

/service_credential_types/{id}

Show an existing ServiceCredentialType

GET

/service_credentials

List ServiceCredentials

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Catalog Inventory basic credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'perform a graphql query') and Jentic returns the matching Catalog Inventory operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Catalog Inventory integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Shopify

Alternative e commerce API

Choose Shopify when you need a different approach to e commerce operations

Alternative

Stripe

Alternative e commerce API

Choose Stripe when you need a different approach to e commerce operations

FAQs

Specific to using Catalog Inventory API through Jentic.

What authentication does the Catalog Inventory use?

The Catalog Inventory uses HTTP Basic authentication with username and password. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I perform a graphql query with the Catalog Inventory?

Yes. Use the POST /graphql endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Catalog Inventory?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I perform a graphql query through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'perform a graphql query'. Jentic returns the matching Catalog Inventory operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the Catalog Inventory have?

The Catalog Inventory exposes 38 endpoints covering graphql, openapi.json, service_credential_types operations.