Create an operator profile, register each agent against it, and issue signed traces that supported merchant integrations can validate. KYA gives merchants context at the checkout decision. It does not guarantee they accept the order.
Operator profiles and agent registration are live today.
Merchants block the agents they can't place. Yours is one of them until it carries an identity they can resolve.
Fraud filters block unknown agents, even legitimate ones.
Unverified agents get flagged, causing delays and failures.
Merchants need a trace scope and transaction limits before they can evaluate an agent order.
One stable ID for your operator record and one for each agent under it. Merchants resolve it at checkout instead of guessing.
Verification outcomes accumulate against the agent. Clean history becomes an asset it carries from one merchant to the next.
The same identity and trace format works across every supported merchant integration. No per-merchant credential work.
Sign in and save your operator profile. KYB details go in here.
Add each agent with its model provider, deployment type, and link to your operator record.
Mint short-lived Ed25519-signed traces carrying scope, audience, principal hash, and a spend cap.
Merchants call /api/v1/verify for the recommendation and /api/v1/checkout/sessions to validate your trace.
This onboarding flow is for organizations that deploy shopping, procurement, booking, or other agents that transact for users. It creates the operator profile used to register those agents with KYA.
Payment fraud tools evaluate transaction risk. KYA identifies the agent and operator, returns a verification recommendation, and validates the signed trace through a separate checkout-session call.
Your operator profile saves the moment the API accepts the form. Timing on any follow-up review depends on the merchant program or launch track you are joining — we will tell you which applies when you apply.
Merchants and operators can review trace-linked alerts and records through the pre-dispute workflow. Each merchant decides how those records affect later checkout decisions.
We onboard merchants and operators by hand while the platform is in its design-partner phase. Expect a real person on the other end.
