Connectors

Bring every verification
result into one view.

Some product requirements need browser checks. Others need specialized tools. Qarmiq brings supported external verification results into the same run view, alongside its own checks.

See Qarmiq in action All features
The real thing

An outside verdict, beside the rest.

A check can be marked as verified by a connector, and its result appears in the run labeled with the tool that produced it.

  • A check says it is verified by a connector, so the run grid expects its verdict
  • The result is labeled with the tool that produced it
  • DeepEval tests AI features, such as a support assistant
Release 2.4 smoke runVerified by
A paid order always produces an invoiceBrowser check
the AI agentpassed
The support assistant never invents a refund policyDeepEval: 2 of 40 refund prompts drifted
DeepEvalfailed
A customer can always sign inVerified script
a scriptpassed

Illustrative example.

In practice

What it does.

01

Use the right verifier for the job.

A browser check may verify checkout behavior. A specialized tool such as DeepEval can evaluate an AI feature. Each result is labeled with the tool that produced it.

02

One product. Multiple sources of evidence.

Bring supported external verdicts into the same view as manual tests, autonomous checks, and verified scripts, so your team can understand the results together.

03

Know where every result came from.

Each result identifies its source, helping the team distinguish what was verified by Qarmiq’s own testing mechanisms from what was assessed by an external tool.

Why connectors

One list, whatever proves it.

Some promises are not proven by a browser test: a model’s answers, a load profile, a scan. They still belong on the same list.

Beside every other verdict

An outside result is read in the same grid, with the same evidence expectations.

Separate from the model

A verifier is an independent opinion, which is the point of using one.

Built for verifiers first

Verifier connectors are built. Data-feed connectors, such as GA4, and a published connector SDK are on the roadmap.

Where it fits

It works with the rest.

Runs and verdicts

Know exactly what passed, what failed, and where.

A run tests a fixed set of scenarios on one environment, across several browsers, and records pass, fail, blocked or skipped for each check. It keeps the exact wording it tested.

See Runs and verdicts → Scenarios and checks

Define what your product must always get right.

A scenario states one thing that must always be true, in a single sentence. Its checks say what must be verified to prove it. Nothing in them is a click or a selector, so a redesign does not invalidate them.

See Scenarios and checks → MCP server

Give your coding agent the context to build without breaking what works.

Qarmiq’s MCP server lets AI coding tools read project and defect context and write scenarios and checks, with an API key. Every write is planned, confirmed and logged.

See MCP server →

See how your existing verification tools fit into Qarmiq.

Tell us which tool already proves something about your product, and we will show you where it would sit.

See Qarmiq in action All features

Qarmiq is not self-serve yet, so we set each team up directly. Pricing is one flat price per project.