Agent request
Product or label reference
MVP for autonomous agent commerce
Don’t let an agent buy what it cannot verify. KYA checks the available evidence for a physical product before an autonomous agent decides to buy.
Agent request
Product or label reference
KYA evidence check
Registry + physical path + optional chain
Machine-readable result
Status + reasons + evidence links
One simple question
The MVP proves the request, evidence check and machine-readable response. Autonomous checkout and delivery matching are intentionally outside this page.
A marketplace or catalog provides a product or label reference.
The verification API receives the reference and caller context.
Registry status, physical-evidence path and optional chain reference.
The agent receives a machine-readable result with reasons and links.
Two sides. One trust network.
Manufacturers make products trust-ready. Autonomous agents verify the offer before purchase and match the delivered physical item to the order afterwards.
A simple guided platform for manufacturers and product partners.
A trust interface for marketplaces, buyers and autonomous agents.
The new shadow module will normalize MetaAnchor, GS1, secure NFC and supporting chain evidence into one policy-bound result. The current live MVP remains authoritative while the kernel is built and compared.
KYA Trust Ladder
Every level requires a stronger, independently verifiable event. Volume alone cannot buy or manufacture trust.
Only verified order lines, fresh possession proofs and structured outcomes can influence trust.
Product, issuer, seller, buyer, service partner, agent and evidence provider are evaluated separately.
Identity in. Trust out.
KYA keeps identity, delegated authority and reputation separate — then returns a minimized, purpose-bound signal to the platform that needs it.
Enterprise and open-agent identities establish who acts, for whom and with which delegated role.
Signed receipts can be consumed by marketplaces, gateways and policy engines without exposing private order data.
Live evidence engine
Explore the current registry and chain checks, or open the genuine MetaAnchor physical-scan path. The long-term Trust Network is documented separately on the Vision page.
Agent asks: “Do I know this asset?”
Scan a genuine hologram.
MetaAnchor uses your smartphone camera to capture the physical Holographic Fingerprint from multiple angles. This is the real physical-authentication path.
The signed Campaign return now points to KYA. NFT mint and transfer remain disabled until a separate controlled activation.
MVP substance
The current MVP combines its own registry with a real physical-scan path and optional public chain evidence. Each result remains explicitly limited to what was checked.
KYA resolves whether a product reference is active, revoked, unknown or still pending.
Campaign callback, strict SIPv4 verifier, Polygon contract and 500 anchor mappings are configured. Fresh scan confirmation is pending.
Polygon and ApeChain references resolve public ownerOf state. This is technical evidence — not legal ownership or physical authenticity.
Completed reference projects
DRiM/Gin and WomanUp prove that customers paid for physical activation. They remain completed one-shot references, not recurring platform revenue.
This completed project linked 5,000 hologram boxes to ApeChain around the 2,222-litre Guinness World Record event in Paris. Box #4336 remains the live KYA reference.
The completed project equipped all 10 works in the artist collection with physical hologram labels — a collection-level proof for art provenance and phygital ownership.
View WomanUp on OpenSea ↗The ERC-6956 duck is the controlled technical test environment used to validate ownerOf resolution, RPC failover and KYA decision logic.
Agent Identity Gateway
Identity, signed mandates, open registries and agent networks can reach the same evidence check. Each route keeps its own trust boundary and maturity status.
Marketplace discovery, standardized jobs and future payments.
Microsoft-validated OAuth tokens and the KYA.Agent.Verify role.
Base Sepolia registry confirmed; KYA registration is ready.
A2A reaches KYA; AP2 can carry signed user intent and purchase authority.
Workload identity and delegated tool access require an approved AWS integration.
Agent wallets and USDC settlement; Arc settles value but does not prove identity.
Enterprise agent route through customer credentials and delegated access.
Enterprise procurement agents can use SAP identity and tenant trust.
Agent and token infrastructure; no KYA identity claim until a verifiable standard is selected.
Checkout and feed interoperability; the commerce session does not independently prove agent identity.
Normalize identity, authorize access and forward one standard request.
The caller route does not change the registry, physical-evidence or optional chain checks.
Singapore pilot offer
Connect one real product flow and measure whether humans and AI agents can verify the exact physical item before purchase, delivery or resale.
MVP design partner
We are looking for a manufacturer, marketplace or agent platform to test one clear flow: an autonomous agent asks KYA for product evidence before buying.