Redhat Catalog Inventory
E CommerceInventorybasic38 EndpointsREST
For Agents
Programmatically perform a graphql query, return this API document in json format. Covers 38 operations with basic authentication.
Use for: I need to perform a graphql query, I want to return this API document in json format, Search for servicecredentialtypes, Find all show an existing servicecredentialtype
Not supported: Does not handle payments, communications, or crm - use for e-commerce only.
Catalog Inventory provides programmatic access to e commerce functionality. The API exposes 38 endpoints secured with basic authentication.
Install Jentic One Beta
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.
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%2Fredhat.com%2Fredhat" | sh2
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%2Fredhat.com%2Fredhat" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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
Monitor Catalog Inventory operational status and events
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
GET
/service_credentials/{id}
Show an existing ServiceCredential
GET
/service_instances
List ServiceInstances
GET
/service_instances/{id}
Show an existing ServiceInstance
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Catalog Inventory API by hand means handling its HTTP basic auth and building requests under the cloud.redhat.com/{basePath} host. Through Jentic you install once, import the Catalog Inventory API from the API Directory, store the credentials once, and your agent calls it.
Permission scoping
Catalog Inventory puts resource ids in the URL path (for example /service_instances/{id} and /service_credentials/{id}), so a rule can pin your agent to specific service instances or credentials. You choose the operations it may call, so its GraphQL endpoint is only included if you add it.
Credential isolation
Your Catalog Inventory credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list service instances' or 'look up a service credential', and Jentic returns the matching Catalog Inventory 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.
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 your Jentic One instance 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 through Jentic One, the self-hosted execution layer, 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.
Can I limit what my agent is allowed to do with the Catalog Inventory API?
Yes. Because you self-host Jentic One, your own rules decide which Catalog Inventory operations and credentials the agent may use. You pick the exact operations it can call, so read endpoints like GET /service_instances and GET /service_credentials can be allowed while the POST /graphql endpoint is included only if you add it. Since the API puts resource ids in the URL path, such as /service_instances/{id} and /service_credentials/{id}, you can also pin the agent to specific service instances or credentials.
GET STARTED