Who it's for
Who this is for.
Four kinds of company. One thing in common: they get paid by, or route money to, parties they have never met.
This is you if…
You sell APIs or data over x402
Your endpoints take money from agents you have never met, and you want to show a real company is behind them without a signup form.
You route other people's agents or money
You run a marketplace, directory or explorer, and every unverified listing is your reputation.
You answer to a regulator
Evidence for your compliance — identity and accountability. A trust layer for the public perimeter.
You publish content that bots want
Crawlers and agents already read your pages. Charge them per request over x402, and show them an accountable operator stands behind the endpoint they pay.
What you no longer build yourself
ZadQ systems store attestation metadata only. Raw KYC material lives exclusively inside the issuer-side KYC boundary and never enters ZadQ databases, logs or analytics. You keep no customer database and run no verification of your own.
Identity is verified in line with the European digital-identity framework (eIDAS). Between the parties, no personal data changes hands unless a dispute is escalated, so your transactions carry no GDPR burden from the verification.
And agent operators
The accountable party behind an agent that pays. It enrols on the same dashboard as vendors, is verified once, and mints a credential for each of its agents. No agent is ever blocked for not being attested.
Agent operators enrol on the seller dashboard. An agent that is not attested keeps paying every vendor that has not chosen to require attested agents: nothing blocks by default.
Selling over x402? Let's find out if we fit.
We are onboarding our first partners: API sellers, publishers, marketplaces and regulated platforms.