Kite Goes Live: What Agent Payments on Avalanche Mean for Builders
Kite launched its mainnet on Avalanche this week. It’s a sovereign L1 that enables AI agents to pay for goods and services, prove their identity, and settle transactions in real time.
What Kite Actually Does
AI agents can browse the web, call APIs, and trigger workflows. But they stall at monetary transactions. Payment infrastructure assumes a person is approving charges, entering card numbers, and waiting for settlement. Agents operate at machine speed, and they need rails that keep up.
Kite provides three pieces. Kite Passport provides agents with a persistent cryptographic identity, enabling them to prove their identity and operate within defined permissions. Programmable delegation allows an agent to act on behalf of a user or organization within predefined boundaries. And stablecoin-based settlement happens in line with execution. No batch processing and no delays.
The testnet metrics add weight. Kite processed over 1.9 billion agent interactions before launch. Daily peaks hit 30 million calls. PayPal Ventures and General Catalyst led a $33 million raise. PayPal is piloting the infrastructure now, and Shopify integrations are in progress.
What Builders in the Avalanche Ecosystem Could Do With This
If you’re shipping on Avalanche, Kite opens up product categories that were previously difficult to build.
Picture a data marketplace where agents purchase datasets per query, paying fractions of a cent per call with zero human approval. Or an API service that charges AI customers programmatically and instantly, the same way it charges human ones. Developers building on Ava Cloud could create agent-facing services that combine access and payment into a single step.
Gaming studios could give in-game agents control over their own micro-economies: buying resources, trading items, and settling transactions continuously during gameplay. DeFi teams could build protocols where automated strategies pay for oracle data, execution services, or cross-chain bridging on every operation.
The pattern is the same across all of these. Wherever software needs to pay for access, Kite provides a way to do so on Avalanche with sub-second finality and predictable costs.
When Software Can Prove Who It Is
Kite Passport deserves a closer look.
Today, agents borrow their operator’s credentials. That creates a problem. A DeFi bot running a yield strategy shouldn’t need full access to its owners’ funds to pay for an oracle call. A gaming agent managing in-game trades shouldn’t share keys with the player who deployed it.
Kite Passport separates the agent from its owner. Each agent gets a verifiable, cryptographic identity and scoped permissions. It can authenticate with services and transact within limits set by someone else. The agent acts. The owner stays in control.
For builders, this changes what you can design. You can create services that verify an agent’s identity before granting access, set spending caps per session, or revoke permissions instantly. Products built this way treat agents as accountable participants rather than anonymous scripts firing requests.
On Avalanche, where sub-second finality and low fees already support high-frequency activity, adding identity and scoped authority to that speed makes agent-facing products viable in a way they weren’t just six months ago.
Explore Kite’s mainnet and documentation to start building.