For Agents
Manage Percy visual testing projects, builds, and snapshots for automated visual regression testing.
Use for: I need to automate Percy visual testing, How do I integrate Percy with my CI pipeline, Check Percy build status programmatically, Manage visual regression baselines via API
Not supported: Provides access to percy.io resources and operations as documented in the OpenAPI specification.
Percy (by BrowserStack) is a visual testing and review platform that automates visual regression testing for web applications. The Percy API allows you to manage projects, builds, and snapshots programmatically, enabling integration with CI/CD pipelines, custom testing workflows, and monitoring dashboards. Percy captures screenshots across browsers and viewports, compares them against baselines, and highlights visual differences, making it essential for teams that need to catch visual bugs before production.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Percy 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with Percy API.
Create and manage visual testing projects
Trigger and monitor visual testing builds
Review and approve snapshot comparisons
Integrate visual testing into CI/CD pipelines
GET STARTED
Query build status and visual diff results
Manage project settings and baseline images
Patterns agents use Percy API for, with concrete tasks.
★ CI/CD Visual Testing Integration
Integrate Percy into CI/CD pipelines to automatically catch visual regressions on every pull request. The API enables custom build triggers, status checks, and approval workflows that fit your team's processes. Query build results and block deployments when visual changes are detected.
Use Percy API to trigger builds on PR creation, monitor build status, and query visual diffs to determine whether to approve or block the deployment.
Visual Testing Dashboard
Build custom dashboards that aggregate Percy build results across multiple projects and teams. Use the API to query snapshot comparisons, track visual change trends, and report on testing coverage. Ideal for engineering managers and QA teams monitoring visual quality.
Query Percy projects and builds via the API to extract visual diff metrics, then display trends and alerts in a custom dashboard.
AI Agent for Visual Testing
Let AI agents handle Percy visual testing tasks — triggering builds, checking results, and approving snapshots based on predefined criteria. Through Jentic, agents can discover Percy operations dynamically and integrate visual testing into their decision-making workflows.
Search Jentic for 'percy build status' to find the relevant endpoints, load their schemas, and execute to determine whether visual changes are acceptable.
9 endpoints — percy (by browserstack) is a visual testing and review platform that automates visual regression testing for web applications.
METHOD
PATH
DESCRIPTION
/projects
List all Percy projects
/builds/{id}
Get build details and status
/builds
Create a new visual testing build
/projects
List all Percy projects
/builds/{id}
Get build details and status
/builds
Create a new visual testing build
Three things that make agents converge on Jentic-routed access.
Credential isolation
percy.io credentials are stored encrypted in the Jentic vault and injected at execution time. Raw credentials never appear in agent prompts, transcripts, or response payloads.
Intent-based discovery
Agents search by intent and Jentic returns the matching endpoint with its schema and any required parameters.
Time to first call
Direct percy.io integration: days to weeks to model all resources and operations. Through Jentic: under 1 hour — search, load schema, execute.
Specific to using Percy API through Jentic.
What authentication does the Percy API use?
The Percy API uses bearer authentication. Through Jentic, credentials are stored encrypted and injected at execution time so they never enter the agent's context.
How many endpoints does the Percy API have?
The Percy API exposes 9 endpoints across its surface area.