Skip to main content

Kite AI Becomes First Crypto L1 Inside Google's Agent Payments Protocol

· 13 min read
Dora Noda
Dora Noda
Software Engineer

A Layer 1 blockchain designed entirely for software that never sleeps just earned a seat at Google's table. On February 25, 2026, Kite AI — an EVM-compatible chain purpose-built for autonomous agents — announced it had joined Google's Agent Payments Protocol (AP2) as a Community Partner. It is the first crypto-native chain to land inside Google's AI commerce network, and the implications reach far beyond a single partnership logo.

Kite's entry marks a quiet but consequential shift. For two years, the "AI × crypto" narrative has oscillated between Bittensor-style inference marketplaces, token-gated chatbots, and wallet SDKs bolted onto general-purpose chains. Kite is a different species: an L1 where agent identity, session-scoped spending, and sub-cent micropayments are native protocol primitives rather than bolt-on standards. Now that architecture is being plugged directly into the distribution channel that Big Tech built for the agentic web — which raises a question the industry has been dancing around: does decentralization matter more, or less, when the front door is Google?

What Kite Actually Is (And Why It Is Not Another "AI Chain")​

Kite — formerly Zettablock — is an EVM-compatible Proof-of-Stake Layer 1 that launched its mainnet in Q1 2026 as a sovereign chain on Avalanche's subnet architecture. The company has raised $33 million in cumulative funding, with its $18M Series A led by PayPal Ventures and General Catalyst in September 2025, later extended by Coinbase Ventures. The cap table reads like a roadmap: 8VC, Samsung Next, Avalanche Foundation, LayerZero, Hashed, HashKey Capital, Animoca Brands, GSR Markets, and Alchemy all sit alongside the payments giants.

What separates Kite from the dozens of "general-purpose chain with AI features" pitches is that its design decisions are unusable for anything else:

  • Three-layer identity via BIP-32 derivation. Every entity in Kite's world exists as a hierarchical key: a user identity (the human or organization that deploys the agent), an agent identity (a verifiable on-chain DID for the autonomous software itself), and session identity (ephemeral keys scoped to a single task or time window). This is the same derivation tree that Bitcoin hardware wallets use to produce child addresses — repurposed so a rogue session key cannot drain a treasury, only blow a task budget.
  • State-channel payments at sub-100ms latency. Kite's documented transaction cost sits around $0.000001 per payment. That is roughly three orders of magnitude below Solana and five below Base. General-purpose chains cannot reach that floor because their fee markets are designed for human-scale throughput, not for agents that might emit a thousand API calls per second.
  • Programmable policy at the account layer. Unified smart contract accounts let a deploying user set spending caps, whitelists, rate limits, and expiry windows before an agent touches mainnet — the equivalent of a corporate card with per-merchant, per-minute, and per-session limits baked into consensus.

On top of that base, Kite AIR (Agent Identity Resolution) adds two consumer-facing primitives: Agent Passport, a verifiable identity with operational guardrails and a funded wallet, and Agent App Store, a marketplace where service providers list APIs, data feeds, and commerce tools that agents can discover and pay for without a human in the loop. The Passport + App Store pair is the part that is already live on Shopify and PayPal, making merchant catalogs discoverable to AI shopping agents with settlement in stablecoins.

Google's AP2 Is the Distribution Layer Crypto Has Been Missing​

To understand why a Community Partner slot in AP2 matters, it helps to look at what Google actually built. Agent Payments Protocol is an open specification launched in September 2025 with over 60 organizations — including Coinbase, Ethereum Foundation, MetaMask, Polygon, Lowe's Innovation Labs, ServiceNow, Salesforce, PwC, 1Password, Shopee, and Worldpay — and it solves the hardest problem in agent commerce: how a merchant can trust that the agent at its door has actual authority to spend on a human's behalf.

AP2's core construct is the Verifiable Credential mandate: a cryptographically signed intent from a user that authorizes a specific agent to perform a specific purchase within specific parameters. The merchant verifies the mandate before releasing goods. This is the identity and policy scaffolding that traditional card networks spent decades building — except Google is giving it away as an open standard.

The crypto-native leg of AP2 is the A2A x402 extension, co-developed with Coinbase, MetaMask, the Ethereum Foundation, and Polygon. It lets agents settle AP2 mandates in stablecoins over any x402-compatible chain, bypassing card rails entirely when both sides prefer it. Coinbase's x402 rail handles the always-on programmable settlement; Google handles identity, policy, and compliance.

That architecture is where Kite fits. AP2 does not care which chain settles the payment — it cares that the mandate is honored. Kite's EVM compatibility and native x402 support make it a first-class settlement venue inside the protocol. And because Kite's identity layer is already structured around user → agent → session hierarchy, mapping an AP2 Verifiable Credential mandate onto a Kite session key is close to mechanical.

The result: a developer building on AP2 who wants sub-cent latency, per-session spending caps enforced at the protocol layer, and an agent-native marketplace for service discovery now has one obvious place to send traffic.

The Market Math: $420B in Stablecoins, $28K in Agent Revenue​

Before anyone declares victory, the reality check is useful. Coinbase reported in March 2026 that x402 processes roughly $28,000 in daily volume across its ecosystem, much of it testing traffic rather than real commerce. Solana's x402 implementation has seen 35 million+ transactions and $10M+ cumulative volume since its summer 2025 launch — real usage, but still a rounding error against the stablecoin base it runs on.

That base, meanwhile, is enormous and growing:

  • Stablecoin transaction volume hit $33 trillion in 2025, up 72% year-over-year.
  • Circulating supply surpassed $300 billion and is projected to reach $420 billion by end of 2026.
  • Galaxy Research estimates agentic commerce could represent $3–5 trillion in B2C revenue by 2030.

The gap between "$28K daily" and "$3–5T by 2030" is the investment thesis every AP2 participant is underwriting. The argument is that agent commerce is a J-curve: negligible real usage while the protocol layer gets built, then a step-function inflection when the identity, payment, and discovery primitives align and a critical mass of merchants list in agent-readable formats. Kite is betting it is the chain that captures the inflection — and PayPal, Coinbase, and Google's endorsements suggest they are hedging the same bet from three different directions.

Agent Infrastructure Is Vertical-Specializing — Fast​

Kite + AP2 is not happening in a vacuum. The 2026 landscape shows an unmistakable pattern: general-purpose chains are losing ground to purpose-built L1s in specific verticals, and agent commerce is only one front.

  • Tempo is an ISO 20022-native L1 targeting institutional payment settlement, with validator compensation denominated in stablecoins and BFT finality tuned for regulatory finality rather than DeFi throughput. DoorDash's April 2026 stablecoin payout pilot uses Tempo rails, and Stripe and Paradigm are among its backers.
  • Pharos Network positions itself as the commercial finance and RWA chain, embedding KYC at the protocol layer to serve tokenized securities and institutional credit.
  • Fogo targets institutional DeFi with native MEV mitigation.
  • Kite owns the AI-agent vertical: identity, session keys, micropayments, and an agent-native app store.

Each of these chains makes the same bet — that compliance, payment semantics, or agent identity are architecturally incompatible with general-purpose consensus and must be re-specified from the bottom up. The 2026 validation is that TradFi is voting with its wallet: BVNK's $1.8B Mastercard acquisition, Klarna's Tempo integration, and Kite's AP2 slot are three different flavors of the same signal.

This is the opposite of the 2021 narrative, when every protocol fought for "EVM compatibility" as the universal dock. The 2026 narrative is that EVM compatibility is necessary but no longer sufficient — the chain's consensus-layer priors now have to match the workload.

Four Architectural Models for Agent-Blockchain Integration​

Zoom out and Kite's approach is one of four visible strategies for how AI agents meet on-chain execution. Each makes different trust and distribution tradeoffs:

  1. Agent-native L1 (Kite). The chain is rebuilt around agent identity, session keys, and micropayments. Maximum design cleanliness; requires bootstrapping an ecosystem.
  2. Exchange-centric wallet service (Coinbase Agentic Wallet, OKX OnchainOS). An agent talks to a wallet API that speaks x402 and settles on existing chains. Fastest distribution via exchange user base; custodial tradeoffs.
  3. Embedded SDK (Privy Agent CLI, Coinbase AgentKit). Developers drop agent wallets into their code as libraries. Maximum developer autonomy; security posture depends on the integrating team.
  4. Big Tech commerce protocol (Google AP2, Visa Intelligent Commerce). The identity, mandate, and discovery layer lives inside a traditional tech or payments giant, and any chain can plug in underneath. Maximum reach; decentralization tradeoff sits at the top of the stack.

What is notable about Kite's AP2 announcement is that Kite is doing strategy #1 and strategy #4 simultaneously — building a sovereign agent L1 and accepting that discovery and policy primitives live inside Google's network. That is not incoherent. It acknowledges a structural reality of the agentic web: the chain is not the bottleneck to adoption, the protocol that merchants agree to speak is. If AP2 becomes the de facto standard for agent commerce the way HTTPS became the standard for the web, a settlement chain that speaks AP2 natively starts with a tailwind no marketing budget can buy.

The Decentralization Question Nobody Wants to Ask​

The awkward subtext of a crypto L1 joining a Google-led protocol: if Google's AP2 becomes the default identity and mandate layer for agent commerce, how much does it matter that the settlement happens on-chain? An agent that holds a Google-issued Verifiable Credential mandate, discovers a service through a Google-indexed registry, and settles in stablecoins on a PayPal- and Coinbase-backed chain is running a workflow where every layer above consensus is gated by Big Tech.

There are two honest answers. The pessimistic read is that this is re-intermediation with extra steps — crypto giving up the distribution fight and becoming settlement plumbing for AI commerce that Google ultimately controls. The optimistic read is that open protocols win on integration surface area, and AP2 is open enough (open spec, multiple stablecoin facilitators, any compatible chain can settle) that it behaves more like TCP/IP than like the iOS App Store.

Which read is right will depend on whether AP2's governance stays genuinely multi-stakeholder or drifts toward Google-dominant control, and whether alternative mandate standards (likely emerging from Anthropic, OpenAI, or a neutral foundation) take hold for agents that do not want to route through a single hyperscaler. The 60+ partner list and the explicit collaboration with Ethereum Foundation and MetaMask suggests Google learned from the Android-vs-open-Linux playbook and is deliberately avoiding single-vendor capture. Time will tell whether that holds under commercial pressure.

What This Means for Builders Right Now​

If you are building in the agent stack in 2026, Kite joining AP2 clarifies a few decisions:

  • Payment rail selection. If your agent needs sub-cent transactions and tight session spending limits, Kite is now a plausible default. For larger enterprise settlements, x402 on Base or Ethereum remains the lower-risk choice. The right answer is often "both" — settlement chain by workload type.
  • Identity posture. Designing an agent that can present an AP2 Verifiable Credential mandate is increasingly non-optional. Merchants integrating with AP2 will assume any agent that shows up can produce one; agents that cannot will be filtered out of the discovery layer.
  • Protocol bets. AP2 and x402 are not mutually exclusive, and Google's A2A x402 extension explicitly couples them. Treating them as a stack (AP2 for identity/mandate, x402 for settlement transport) is the simplest mental model.

The Bigger Picture​

The Kite–AP2 announcement is small in isolation: one chain, one community partner slot, one press release. Its weight comes from what it confirms. In 2026, the question for agent infrastructure is no longer "will AI agents hold crypto?" — they already do, at 250,000+ daily active addresses across Ethereum, Solana, and BNB Chain. The question is which rails survive the transition from novelty to default.

A chain that gets picked by Google's commerce protocol, pre-integrated with Shopify and PayPal, funded by the operators of two of the three largest stablecoin ecosystems, and designed from consensus up for session-scoped spending starts that race with more structural advantages than any general-purpose L1 can manufacture retroactively. Whether Kite converts that position into durable settlement share — or gets absorbed into a multi-chain AP2 mesh where the specific chain matters less than the mandate format — is the story 2026 and 2027 will tell.

What is already clear: the chain-level abstraction for agent commerce is no longer "deploy on Ethereum and figure it out." It is a vertical-specialized stack with AP2 at the identity layer, x402 at the transport layer, and purpose-built L1s competing at the settlement layer. Kite just made itself the most visible example of the last one.

BlockEden.xyz provides enterprise-grade RPC and indexing infrastructure for AI agents and the chains they transact on — including EVM networks, Solana, Sui, Aptos, and the purpose-built L1s now emerging for agent commerce. Explore our API marketplace to build on rails designed for autonomous, high-frequency workloads.

Sources​

Share on Twitter