--- title: Know Your Human (KYH) for Agentic Commerce | Sardine source_page: https://www.sardine.ai/know-your-human canonical: https://www.sardine.ai/know-your-human format: text/markdown description: Shopping agents get declined because they look like bots. Sardine’s Know Your Human (KYH) protocol binds human identity to shopping agents so merchants can approve legitimate agent purchases. --- **Quick links:** [Human page](https://www.sardine.ai/know-your-human) · [Home](https://www.sardine.ai) · [Customers](https://www.sardine.ai/customers) · [Blog](https://www.sardine.ai/blog) · [Demo](https://www.sardine.ai/demo) --- # Know Your Human (KYH) for Agentic Commerce | Sardine Shopping agents get declined because they look like bots. Sardine’s Know Your Human (KYH) protocol binds human identity to shopping agents so merchants can approve legitimate agent purchases. ## Higher conversions for merchants and shopping agents Personal shopping agents have poor conversion rates because they appear as bots and are declined by merchants. Know Your Human (KYH) binds a human’s real identity to their agent. ## See KYH in action ## Merchants win more 
disputes with KYH Shopping agents hide their human’s device and IP signals, leaving merchants without key evidence for disputes. KYH binds the agent to a human for a stronger dispute response. ## Verify the human behind an agentic purchase When an agent places an order, the customer receives a secure verification link via SMS. Opening the link in their browser allows Sardine to capture device and behavior signals that binds the agent to the human behind the purchase. ## How agents connect each purchase to a real customer The agent connects the customer’s device to its session using Sardine’s SDK or a merchant-provided Method URL. At checkout, it passes the session details to the merchant, who uses Sardine to retrieve the customer’s device and IP signals, verify the human behind the purchase, and approve the order. ## Approve more purchases from shopping agents See how Sardine’s KYH helps you connect agents to 
the human behind the purchase. ## Frequently asked questions ### Why does bot detection block agent purchases? A legitimate shopping agent may use the same cloud infrastructure and browser automation as an abusive bot. Without the customer’s device and IP, the merchant has fewer signals to distinguish them. ### Which customer signals does KYH provide? Agent-KYH-Provider and Agent-Context-Key identify the provider and session used to retrieve the customer’s device fingerprint and IP. The request also includes a forwarded IP and an agent signature. The proposal describes possible extensions to email, phone, KYC, and identity verification data. ### How can device data support a dispute response? A customer may not recognize a purchase made by their agent. Device and IP records can help the merchant associate the order with that customer. Programs such as Visa Compelling Evidence 3.0 and Mastercard First-Party Trust have their own eligibility and evidence requirements; collecting a signal alone does not guarantee a successful dispute response. ### Does KYH replace other protocols? No. KYH supplies customer identity signals for a risk decision. Sardine proposes it as an addition to other agentic commerce protocols. ## Featured resources

curl -X POST https://api.sandbox.sardine.ai/v1/identity/kyh/widget \
  -u "$SARDINE_CLIENT_ID:$SARDINE_CLIENT_SECRET" \
  -H "Content-Type: application/json" \
  -d '{
    "sessionKey": "898cfa13-7ec6-48e2-85da-dd5882dc4ac4",
    "code": "482913"
  }'

{
  "widgetUrl": "https://identity.sandbox.sardine.ai/kyh?token=...",
  "expiresAt": "2026-11-03T14:05:00Z"
}

<script src="[Sardine Device Intelligence JS]"></script>

# session binding (illustrative)
sessionKey = "session_key_060f69410f3b7a47b899cbc09da01a93a44cdb52b78ea3ca679dad6928782e55"

POST /method HTTP/1.1
Host: device.lastminutetickets.example
Content-Type: application/x-www-form-urlencoded

MethodData=eyJTZXJ2ZXJUcmFuc0lEIjoic2Vzc2lvbl9rZXlfMDYwZjY5NDEwZjNiN2E0N2I4OTljYmMwOWRhMDFhOTNhNDRjZGI1MmI3OGVhM2NhNjc5ZGFkNjkyODc4MmU1NSIsIk1ldGhvZE5vdGlmaWNhdGlvblVSTCI6Imh0dHBzOi8vYXRsYXMtYWdlbnQuZXhhbXBsZS9reWgvbm90aWZ5In0

# MethodData decodes to:
{
  "ServerTransID": "session_key_060f69410f3b7a47b899cbc09da01a93a44cdb52b78ea3ca679dad6928782e55",
  "MethodNotificationURL": "https://atlas-agent.example/kyh/notify"
}