Skip to main content
QWED v8.0.0 is the current release. Every VERIFIED answer now carries a signed attestation you can check against /.well-known/jwks.json. Some settings, response shapes, and SDK types change, so read the upgrade steps before you upgrade.

​
What is QWED?

QWED (Query With Evidence & Determinism) is a trust boundary for AI systems:
  • LLMs can translate user intent into structured claims.
  • QWED verifies those claims with deterministic engines before execution or response.
  • You get proof-backed outcomes instead of probability-only confidence.
QWED is designed for LLM verification, AI agent security, verified tool calls, prompt injection defense, and deterministic transaction verification in high-stakes workflows.
“Do not trust generated output. Verify it.”

​
Explore common verification problems

LLM verification

Learn how formal verification for LLMs differs from prompting, RAG, and output formatting.

AI agent security

Add pre-execution checks, policy enforcement, and budget controls for agent actions.

Prompt injection defense

Harden your stack against prompt injection, exfiltration, and unsafe execution paths.

QWED MCP

Give MCP clients access to QWED’s deterministic verification libraries.

​
When to use QWED first

Math and logic

Verify equations, constraints, and logical claims before they reach users.

Code and SQL

Catch unsafe patterns, injection risks, and structural errors before execution.

Agent tool calls

Inspect actions and payloads before external systems are touched.

High-stakes workflows

Add deterministic checkpoints for finance, legal, tax, and regulated systems.

​
Quick start (5 minutes)

The examples below use the qwed CLI that this installs. The qwedai/qwed-verification:8.0.0 Docker image runs the API server instead; see Self-hosting.
1

Install and configure

Follow Installation and set your provider with LLM configuration.
2

Run first verification

Use Quick start to validate math, logic, code, and SQL.
3

Integrate into production flow

Use Integration getting started and Production deployment.

​
Verification engines at a glance

Math

SymPy-based symbolic verification.

Logic

Z3 SAT/SMT verification with models.

Code

AST and symbolic checks for risky behavior.

SQL

Parser-backed SQL safety and validation.

Schema

Type and shape validation for structured outputs.

Taint

Data-flow tracking for untrusted inputs.

See all engines

Explore core, analysis, and specialized engines.

​
What’s new in v8.0.0

Signed verdicts

The server signs the status, proof_ref, and statement hash of every VERIFIED answer with an ES256 attestation, and the admission on routes that decide one. Check it against the public keys at /.well-known/jwks.json. Set QWED_SIGNING_KEY or QWED_SIGNING_KEY_FILE so attestations keep verifying across restarts and replicas. Read about attestations →
The server now refuses to start without QWED_AUDIT_SECRET_KEY. The Docker image runs the API server instead of the GitHub Action, and the Go module path moves to /v8. A math claim proven false is now VERIFIED, not UNVERIFIABLE, with admission BLOCKED in API and SDK responses (DENY in Verification Context documents and CLI output). Read the upgrade steps →
  1. Core concepts
  2. Architecture overview
  3. SDKs overview
  4. API overview
  5. Integration guide