Can I limit what my agent is allowed to do with the Browser Use API?

Yes. You choose which operations your agent may call, so you can allow starting runs and reading their status while leaving session deletion and profile removal out, and every call it makes is logged. The run's target travels in the request body, so your rules bound which operations run rather than which site is visited.

What authentication does the Browser Use API use?

The Browser Use API authenticates with an API key sent in the X-Browser-Use-Api-Key request header per its OpenAPI spec. Through Jentic the key is stored encrypted by your own instance and added to each request at call time, so it never appears in the agent's prompt or logs.

Can I reuse a logged-in browser state across runs with the Browser Use API?

Yes. You save a browser profile and attach it to a session, so repeated runs start from the same signed-in state instead of authenticating each time. The session operations let an agent open, inspect, and close those browsers as it works.

What are the rate limits for the Browser Use API?

The OpenAPI spec does not specify rate limits for the Browser Use API. For current limits and concurrency guidance, see the Browser Use documentation at https://docs.browser-use.com.

How do I run a browser task with the Browser Use API through Jentic?

Import the Browser Use API from the Jentic API Directory, then have your agent issue a request such as 'run a browser task on this site'. Jentic matches the intent to the start-run operation and returns its input schema so the agent builds a valid request, with your stored API key injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.