What authentication does the OpenALPR CarCheck API use?

Each recognition call includes a `secret_key` query parameter that identifies your account. Through Jentic that key is stored once, encrypted, by your own instance and supplied at execution time, so the agent never reads the raw value.

How do I recognize a plate from an image?

Send the image to POST /recognize with your `secret_key` and a `country` value. To read vehicle attributes as well, set the `recognize_vehicle` flag, and use POST /recognize_url when the image is already hosted at a URL.

Can it identify the vehicle, not just the plate?

Yes. Setting `recognize_vehicle` on a recognition call adds make, model, color, and body-type predictions alongside the plate read, which is useful for fleet and security records.

What are the rate limits for the OpenALPR CarCheck API?

The OpenAPI specification does not declare rate limits. Send frames at a sensible cadence and back off on error responses; confirm the limits tied to your plan in the OpenALPR documentation.

Do I need an MCP server to use the OpenALPR CarCheck API with an agent?

You do not. Jentic connects the API to your agent directly from the API Directory: import it, store your secret key once, and the agent calls the recognition operations without a separate server to run.

Can I limit what my agent is allowed to do with the OpenALPR CarCheck API?

Yes. Because you run Jentic One yourself, you choose the allowed operations: an agent can be permitted to call recognition from an image while URL-based recognition stays excluded, and the secret key stays with your instance and is applied at call time.