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.