Everything you need to trust AI buyers.
The KYA platform is the verification layer between agent shoppers and your checkout. Six primitives resolve identity, bind and validate the operator's authorization, classify traffic, and record every decision — split across trace issuance upstream, the verify and checkout-session calls at your edge, and the pre-dispute side-channel.
Six named parts. They compose.
Each primitive is a stable contract in the verification API. You call them together at the checkout edge; you can reason about them independently.
Agent Identity
Every KYA agent carries a signed, revocable identity tied to a real business operator. POST /api/v1/verify resolves the agent to the operator behind it and returns a trust-score recommendation. The principal hash and spend scope ride on a signed trace the operator issues upstream, and are enforced when you open the checkout session.
Agent Wallet Auth
The operator issues a signed trace carrying scope, spending cap, audience, and principal hash. POST /api/v1/checkout/sessions validates that trace against a delegated wallet and fails the session with an explicit reason when the transaction falls outside scope — before a card is touched.
Transaction Guard
Policy evaluation splits across two calls at the checkout edge. POST /api/v1/verify returns an accept / review / decline recommendation from trust score, merchant verify rules, and the agent's configured transaction ceiling. POST /api/v1/checkout/sessions runs the trace-scope, wallet, audience, amount, and MCC checks before money moves.
Bot Classification
Not all automated traffic is the same. KYA separates verified agent buyers from scrapers, credential stuffers, and inventory hoarders — so your fraud stack only fights what it should.
Merchant Verification
Merchants sign the other side of the handshake too. An agent knows it is transacting with a real, KYC-verified merchant, and the merchant knows the counter-party is bound to policy.
Evidence Log
Verify decisions log to kya_verifications keyed by a verification id; checkout sessions log to kya_checkout_sessions keyed by trace id with the full policy-check record. Those records can be joined with the signed trace when a merchant or operator opens a pre-dispute case — no screenshots, no forensics.
Platform questions.
What is the KnowYourAgent platform?+
A verification layer that sits between AI shopping agents and merchant checkouts. Two calls do the work: /api/v1/verify resolves the agent's identity and returns a trust-score-driven recommendation; /api/v1/checkout/sessions validates the signed trace the operator issued upstream and enforces scope, spend cap, wallet, audience, and MCC. Verify decisions log to kya_verifications; checkout sessions log to kya_checkout_sessions keyed by trace id; those records can be referenced later if a pre-dispute workflow is opened.
How does KYA verify an agent's identity?+
Each registered agent receives a unique KYA ID tied to a verified business operator. /api/v1/verify resolves that ID to the operator and returns the trust-score recommendation inline with your authorization. The signed trace that carries the principal hash and spend scope is validated separately — when the merchant opens a checkout session against /api/v1/checkout/sessions.
What happens if an agent tries to exceed its spending cap?+
/api/v1/checkout/sessions fails the session with an explicit reason code when the transaction exceeds the trace's spend cap or falls outside scope — before the card is touched. The failed session is recorded against the trace id, so the merchant and operator have the exact failure record if they later need to open a pre-dispute case.