An API paid per request, with an accountable party behind the address
ZadQ is the first product built on MintID, an x402 seller-verification service operated by the CONECTIA group, a disclosed related party. Through ZadQ, an x402 seller (an API, data or content endpoint paid per request in stablecoins) shows, with an issuer-signed attestation, that an accountable, KYC-verified person or organisation stands behind its payment address, without naming who.
A seller attests once, and every buyer checks it for free
The seller is verified once
An accepted issuer verifies the party behind the seller and issues a conventional, issuer-signed attestation for its payment address and resource. This version, on the classical seller rail, makes no zero-knowledge claim: the seller’s endpoint is public, so unlinkability would add nothing there; the zero-knowledge seller rail follows.
Buyers read the signal for free
Explorers and buying agents check the attestation through MintID’s free verification path before they pay.
A verifier keeps it current
A registered verifier re-checks each seller on a published cadence and publishes its own signed verdict: active, suspended, revoked or unknown.
Standard MintID parts, no protocol change
The pilot is an ordinary issuer-and-verifier pairing. It needs no change to the protocol.
Sellers with something at stake
Sellers and agents with meaningful economic volume, and regulated business counterparties. For them, the attestation brings privacy and compliance by design today; funded recourse is specified and scheduled for the financial-recourse stage of the MintID network. The pilot makes no promise of cost savings.
The pilot changes one thing per step: the proof form, then the topology
The distributed MintID network does not exist yet, so the pilot runs on the single-node production chain and changes one thing at each step.
Single-node production chain
ZadQ runs today on the single-node production chain, in production since 20 September 2026 and operated by the CONECTIA group. The chain runs MintID’s own code without a fork; it is not yet the distributed MintID network.
Zero-knowledge proofs on the same chain
The ten-second zero-knowledge presentation already runs in production. This step, specified and scheduled, moves seller attestations onto it on the same chain: the zero-knowledge seller rail. Buyer-side agent credentials come with MintID’s agent product, and they will use zero knowledge from the start.
On the MintID network
If that network is launched, the topology changes: the pilot moves onto the distributed MintID network. Until then, nothing measured on the single-node production chain counts toward the network’s traction criterion.
What the pilot measures
Success criteria are set in advance and measured. Four signals decide whether the pilot scales:
Sellers sign up for the paid service.
Attested sellers stay beyond 90 days.
Explorers show the verdict to buyers.
Verifiers ask for the signal.
Pilot activity is reported as a related-party pilot and excluded from the network’s traction criterion.
Operated by the CONECTIA group, a disclosed related party
The pilot is operated by Conectia PRO, part of the CONECTIA group and a disclosed related party of MintID; ZadQ is the group’s own product line. Payment addresses held by a third party on a seller’s behalf are outside this version. ZadQ’s own site is zadq.app.
Take part in the pilot
zadq.app describes ZadQ in full, and the whitepaper explains where the pilot sits in MintID’s plan. Sellers, explorers and verifiers who want to take part can get in touch.