Skip to main content
QWED is defined by formal specifications that enable interoperability.

Core specifications

SpecificationVersionDescription
QWED-SPECv1.0.0Core protocol definition
QWED-Attestationv1.0.0Cryptographic proofs
QWED-Agentv1.0.0AI agent verification

What’s in a spec?

QWED-SPEC v1.0

The core specification defines:
  • Request/response format — JSON schemas for API
  • Verification engines — Math, Logic, Code, SQL, etc.
  • QWED-Logic DSL — Grammar for logical expressions
  • Error codes — Standardized error taxonomy
  • Versioning — Semantic versioning rules

QWED-Attestation v1.0

The attestation specification defines:
  • JWT format — ES256 signed tokens
  • Claims — Standard and custom JWT claims
  • Trust anchors — Issuer verification
  • Chain validation — Linked attestations

QWED-Agent v1.0

The agent specification defines:
  • Registration — Agent identity and permissions
  • Action verification — Pre-execution checks
  • Budget management — Cost and rate limits
  • Trust levels — 0-3 autonomy scale

JSON schemas

Machine-readable schemas are available at:
specs/schemas/
├── request.v1.json
├── response.v1.json
├── attestation.v1.json
└── agent.v1.json

Implementing QWED

To implement the QWED protocol:
  1. Parse requests per request.v1.json
  2. Route to appropriate verification engine
  3. Return responses per response.v1.json
  4. Optionally generate attestations per QWED-Attestation

Conformance levels

LevelRequirements
BasicRequest/response format
Standard+ All 8 engines
Full+ Attestations + Agent API