/ MERCHANTSFor checkout owners

Let the agent check out only inside the signed mandate.

/api/v1/verify returns identity and an accept / review / decline recommendation. /api/v1/checkout/sessions enforces the operator's signed trace — audience, scope, spend cap — and fails the session if the cart is out of bounds. Neither call moves the card.

Editorial still life of a dark paper packet with sparse marks for identity, audience, scope, and spend cap
/ Signed mandateAudience, scope, and spending limit ride on the operator’s trace.
How it works

Three checks at the checkout edge.

01

Verify the agent

POST /api/v1/verify with the KYA ID and transaction_context. You get identity, trust_score, and an accept / review / decline recommendation — not enforcement of the signed cap.

02

Enforce the signed trace

POST /api/v1/checkout/sessions with the trace_jwt and the cart. Orders outside audience, scope, or spend cap fail with an explicit reason code before the card is touched.

03

Keep the records with the order

Store the verification_id and checkout session against the order. If a dispute is opened later, the signed trace is already on the file.

/ 03Integrations

Shopify, REST, WooCommerce next.

KYA attaches to the checkout surface you already run.

Shopify

APP
Pilot Onboarding

Guided pilot onboarding is available now. Review setup, pricing, and rollout options while public install is being finalized.

Request a pilot

Custom API

REST
Available now

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 docs

WooCommerce

SOON
Planned

WooCommerce remains on the roadmap for a native plugin after the Shopify launch track stabilizes.

Request a pilot
/ 04FAQ

Merchant questions.

Does this affect human checkouts?

No. You call KYA on the agent path. Human sessions are unchanged. Neither /api/v1/verify nor /api/v1/checkout/sessions moves the card.

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 store the verification and checkout-session records.

Next step

Pick a design-partner slot or talk to a solutions engineer.

Request a pilot