canonical: https://jentic.com/apis/platform.mattel/hot-wheels-catalog

# Platform Mattel Hot Wheels Catalog Service API

The Hot Wheels Catalog Service API provides read access to a catalog of Hot Wheels vehicles backed by a MongoDB collection, with flexible Atlas Search queries. It returns catalog items and lets authorized admins create, update, count, and delete vehicle reports through a controlled HTTP interface. The service abstracts direct database access behind role-based authentication, validation, and logging.

## For AI agents

Search and read a catalog of Hot Wheels vehicles with Atlas Search queries, and create, update, count, or delete vehicle reports. Access is gated by role-based API key authentication.

## Scope

Does not handle payments, shopping carts, or order fulfillment. Use for Hot Wheels catalog search and vehicle reports only.

## Capabilities

- Search the Hot Wheels vehicle catalog with Atlas Search queries
- Retrieve the full list of vehicles in the catalog collection
- File vehicle reports and update them
- Count matching reports and remove outdated ones

## Use cases

### AI Catalog Agent

An AI agent connected to the Hot Wheels Catalog Service through Jentic can answer questions about the vehicle collection by running an Atlas Search query and reading the catalog, then file a report when it spots a data issue. Because access is gated by a role-based key, the agent operates within the permissions the key grants.

Example prompt: Search the catalog for a vehicle by name and return its catalog record

### Vehicle Catalog Search

Query the Hot Wheels catalog with flexible, pipeline-based Atlas Search to return formatted results. The search endpoint runs aggregation-style queries over the collection, and the catalog endpoint lists all vehicles for browsing.

Example prompt: Run an Atlas Search query for vehicles matching a series name and read the matching items

### Report Management

Track issues against catalog vehicles by filing, updating, counting, and removing reports. The report endpoints let an agent create a report, update it as the issue is resolved, count how many remain, and delete those that are closed.

Example prompt: Create a report for a catalog vehicle, then update it once the issue is resolved

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/search` | Search catalog items with Atlas Search |
| GET | `/catalog` | Read all catalog items |
| GET | `/report` | Count reports |
| POST | `/report` | Create a report |
| PUT | `/report` | Update a report |
| DELETE | `/report` | Delete a report |

## Key resources

- **Catalog** — Hot Wheels vehicles read from the catalog collection
- **Search** — Atlas Search queries over the vehicle collection
- **Reports** — Vehicle reports created, updated, counted, and deleted

## AI readiness

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.

- **Score:** 47 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 90 / 100
  - Developer Experience & Jentic Compatibility: 66 / 100
  - AI-Readiness & Agent Experience: 23 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 63 / 100
- **View full report:** https://jentic.com/apis/platform.mattel/hot-wheels-catalog/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Hot Wheels Catalog Service by hand means sending its API key in a custom header and shaping Atlas Search queries and report payloads yourself. Through Jentic you install once, import it from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** The catalog and report operations carry their filters in the request body, so a rule bounds which operations your agent may call rather than which record. A rule can allow catalog search and reads while leaving report deletion out unless you add it.
- **Credential handling:** Your Hot Wheels Catalog API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'search the vehicle catalog', and Jentic returns the matching Hot Wheels Catalog operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **eBay Commerce Catalog** — Product catalog data for commerce listings, where the Hot Wheels service catalogs vehicles.
- **Catalog Machine** — Product catalog builder and management, where the Hot Wheels service exposes a fixed vehicle catalog.
- **Algolia Search** — Hosted search engine, complementing the catalog's built-in Atlas Search.

## FAQ

### Is there a Hot Wheels Catalog MCP server?

You don't need an MCP server to give your agent the Hot Wheels Catalog Service API. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent can search the catalog and file reports. Operations are discovered on demand, so your agent's context stays lean.

### Can I limit what my agent is allowed to do with the Hot Wheels Catalog API?

Yes. The catalog and report operations carry their filters in the request body, so a rule bounds which operations your agent may call. Write a rule that allows only catalog search and reads, so the agent can browse vehicles but cannot delete reports unless you add that operation, and every call is logged.

### What authentication does the Hot Wheels Catalog Service API use?

The Hot Wheels Catalog Service API authenticates with an API key sent in the api_key header per its OpenAPI spec, and the service enforces role-based access behind it. With Jentic, the key is stored encrypted by your own Jentic One instance and injected at call time.

### Can I search the Hot Wheels catalog with the API?

Yes. The search endpoint runs Atlas Search aggregation queries over the vehicle collection and returns formatted results, while the catalog endpoint lists every vehicle. An agent can combine them to find and read specific vehicles.

### Can I file a vehicle report with the Hot Wheels Catalog API?

Yes. The report endpoints create a report, update it, count how many match, and delete closed ones. An agent can file a report when it finds a catalog issue and update it as the issue is resolved.

### How do I search the catalog with the Hot Wheels Catalog API through Jentic?

Import the Hot Wheels Catalog Service API from the Jentic API Directory, store your API key once, and have your agent search by intent such as 'search the vehicle catalog'. Jentic returns the search operation with its input schema, and your agent passes the query. To run it on your own infrastructure, install Jentic One from its GitHub repo.