Reference implementation: Mandact

A verifier needs something to verify. Mandact produces evidence in the formats specified here. KYA verifies it – and any other evidence by the same rules.

In short

Mandact issues evidence in the KYA formats. KYA verifies it by the same rules as any other evidence.

Why there is a reference implementation

A specification without an implementation stays on paper. The reference implementation shows that the formats work in real operation: with real agents, real decisions before execution and real receipts afterwards. It is also the first touchstone for the test vectors.

What Mandact does

  • Issue mandates for your own agents: action types, amount limits, counterparties, validity, as SD-JWT VC
  • Decide before every execution whether an action is covered, through a gateway for MCP and HTTP tools, fail-closed
  • Record every decision signed and every execution as a chained receipt
  • Produce an evidence dossier that can be verified offline
  • Revoke mandates at any time, effective from the next decision

Explore Mandact

How Mandact evidence is verified here

Exactly like everything else: with the same engine, the same rules and no special treatment. Mandact's field names are listed as aliases in the claims profile as far as they are publicly documented. The complete mapping is anchored with a real Mandact artifact as a test vector; until then the report honestly marks every unmapped field as not checked.

Separating verifier and product

KYAMandact
RoleIndependent verificationIssuance, decision, receipt
PriceFree, permanentlyCommercial subscription
AccountNoneFor operators
DataStays in the browserIn the customer's operation
RulesPublic, versionedImplements the same rules

If the verifier charged money, it would no longer be a verifier but a second product. That is why KYA is not monetized.

Other implementations

Every implementation that passes the test vectors is listed on equal terms. Mandact has no precedence other than having been first.