SpinUI home
Contact us

Features

Pricing

Sign in

Run from your pipeline or your coding agent

For developers who want a test run after every deploy, and for teams that use coding agents. Start suites from a pipeline, a deploy script or an agent, and read the results back.

How it works

  1. Create a trigger or a token. A trigger URL starts one suite. A CI token lets a pipeline start runs and read results through the API. An agent token connects a coding agent.
  2. Call it from your system. Send an HTTP POST to the trigger URL from a deploy script, or use a CI token from GitHub Actions or Azure Pipelines. We provide sample pipeline files.
  3. SpinUI runs the suite. Repeated calls while a triggered run is still waiting or running give that one run.
  4. Read the result. Read the outcome through the API, or let a coding agent read why a run failed.

What is included

  • Trigger URLs. A trigger URL starts one suite when another system sends it an HTTP POST. Use it from a deploy script, or from WordPress after a plugin update. SpinUI shows the URL once, and you can revoke it at any time.
  • One run, not five. Repeated calls while a triggered run is still waiting or running give that one run, so five plugin updates do not start five runs.
  • CI tokens. A CI token lets a pipeline start runs and read results through the API. We provide sample pipeline files for GitHub Actions and Azure Pipelines.
  • MCP for coding agents. Claude Code, Codex, Cursor, VS Code and Copilot can read your suites and tests, start runs and read why a run failed. An agent token works in one organization, with your role, and you can revoke it at any time.
  • Agents propose, you approve. Agents read and run by default. If you allow changes, an agent can only propose them, and a person approves each one in SpinUI before it can be applied.
  • Hard limits. An agent can never change your suites, schedules, environments, secrets, members or plan.

Plans. Trigger URLs and CI tokens: Individual and up. MCP for coding agents: Team and Business.

Good to know

The sample pipelines use the SpinUI command-line tool, which we have not published yet. Trigger URLs and the API work without it. Content your agent reads, such as website text and test emails, goes to that agent and its provider, not through us.

Questions

Do I need the SpinUI command-line tool?

No. Trigger URLs and the API work without it. The sample pipeline files use the command-line tool, which we have not published yet.

What stops five deploy events from starting five runs?

Repeated calls while a triggered run is still waiting or running give that one run.

What can a coding agent do through MCP?

Read your suites and tests, start runs and read why a run failed. If you allow changes, an agent can only propose them, and a person approves each one in SpinUI. An agent can never change your suites, schedules, environments, secrets, members or plan.

Which plans include trigger URLs and MCP?

Trigger URLs and CI tokens: Individual and up. MCP for coding agents: Team and Business. The pricing page shows the limits for each plan.

What if a trigger URL or token leaks?

Revoke it. SpinUI shows a trigger URL once, and you can revoke a trigger or a token at any time.

Keep reading

Check your site the way a person would

Record your first test by using your site.

Contact us Sign in