API testing that ships as a suite
Collections, environments, assertions - run as a suite, share the report.
QA platform25 tools09 AI providers
One governed workspace for the whole test pass - API testing, interception, capture, live review, and AI on your own keys - from first repro to filed issue.
Catch the failure with its evidence. The run flags the regression; frame and request are already attached.
01The workflow
One flow carries a defect from the first repro to a filed issue. Nothing retyped, nothing lost on the way.
A typical test pass spread across 9 unrelated browser tabs - a REST client, a JSON formatter, screenshot and recording apps, a chat thread, a shared drive, a spreadsheet of test cases, and the issue tracker - joined by 8 manual copy, paste, upload, and retype steps.
9 tabs8 manual handoffs2 unsaved0 audit trail
Record, screenshot, or catch the failing request. Redact before it leaves the device.
Your own model turns the evidence into a reproducible report or test cases.
Comment on the live page, assign an owner, set a priority, decide.
One click into Jira, Linear, or GitHub with everything attached.
1 workspace1 click to the trackerfull audit trail
Handoffs retyped by hand
The same defect written three times.
Evidence scattered
Frames in a folder, requests in a chat.
Unvetted tools, real data
Payloads pasted into whatever site ranked first.
02The platform
Each one is built for the work QA does day to day, and evidence from one becomes the input to the next.
Collections, environments, assertions - run as a suite, share the report.
Mock, rewrite, and inject failures on the fly. Never blocked on a backend.
5 surfaces, 9 providers, one model policy per workspace.
Record, screenshot, annotate, redact, export. Every frame stays on the device.
Click the live page to comment, assign, prioritize, and sign off.
JSON, diffs, regex, JWTs, PDFs, test data, contrast - the same tooling for everyone.
03The toolkit
Everything an engineer reaches for during a test pass, under one set of conventions instead of a dozen unvetted sites.
25 tools05 shared with the workspace20 private to the engineer
04Security & governance
Roles, an audit trail, scoped secrets, and processing that stays on the engineer's machine. Answered by default.
Permission catalog
System roles, resolved live
| Permission | Viewer | Editor | Admin | Owner |
|---|---|---|---|---|
| View shared resourcesresources.read | ||||
| Edit shared resourcesresources.write | ||||
| Run API teststools.api_testing.execute | ||||
| Use API secretssecrets.use | ||||
| Manage API secretssecrets.manage | ||||
| Invite membersmembers.invite | ||||
| Manage custom rolesroles.manage | ||||
| View audit logworkspace.audit.read | ||||
| Delete workspaceowner onlyworkspace.delete |
Four system roles plus custom roles from a granular catalog.
Membership, role edits, and sensitive actions, recorded.
Using a secret and managing one are separate permissions.
20 of 25 tools never upload a byte. PDF redaction and compare that never uploads your document.
Verified accounts, named invitations, revocable any time.
Every tool declares its scope before you start typing.
05 In short
One governed workspace. One flow from capture to a filed issue. Everything on this page ships today.