Can I look up an Intel codename through this API?

Yes. GET /api/products/get-codename takes a product reference and returns the corresponding internal codename, which is useful when normalising references between marketing and engineering systems.

Can I retrieve ordering information for a specific Intel SKU?

Yes. GET /api/products/get-ordering-info exposes ordering metadata for a product, suitable for syncing into storefront and procurement systems.

What are the rate limits for the Intel Product Catalogue API?

The OpenAPI specification does not encode explicit rate limits. The API is partner-only and issued credentials carry implicit fair-use expectations, so cache responses where possible and avoid tight polling loops on /api/products/get-products.

How do I look up an Intel product through Jentic?

Run pip install jentic, then have the agent issue the search-load-execute flow with the query 'look up an Intel product codename'. Jentic returns the operation backed by /api/products/get-codename; the agent supplies the product identifier and receives the codename. The same pattern works for /api/products/get-ordering-info and /api/products/get-products-info.

How do I get credentials for the Intel Product Catalogue API?

Both Basic credentials and a client_id come from the Intel PIM 360 team on request, per the catalogue's stated onboarding process. Without both, the gateway will return 401 even for read-only lookups.

Can I limit what my agent is allowed to do with the Intel Product Catalogue API?

Yes. Because you run Jentic One self-hosted, your own rules decide which of the catalogue's operations the agent may call, so you can allow only get-codename or get-ordering-info and withhold the rest. Every operation here is a read (get-codename, get-ordering-info, get-products, and get-products-info), so there is no write or delete path an agent could reach. Your Intel Basic credentials and client_id stay under your control and are attached to the request at execution time rather than exposed to the agent.