Install Jentic One Beta

Connect the LambdaTest Screenshots API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the LambdaTest Screenshots API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Flambdatest.com%2Flambdatest" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Flambdatest.com%2Flambdatest" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with LambdaTest Screenshots API.

Start a screenshot test across selected browsers and devices

List available devices, browsers, and operating systems

List supported screen resolutions and locations

Check the status of a running test

Retrieve captured screenshots for a test

GET STARTED

Start building with LambdaTest Screenshots API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use LambdaTest Screenshots API for, with concrete tasks.

★ Run cross-browser screenshot tests

Visual bugs often appear only in specific browsers or devices. The LambdaTest Screenshots API starts a test that captures a page across chosen browser, operating system, and device combinations, letting a CI step or tool verify appearance without a manual pass. A single request queues screenshots for every selected configuration.

Start a screenshot test for a URL across a chosen set of browsers.

Discover test configurations

Choosing what to test against requires knowing the supported options. The LambdaTest Screenshots API lists devices, operating system and browser combinations, resolutions, and locations, so an application can build a valid test request without guessing. These lists reflect the configurations currently available.

List the available browser and operating system combinations before starting a test.

Collect screenshot results

After a test runs, the images need to reach the tool that requested them. The LambdaTest Screenshots API reports test status and returns the captured screenshots for a test, individually or bundled as a zip, letting an application store or display the output. Status can be polled until the test completes.

Retrieve the completed screenshots for a test and download them as a zip.

Agent-run visual checks

An AI QA assistant can capture and collect cross-browser screenshots for a user without a developer wiring each call. Through Jentic the agent matches an intent such as 'screenshot the landing page in Chrome and Safari' to the LambdaTest start and results operations and runs them. The credentials stay in the user's Jentic One instance and never reach the agent's prompt.

Start a screenshot test for the requested page and browsers, then return the captured images.

Key Endpoints

9 endpoints — the lambdatest screenshots api captures automated screenshots of a web page across many browsers, operating systems, devices, and resolutions.

METHOD

PATH

DESCRIPTION

POST

Start a screenshot test across selected browsers.

GET

/devices

List available devices.

GET

/os-browsers

List supported operating system and browser combinations.

GET

/{test_id}

Retrieve the screenshots for a test.

GET

/{test_id}/zip

Download all screenshots for a test as a zip.

GET

/resolutions

List supported screen resolutions.

POST

Start a screenshot test across selected browsers.

GET

/devices

List available devices.

GET

/os-browsers

List supported operating system and browser combinations.

GET

/{test_id}

Retrieve the screenshots for a test.

GET

/{test_id}/zip

Download all screenshots for a test as a zip.

GET

/resolutions

List supported screen resolutions.

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the LambdaTest Screenshots API yourself means handling Basic authentication, choosing valid device and browser combinations, and polling for test completion. With Jentic you install once, import LambdaTest Screenshots from the API Directory, and store your credentials a single time.

Permission scoping

Jentic lets you grant your agent only the operations it needs, such as starting tests and reading results without the stop operation, and enforces that on every call.

Credential isolation

Your LambdaTest username and access key are stored once, encrypted, by your own Jentic One instance. They are injected when a call runs and never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents find the LambdaTest Screenshots API through Jentic's intent search, matching a request like 'screenshot this page in Chrome' to the right operation without hardcoded endpoints.

FAQs

Specific to using LambdaTest Screenshots API through Jentic.

What can an AI agent do with the LambdaTest Screenshots API through Jentic?

An agent can start a cross-browser screenshot test, list the available devices and browsers, check the test status, and retrieve the captured images individually or as a zip. Through Jentic the agent matches an intent to the right operation and runs it with your credentials injected at execution time.

How do I authenticate with the LambdaTest Screenshots API?

The API uses HTTP Basic authentication with your LambdaTest username and access key. You store those credentials once in your Jentic One instance, and they are added to each call at run time rather than exposed to the agent.

Which browsers and devices can I capture screenshots on?

The API lists supported devices, operating system and browser combinations, resolutions, and locations, so you can build a valid test from the current options. Query those lists before starting a test to choose the configurations you need.

Does the Screenshots API document rate limits?

The OpenAPI specification does not state rate limits; capture allowances depend on your LambdaTest plan. Check the current limits for your account in the LambdaTest dashboard and documentation at https://www.lambdatest.com/support.

Can I control what my agent is allowed to do with the LambdaTest Screenshots API?

Yes. Jentic lets you allow only the operations your agent needs, for example starting tests and reading results while withholding the stop operation. Your Jentic One instance enforces that boundary on every call and keeps your credentials outside the agent's context.

LambdaTest Screenshots API

Name: LambdaTest Screenshots API
Brand: LambdaTest Screenshots API
Availability: InStock

Official vendor OpenAPI document · agent-readyDeveloper ToolsTesting Qabasic9 EndpointsREST

For Agents

Start cross-browser screenshot tests, list available devices and browsers, and retrieve the resulting images individually or as a zip.

Use for: Capture screenshots of a page across browsers, List the browsers I can test against, Check whether my screenshot test finished, Download the screenshots from a test

Not supported: Captures screenshots only; it does not run functional or Selenium test scripts, and does not host real-device interactive sessions.

The LambdaTest Screenshots API captures automated screenshots of a web page across many browsers, operating systems, devices, and resolutions. It starts a screenshot test, lists the available devices and browser combinations, reports test status, and returns the resulting images individually or as a zip. Requests and responses are JSON, so an agent can run cross-browser screenshot checks and collect the output without a manual test run.

Jentic One on Github View OpenAPI Document