Can I list available browsers with the TestingBot API?

Yes. Use the GET /browsers endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the TestingBot API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I list available browsers through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list available browsers'. Jentic returns the matching TestingBot API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the TestingBot API have?

The TestingBot API exposes 31 endpoints covering browsers, builds, configuration operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which TestingBot operations and credentials your agent may use. TestingBot puts the team-member id in the URL path (/team-management/users/{id}), so you can pin the agent to reading one member with GET /team-management/users/{id} and nothing else. Write operations such as PUT /user or POST /team-management/users are excluded unless you explicitly add them.