KITE AI (@GoKiteAI): . @a16zcrypto recently laid out a clear framework for AI trends in 2026:
Estimated coin impact
Scores are not price-change percentages. High impact means a score of +70 or more, or -70 or less.
Impact unavailable
. @a16zcrypto recently laid out a clear framework for AI trends in 2026: 1️⃣ Research oriented agents will move into more substantive workflows 2️⃣ Trust and identity will replace raw intelligence as the primary bottleneck 3️⃣ The open web will need to shift from static licensing to real time, usage based value return Among these, the most underestimated yet most decisive shift is from KYC to KYA. Why KYA becomes a visible trend this year is straightforward. As a16z puts it: "Just as humans need credit scores to get loans, agents will need cryptographically signed credentials to transact — linking the agent to its principal, its constraints, and its liability. Until this exists, merchants will keep blocking agents at the firewall." Kite is converging the identity and constraint capabilities required for KYA with the internet native billing path represented by x402 into composable primitives. On the product side, we have defined AI Passport identity and signing, along with agent oriented delegation and constraint expression, so identity can move across services and policies can be verified and enforced. On the settlement side, we have deployed a general purpose x402 facilitator on testnet, pushing per call stablecoin payments toward becoming a default interface for agents calling services. We also recently joined the Agentic AI Foundation to help advance open standards and interoperable infrastructure for production grade agents. Next, Kite will focus on three priorities to make KYA real in practice: 1️⃣ Standardize and simplify agent authentication and credential integration, so merchants and developers can use a unified approach to identify, authorize, and attribute responsibility 2️⃣ Make constraints verifiable and auditable at execution time, so permission boundaries are enforced within the call path rather than patched after the fact 3️⃣ Bind x402 style per call settlement and receipt mechanisms more tightly into the agent call flow, closing the loop across identity, constraints, and settlement on a single rail Kite’s view is that KYA is likely to become one of the key thresholds for agents to operate in production. Our goal is not to create another entry point, but to push identity, constraints, and settlement down to the protocol layer as default composable primitives, so every agent call can naturally carry verifiable permission boundaries, accountable responsibility, and native value flow.