We organize around what merchants and developers actually have to ship: verification primitives, the risk problems they solve, and the merchant revenue they protect.
Agent Identity, Wallet Auth, Transaction Guard, Bot Classification, Merchant Verification, and the Evidence Log. Each is a stable contract in the API. Adopt one, or all six, without touching your processor or gateway.
See the platformA side-channel for agent transactions: signed-trace evidence travels with every alert, and response clocks plus automation rules help teams resolve issues before chargebacks. The post-action layer that identity and edge-enforcement stacks do not cover.
See the Pre-Dispute NetworkVerified agents check out without getting flagged. When something does go wrong, the Pre-Dispute Network surfaces it merchant-to-operator first, so resolution happens before the card network sees a chargeback.
For merchantsAI agents don't have credit histories. They don't match your velocity models. They look like bots to your WAF and like humans to your checkout. 3-D Secure fails them. Your chargeback policy can't locate them. Your evidence log has no row for them.
KnowYourAgent issues verifiable identity at the agent layer: cryptographic AID, a signed trace carrying the principal hash and spend scope, policy-bound transaction controls, and the Pre-Dispute Network that intercepts issues before chargebacks fire. None of it assumes a human is holding the phone.
“Agentic commerce is transforming the digital shopping experience. This shift will rival the impact that online shopping and mobile devices have had on commerce.”
“Sparky will be the primary digital vehicle for discovery, shopping, and managing everything from reorders to returns.”
An AI shopping agent is autonomous software that browses, compares, and buys on behalf of a human customer. These agents are arriving at merchant checkouts today, and most fraud tools flag them as suspicious because they don't behave like human buyers — costing merchants legitimate revenue.
Two calls at the checkout edge. The merchant calls /api/v1/verify with the agent's KYA ID and transaction context; KYA resolves the identity, the operator behind it, and the current trust level, and returns an accept / review / decline recommendation with reasons. Separately, the merchant opens /api/v1/checkout/sessions with the signed trace the operator issued upstream — that call validates the trace against a delegated wallet and enforces scope, spend cap, audience, and MCC before the card is touched.
The KYA Pre-Dispute Network runs as a side-channel between merchants and operators so problems surface before they escalate to chargebacks. If an agent exceeds its authorized scope or a customer disputes a purchase, an alert is opened against the X-KYA-Trace-ID with the signed trace, verification record, and checkout-session record attached. Merchant rules can auto-resolve matching alerts; operators can respond before escalation.
Merchant onboarding is being packaged for a guided Shopify rollout, and custom API integrations fit alongside your existing checkout logic. Merchants start with /api/v1/verify for identity and recommendation, and add /api/v1/checkout/sessions when they want signed-trace enforcement at checkout. In both cases, KYA sits alongside your existing payment and fraud stack rather than replacing it.
Merchant onboarding currently starts with a guided pilot package, with launch pricing previewed on the pricing page. Operator pricing is separate and remains available for teams registering and managing agent fleets.
No. KYA runs as a parallel verification call alongside your existing payment processing and only activates when an AI agent is detected. Human customers see no change to the checkout flow.