ShopifyAPP
Pilot Onboarding
Guided pilot onboarding is available now. Review setup, pricing, and rollout options while public install is being finalized.
Request pilot access/ MERCHANTSFor payments & fraud leaders
Let verified agents check out. Block the rest.
KnowYourAgent sits at your checkout edge. /api/v1/verify resolves the agent to its operator and returns a trust-score recommendation; /api/v1/checkout/sessions validates the signed trace the operator issued — principal hash, spend scope, delegated wallet — and fails the session if the order is out of bounds. Verification and checkout-session records stay queryable by ID, and those records can be pulled into a pre-dispute case when one is opened.
/ 01Outcomes
Six outcomes merchants ship with KnowYourAgent.
Each outcome maps to a primitive on the platform. We deliberately don't quote percentage lifts we can't prove — the metrics here are the ones you will measure after rollout.
/ OUT-01
Cleaner approvals
Separate legitimate agent traffic from suspicious automation before payment. Stop letting your fraud stack false-positive good agent orders.
/ OUT-02
Fewer manual reviews
Your ops team stops triaging "is this a bot?" — identity, operator, and policy context arrive at the checkout decision with the order.
/ OUT-03
Higher-confidence limits
Approve larger agent orders when the transaction fits the policy you configured. Caps and MCC allow-lists enforced at the edge.
/ OUT-04
Pre-Dispute Network recourse
Open an alert against the X-KYA-Trace-ID with the signed trace and checkout-session record attached. The alert carries a response deadline, with a shorter clock for stop-loss cases.
/ OUT-05
Cross-channel consistency
One agent-identity layer whether the checkout is web, API, or an in-session assistant. One verification record and checkout-session trail across channels.
/ OUT-06
Audit-ready evidence
Every trace-enforced checkout session produces a signed evidence record; verify decisions log alongside. When finance, legal, or a card network asks for proof, the signed trace plus the pre-dispute record are already on file.
/ 02How it works
Four checks at the checkout edge.
/api/v1/verify returns a trust-score recommendation in-band with your authorization; /api/v1/checkout/sessions validates the signed trace the operator issued upstream and enforces scope, wallet, and amount. Verification and checkout records remain available if a merchant or operator later opens a pre-dispute case.
01
Agent presents AID
The incoming agent surfaces its KnowYourAgent Identity at checkout. /api/v1/verify resolves the ID, returns a trust-score recommendation, and pulls the reputation graph.
02
Wallet Auth resolves
The signed trace carries the principal hash and the authorization scope the operator issued upstream. /api/v1/checkout/sessions validates it against a delegated wallet; orders outside scope, spend cap, audience, or MCC are declined with an explicit reason code.
03
Transaction Guard enforces
Policy-bound limits apply at the checkout-session call: trace amount limits, delegated-wallet limits, daily and monthly ceilings, and MCC allow-lists. You set the ruleset; we enforce it at the edge.
04
Evidence record persists
Verification and checkout-session records keep the decision, trace, and policy-check trail together. If a dispute is raised, the signed trace and merchant response can be attached to a pre-dispute case.
/ 03Integrations
Meet your stack where it lives.
No rip-and-replace. KYA plugs into the checkout surface you already run — starting with Shopify and an HTTP API you can wire into anything else.
Custom APIREST
Available now
Drop KYA into any commerce stack. Call /api/v1/verify for identity and recommendation, and /api/v1/checkout/sessions when you want signed-trace enforcement at checkout. Typed SDKs are on the roadmap; the REST surface and the @knowyouragent/cli ship today.
Read the docsWooCommerceSOON
Planned
WooCommerce remains on the roadmap for a native plugin after the Shopify launch track stabilizes.
Request integration/ 04FAQ
Merchant questions.
Does this affect human checkouts?+
No. KYA activates only when agent signals are present. Your existing human checkout experience is unchanged.
How long does merchant setup take?+
The Shopify path is handled as guided onboarding. Custom-API merchants integrate KYA alongside their current checkout logic with /api/v1/verify for identity and recommendation, and /api/v1/checkout/sessions when signed-trace enforcement is in scope.
What if we are not on Shopify?+
Start with the verification API today and work with the KYA team on a custom integration path. WooCommerce is planned as the next native plugin.
What data does KYA access?+
Only the checkout and order context required to verify agent identity, apply your merchant policy, and report outcomes back into the trust network.