For Agents
Look up Intel product codenames, ordering information, and product metadata from the PIM 360 product catalogue.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Intel Product Catalogue Service, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: 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 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.
What an agent can do with Intel Product Catalogue Service API.
Resolve an Intel product to its internal codename via /api/products/get-codename
Retrieve ordering information for an Intel product via /api/products/get-ordering-info
List product records via /api/products/get-products
GET STARTED
Use for: I want to look up the codename for an Intel processor, Retrieve ordering information for a specific Intel SKU, Get detailed product metadata for an Intel CPU, List Intel products available in the catalogue
Not supported: Does not handle silicon ordering fulfilment, live inventory, or customer support — use for Intel product metadata lookup only.
The Intel Product Catalogue Service is a small product information management API published by Intel's PIM 360 team for partners and authorised tools. Across four endpoints it exposes Intel product metadata — codenames, ordering information, full product records, and product information lookups — for use in catalogue, e-commerce, and procurement systems. The API requires both HTTP Basic credentials and a client_id header that PIM 360 issues on request.
Fetch detailed product information via /api/products/get-products-info
Combine credential pairs (Basic auth plus client_id) for partner access
Patterns agents use Intel Product Catalogue Service API for, with concrete tasks.
★ Catalogue Sync into a Reseller Storefront
An authorised Intel reseller can keep their storefront catalogue in sync with PIM 360 by pulling product records and ordering information through /api/products/get-products and /api/products/get-ordering-info. The reseller no longer needs to maintain Intel SKU metadata manually as new lines launch.
Page through /api/products/get-products and write changed rows into the storefront catalogue, attaching ordering information from /api/products/get-ordering-info.
Codename Resolution in Internal Tools
Internal procurement and engineering tools often need to translate between marketing names and internal codenames. /api/products/get-codename returns the codename for a given product, so a tooling layer can normalise references in tickets, BOMs, and forecasts.
Call /api/products/get-codename with the product identifier and surface the codename in the internal record.
AI Agent Catalogue Operator via Jentic
An AI agent given access to the Intel Product Catalogue Service through Jentic can answer questions like 'what is the codename for product X' or 'show me ordering info for SKU Y' on behalf of an authorised partner. Jentic isolates the Basic credentials and client_id in its vault, so the agent only sees structured product data.
Through Jentic, call intel_get_product_info for the requested product and return codename, ordering info, and product details to the caller.
4 endpoints — the intel product catalogue service is a small product information management api published by intel's pim 360 team for partners and authorised tools.
METHOD
PATH
DESCRIPTION
/api/products/get-codename
Get the codename for a product
/api/products/get-ordering-info
Get ordering information for a product
/api/products/get-products
List products
/api/products/get-products-info
Get detailed product information
/api/products/get-codename
Get the codename for a product
/api/products/get-ordering-info
Get ordering information for a product
/api/products/get-products
List products
/api/products/get-products-info
Get detailed product information
Three things that make agents converge on Jentic-routed access.
Credential isolation
Intel requires both Basic credentials and a client_id header. Both are stored encrypted in the Jentic vault and combined into the request at execution time, so the agent never holds either secret directly.
Intent-based discovery
Agents search Jentic by intent (for example 'look up Intel codename' or 'get Intel ordering info') and Jentic returns the matching catalogue operation with its input schema.
Time to first call
Direct integration: about a day to handle dual-auth headers and four lookup endpoints with caching. Through Jentic: under 30 minutes — search, load, execute.
Alternatives and complements available in the Jentic catalogue.
Specific to using Intel Product Catalogue Service API through Jentic.
What authentication does the Intel Product Catalogue API use?
The spec defines two security schemes that are used together: BasicAuth (HTTP Basic) and ClientId (apiKey in the header named 'client_id'). Both must be present, and the credentials are issued by the Intel PIM 360 team on request. Through Jentic, both credentials are stored in the encrypted Jentic vault and merged into the request at execution time.
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.