Knowledge

Give Qarmiq the context
your product depends on.

Bring together specifications, help pages, policies, and release notes to establish what your product is meant to do. Your team confirms the knowledge before Qarmiq relies on it.

See Qarmiq in action All features
The real thing

Documents in. Confirmed knowledge out.

Knowledge is what the product is meant to do, in your own words, held where scenarios and agents can read it.

  • Add documents by pasting, uploading, pulling from a URL on a schedule, or pushing from your systems
  • Each item waits for a person to confirm it
  • Conflicting items are flagged instead of quietly merged

Where it stands. The crawl is set up with us. It can sign in with a saved test account, but not through single sign-on or multi-step logins, and it starts on request.

Project knowledge4 items
Checkout help pagePulled from a URL, weekly
Confirmed
Refund policyUploaded as Markdown
Needs confirming
Release notes 2.4Disagrees with the refund policy on partial refunds
Conflict
/account/billingNothing explains this page. What is it for?
Question

Illustrative example.

In practice

What it does.

01

Your product’s requirements already exist somewhere.

They may live in documents, help pages, or internal specifications. Bring them together so checks and agents can use a shared understanding of expected behavior.

02

Don’t let conflicting information become a faulty assumption.

Qarmiq flags conflicting information and asks your team about unexplained pages or changes instead of quietly guessing.

03

Your team owns what Qarmiq knows.

Each item waits for human confirmation. Accepted knowledge can inform scenarios and testing, with a clear distinction between confirmed facts and unresolved questions.

Why confirmation matters

Nothing relies on a guess.

What Qarmiq knows about your product is what your team has confirmed, and it is the context behind the scenarios and the agent's tests.

Confirmed by your team

Each item is accepted by a person, so the knowledge is yours and can be traced to who said so.

Conflicts surfaced

Two documents that disagree are shown side by side for someone to resolve, not blended into an average.

Questions about the unexplained

A crawl can map your pages and what each one is for. Qarmiq then asks about pages nothing explains, and about form fields that were removed or changed.

Where it fits

It works with the rest.

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 → Autonomous testing

Let AI investigate. Make every verdict earn your trust.

Choose Test autonomously on one check or a whole run and an AI agent tests it in a real browser. A separate AI judge decides pass, fail or inconclusive from the evidence.

See Autonomous testing → 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 →

Start with what your team already knows.

Bring a few documents. We will show you what Qarmiq asks about before it relies on any of them.

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.