API + MCP native

Know whether the UI your agent built is actually usable.

AgentScope runs real browsers against complex web apps, detects blocked controls, clipping and responsive failures, explores meaningful states, and returns machine-readable evidence your coding agents can fix.

✓ Chromium · Firefox · WebKit✓ 6-view responsive matrix✓ Deterministic first, vision second
  uiqa.json
POST /v2/ui/audit
{
  "target": "https://app.example.com/editor",
  "options": {
    "viewport_matrix": "standard",
    "verify_physical_clicks": true
  }
}

critical  toolbar overlaps export button
major     properties panel clipped @ 390px
fix_packet  src/Toolbar.tsx:184
gate        FAIL · exit_code 2
6standard viewports
3browser engines
41MCP tools
1 APIfor agents + CI
Beyond screenshot diffs

UI QA that reasons about interaction, not pixels alone.

Traditional visual testing asks “did pixels change?” AgentScope asks the harder question: “can a human or agent actually use what shipped?”

01 / HIT TARGETS

Real clickability evidence

Detect a button that exists in the DOM but sits under an overlay, sticky toolbar or higher z-index receiver.

02 / RESPONSIVE

One audit, six viewports

Desktop through small mobile, with findings deduplicated while preserving every affected viewport.

03 / STATE GRAPH

Explore meaningful UI states

Replay tool selection, sidebars, dialogs and editor modes so transient layout failures stop hiding in interaction paths.

04 / FIX PACKETS

Evidence your agent can patch

Selectors, blockers, source hints, component/CSS context and replay steps become a concise machine-readable fix packet.

05 / QUALITY GATES

Block bad UI before deploy

Turn critical overlap, clipping, accessibility and interaction failures into CI exit codes and release policy.

06 / PROVIDER NEUTRAL

Use from any coding agent

HTTP API and MCP surface mean Claude, ChatGPT, CI workers or your own orchestration can invoke the same runtime.

Agent loop

Build → inspect → fix → prove.

AgentScope fits after implementation and before merge or deployment. It does not replace your coding agent; it gives that agent a better sensory and verification layer.

01

Audit

Capture geometry, hit stacks, accessibility and screenshots.

02

Explore

Traverse high-risk editor and application states.

03

Fix packet

Give the coding agent bounded, source-oriented evidence.

04

Verify

Re-run only affected states/viewports, then a quick regression.

CapabilityScreenshot diffAgentScope
Pixel change detectionYesYes
Blocked button / hit receiverIndirectDeterministic
State exploration + replayLimitedBuilt in
Source/component hintsVariesFix packet
MCP for coding agentsRareNative
Release quality gateYesYes
Simple execution credits

Pay for useful browser work, not every pixel.

An execution credit tracks an AgentScope browser/UI-QA unit. Start free, then scale concurrency and evidence retention as agents do more work.

Compare all plans →

Give your coding agents eyes—and a pass/fail standard.

100 execution credits are included. No payment method required for Free.

Create your API account →