YOUR VENDOR WORKSPACE
Less administration.
Better experiments.
Bring your vendors, sessions and implementation work into one place. Turn a promising tool into a test you can compare fairly.
Loading sign-in…
Advanced: workspace access token
Kept in memory for this session only. Vendor credentials belong in your secret manager.
CONNECT YOUR RUNTIME
Connect a vendor runtime.
Check that this code matches the code in your runtime CLI. This connects bounded inspection work and evidence reporting. It grants no purchase authority.
Connection code:
Vendors
Manage access, setup and inspection evidence.
Add a vendor
No vendors yet
Add your first vendor to track access and begin an inspection.
| Vendor | Category | Session | Setup | Checks | Updated | Actions |
|---|
Runs & evidence
Inspect vendors and resolve operator handoffs.
No runs yet
Open a vendor and choose an inspection to collect the first evidence.
| Vendor | Intent | Status | Created | Updated | Evidence |
|---|
WORKSPACE INFRASTRUCTURE
Runtime
Configuration and connection status reported by this instance.
Connect your tools
Use the same workspace from the web, CLI, or an MCP client.
API specification · Capabilities · Release details
Authenticate once in the CLI, then use the MCP command as your client's stdio server. Access stays scoped to this environment and your workspace.