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 / Catalog Inventory
Catalog Inventory logo

Redhat Catalog Inventory

38
AI ReadinessNon-Ready (F)38/100
See full scorecard
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.

Jentic One on GithubView OpenAPI Document

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" | 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%2Fredhat.com%2Fredhat" | 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

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

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.

C

Catalog Inventory

- Non-Ready (F)
38/100
74
Foundational Compliance
60
Developer Experience & Jentic Compatibility
47
AI-Readiness & Agent Experience
94
Agent Usability
10
Security
59
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
74

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4
97%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

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

0%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

60

Developer Experience & Jentic Compatibility

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

Grade: B-Signals: 4
11%

Example Density

How richly the API is illustrated with examples.

90%

Example Validity

Percentage of examples that conform to their schemas.

41%

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.

47

AI-Readiness & Agent Experience

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

Grade: DSignals: 4
36%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

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

51%

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.

10

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1
10%

Authentication Strength

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

59

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: C+Signals: 1
59%

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 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

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 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

Start building with Catalog Inventory API

Explore with Jentic One
View OpenAPI Document