About ZadQ

ZadQ lets vendors, and the agents that pay them, prove that an accountable, KYC/KYB-verified person or organisation stands behind them — without revealing who. Anyone checks the verdict for free.

ZadQ is a verification service for agent payments. Vendors that sell to machines over x402, and the agents that pay them, prove that an accountable, KYC/KYB-verified person or organisation stands behind them — without revealing who. Anyone reads the verdict free of charge: buyers, agents, explorers and marketplaces, next to the signals they already use, and every integration keeps working when no verdict is available. ZadQ serves vendors and agent operators with meaningful economic volume, and regulated B2B counterparties. We sell privacy, funded recourse and compliance-by-design. ZadQ is operated by Conectia OÜ (Estonia). It is built on the MintID identity network and operated by the CONECTIA group, the network's first implementer, on the same published terms as any issuer — a relationship we disclose wherever it is relevant, because the point of the system is that you don't have to trust us.

Live and early

ZadQ is live and onboarding its first operators. The verification model, the verdicts and the integration surfaces on this site are running.

Onboarding runs in the seller dashboard: for a vendor, from the wallet login to the first published verdict; for an agent operator, from the wallet login to the first agent credential.

Early means small, not provisional. What this site describes in the present tense is running today; what is not running yet is named in the future tense, or not at all.

Who operates it

ZadQ is operated by Conectia OÜ, a company registered in Estonia and the entity named in our terms and privacy policy. Conectia OÜ belongs to the CONECTIA group.

The accountability we sell, a named operator behind a service, is the one we practise. You know who answers for ZadQ before you decide to use it, the same way your buyers will know who answers for you.

Built on the MintID identity network

ZadQ issues and checks its attestations on the MintID identity network. An accepted issuer verifies the seller and issues the credential or signs the attestation; the network publishes the issuer's status, bond and registration on terms anyone can verify on its public record; ZadQ's verifier decides. MintID itself issues nothing and certifies nothing. ZadQ's verifier and the operator's issuer were admitted through the same path the network offers anyone: a governance proposal, today voted by the network's single validator and, once the compliance council is seated, by the council; the same slashable bond; the same thirty-second status roots; all of it on the public record.

Verification stays free to whoever runs the check, and nothing in a buyer's, seller's or platform's flow ever waits on us: when no verdict is available the badge reads "unknown" and the flow continues under the checking party's own policy.

The relationship, disclosed on purpose

ZadQ is built on the MintID identity network and operated by the CONECTIA group, the network's first implementer, on the same published terms as any issuer: the same admission, the same bond on the network, the same status rules, verifiable by anyone on the network's public record. We disclose this relationship wherever it is relevant.

That makes us a related party of the network we build on. We could have left it for you to find. We say it here, and wherever else it is relevant, because a related party you can check is worth more than one you are asked to trust.

It works in your favour. Nothing about our standing rests on our word: the terms are the network’s, not ours, and the record is public. You can check us there without asking us.

It also binds us. Being first earns the group no separate rules: whatever holds any issuer to its terms holds us to ours.

What we do not publish yet

We publish no adoption metrics today because there are none to publish.

When there is a first dataset, the series will be registry-based or aggregate, dated, monthly, and labelled with our related-party position; the group’s own verifier deployment will be reported as context and never counted as independent.

Nor do we publish how the platform is deployed. Infrastructure detail helps an attacker more than it helps you; what you need to hold us to account is in our disclosures and on the network’s public record.

See the published metrics

How to reach us

Write to hello@zadq.net with your side, your rail and roughly your volume. You get a straight assessment of fit, including “not you”.

Ready to be attested? Open the seller dashboard. Operating agents rather than selling? The agent operators page is yours.

Writing about ZadQ? The press kit carries the lines we use, the facts of record and the brand assets. Open the press kit

Selling over x402? Let's find out if we fit.

We are onboarding our first partners: API sellers, publishers, marketplaces and regulated platforms.