Your agent can't tell a real merchant from a copy of one.
KYM gives a merchant a verified identity bound to its own domain, and puts the check inside the payment path, so an AI shopping agent cannot pay an impostor even if it never heard of us.
Everyone else verifies the agent. KYM verifies the merchant.
Agents don't get suspicious. They get tasks done.
An agent told to “find the cheapest USD/SGD reference rate” cannot tell a real service from a copy of it. A cloned endpoint copies the template, the docs, the address and the company number, then undercuts on price, which is precisely what makes it win an automated comparison.
The harm is not abstract. The copy returns a rate that is wrong by three percent, and the agent computes a payment from it. On a $10,000 transfer that is S$385, from a number nobody would blink at.
The obvious fix, having the agent look for a trust badge, fails immediately: a copy clones the badge too. It can clone the whole thing and display its victim's legal name while doing it.
An agent verifies the host it is actually on, never an identifier the page handed it.
A KYM identity is bound to a domain at the moment it is issued. Move it to another host and it stops verifying. Stolen credentials stop being useful the moment they travel.
Three moving parts, one of which nobody can skip.
Payment providers already run merchant checks. They just keep the results private, tie them to payment accounts rather than websites, and silo them per provider, so no agent can consult them. KYM makes the proof public, machine-readable and bound to a domain.
The merchant proves who it is, once
KYM establishes that the business is real and registered, and that the merchant genuinely controls the domain it trades on. What comes back is an identity tied to that domain and to nothing else.
Anyone can check it, for nothing
Checking is open to every agent, facilitator and marketplace, at no cost and no sign-up. It is built to be cheap enough to run on every single transaction, because a check people skip protects nobody.
The payment path refuses to pay strangers
The check sits in the settlement path, not in the agent's reasoning. A careless or prompt-injected agent cannot skip it, because it cannot move money without passing it.
KYM is deliberately rail-agnostic. It asks you to adopt no chain, no protocol and no payment provider, and it holds no opinion about how your buyers pay. A trust layer that works on only one rail is a feature of that rail, not a trust layer.
See it happen, from the buyer's side.
A short walkthrough of an AI agent shopping around, comparing prices and paying. For a merchant, the interesting part is what you never have to do: once your identity is verified, a buyer who has never heard of you can transact without a person stopping to ask who you are.
KYM - Agent Purchase Flow. Watch on YouTube
Unknown must never mean blocked.
A binary gate on a young registry blocks the honest majority and gets switched off within a week. KYM holds the money instead, and asks a human.
Settles instantly
Identity confirmed, still live, and bound to the host actually connected to. Money moves machine to machine, in seconds, with no human in the path.
Held for approval
No identity published. Funds are held rather than refused, and a person is asked to approve. The default is caution, not obstruction.
Refused, with a reason
Presented on the wrong domain, out of date, altered, or withdrawn since it was issued. The refusal says why, in a form software can act on.
Merchants pay for identity. Checking is free, forever.
That asymmetry is the product, not an oversight in the pricing. A gate that costs money to consult is a gate people route around, and a verification layer nobody consults protects nobody.
- Verification that the business is real and the domain is yours
- An identity bound to your domain, held by you
- Annual re-verification, and withdrawal the moment something changes
- A record of what was checked, and when
- Works with whatever rail your buyers arrive on
- Open to every agent, facilitator and marketplace
- Live status, so a withdrawn identity stops working immediately
- Drops into a checkout or settlement flow you already run
- No chain, protocol or provider to adopt
- No commercial terms attached, ever
Get an identity, or get early access to the gate.
We're onboarding a first cohort of merchants and integration partners. Tell us which you are and we'll come back to you with next steps. No obligation, no sales sequence.
You're on the list.
We'll be in touch at the address you gave us, usually within a working day. Nothing else is needed from you.