canonical: https://jentic.com/apis/intel.com/intel

# Intel Product Catalogue Service

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.

## For AI agents

Look up Intel product codenames, ordering information, and product metadata from the PIM 360 product catalogue.

## Scope

Does not handle silicon ordering fulfilment, live inventory, or customer support - use for Intel product metadata lookup only.

## Capabilities

- 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`
- Fetch detailed product information via `/api/products/get-products-info`
- Combine credential pairs (Basic auth plus client_id) for partner access

## Use cases

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

Example prompt: 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.

Example prompt: 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.

Example prompt: Through Jentic, call intel_get_product_info for the requested product and return codename, ordering info, and product details to the caller.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/products/get-codename` | Get the codename for a product |
| GET | `/api/products/get-ordering-info` | Get ordering information for a product |
| GET | `/api/products/get-products` | List products |
| GET | `/api/products/get-products-info` | Get detailed product information |

## Key resources

- **Products** — Lookup endpoints for Intel product records and metadata.

## Why Jentic

- **Setup:** Wiring the Intel Product Catalogue Service by hand means combining Basic credentials with a client_id header on every request and tracking its four product lookup endpoints. Through Jentic you install once, import the Intel Product Catalogue Service from the API Directory, store both secrets once, and your agent calls it.
- **Permission scoping:** The Intel catalogue exposes read-only lookups such as get-codename and get-ordering-info with parameters in the query, so limit the agent to the operations it needs rather than to one product. Every operation here is a read, so no write or delete path is available to add.
- **Credential handling:** Your Intel Basic credentials and client_id are stored once, encrypted, by your own Jentic One instance and combined into each request at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'look up an Intel codename' or 'get Intel ordering info', and Jentic returns the matching catalogue operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Digi-Key API** — Digi-Key offers a broader electronic component catalogue including Intel parts.
- **Best Buy API** — Best Buy exposes consumer-product catalogue data that often features Intel-powered devices.
- **Algolia API** — Algolia indexes catalogue data so customer-facing search works on top of Intel metadata.

## FAQ

### 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 your encrypted Jentic One instance 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.

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