Kite kite
What is Kite?
Kite (Kite AI) is an agent-first payments and coordination network built around Kite Chain, a Proof-of-Stake, EVM-compatible Layer-1. Its stated goal is to let autonomous AI agents transact, coordinate, and operate as first-class economic actors rather than forcing them through human-oriented credentials and payment rails. The official site describes a three-part platform: an Agent Interface and Experience layer for workflows and integrations, Kite Passport for identity and authority controls, and Kite Chain for settlement.
Kite Chain is presented as the settlement layer for stablecoin-native, low-cost, real-time agent payments. The official network documentation identifies KiteAI Mainnet (chain ID 2366), KITE as its native token, an RPC endpoint, and Kitescan as the explorer. Mainnet is live according to the project homepage and the project's official X account.
The platform also includes an Agent Passport identity system. The whitepaper proposes separate user, agent, and ephemeral session identities, with delegation and permissions enforced cryptographically. This is intended to let users give agents narrowly scoped authority while retaining self-custody and the ability to revoke access.
Kite positions itself as compatible with agent and payment standards including x402, Google A2A/AP2, Anthropic MCP, OAuth 2.1, and Stripe MPP. Its public GitHub organization provides the Kite Chain repository, developer documentation, sample dApps, and agent-coordination projects.
What problem does Kite solve?
Kite targets a mismatch between autonomous-agent behavior and existing human-centric infrastructure. Agents may need to execute many small, machine-to-machine payments and service calls, while conventional cards, bank transfers, and API credentials impose fixed fees, settlement delays, broad permissions, and fragmented credential management. Those constraints make pay-per-request agent commerce difficult and increase the blast radius of a compromised key.
The project also identifies a trust and governance gap: a service may not be able to prove which principal authorized an agent, whether a request stays within a cumulative spending limit, or what happened across a multi-agent workflow. Kite's proposed answer is programmable governance, hierarchical delegation, immutable auditability, and agent-native settlement rather than relying on an agent's software to honor unenforced policy.
How does Kite work?
Kite's architecture combines the Kite Chain settlement layer, Kite Passport/core agent services, and agent-facing interfaces. The chain is EVM-compatible and uses PoS consensus; the official docs identify KITE as the native asset and stablecoins such as bridged USDC.e and USDT as payment assets on mainnet. The homepage describes deterministic finality, low fees, dedicated agent payment lanes, and native cross-chain messaging as chain capabilities.
Passport is intended to establish a chain of authority from a user to an agent to a short-lived session. The whitepaper describes BIP-32-derived agent addresses, random task/session keys, parent-agent signatures, scoped permissions, and revocation. Users can set budgets, limits, time windows, providers, and other constraints; the system is designed to verify those conditions before funds move and to leave an audit trail.
For high-frequency interactions, the whitepaper proposes programmable micropayment/state-channel flows: on-chain opening and closing with many off-chain signed updates, reducing per-request overhead. Kite's interoperability layer is designed to carry standard payment intents and agent messages, with x402 and AP2 used for payment expression and Kite Chain used for execution and settlement.
KITE has both network and ecosystem roles. Official tokenomics documentation states a capped 10 billion supply, with allocations of 48% ecosystem/community, 12% investors, 20% modules, and 20% team/advisors/early contributors. Documented utilities include module liquidity requirements, ecosystem eligibility and incentives, staking, governance, and a planned commission mechanism tied to AI-service transactions.
Key facts
- Native token: KITE; KiteAI Mainnet chain ID 2366; testnet chain ID 2368.
- Kite is a PoS, EVM-compatible Layer-1 focused on agentic payments and coordination.
- Mainnet RPC: https://rpc.gokite.ai/; explorer: https://kitescan.ai/.
- Official tokenomics documents cap total KITE supply at 10 billion.
- Stated allocation: 48% ecosystem/community, 12% investors, 20% modules, 20% team/advisors/early contributors.
- Official docs list native staking-manager and staking-vault contracts on Kite Mainnet.
- External-chain KITE deployments are documented on Ethereum, BSC, and Avalanche C-Chain at the same address: 0x904567252D8F48555b7447c67dCA23F0372E16be.
- Kite's stated standards integrations include x402, A2A, AP2, MCP, OAuth 2.1, and Stripe MPP.
- The official GitHub organization lists gokite-chain, developer-docs, sample dApps, and agent-coordination repositories.
Official links
Categories
Related coins
Compare
Frequently asked questions
What is KITE used for?
Official documentation describes KITE utilities including module liquidity, ecosystem access eligibility, ecosystem incentives, PoS staking, validator/delegator participation, and governance. A later phase is described for commissions associated with AI-service transactions.
What network does KITE run on?
Kite's native asset runs on KiteAI Mainnet, a PoS EVM-compatible Layer-1 with chain ID 2366. The project also documents KITE token deployments on Ethereum, BNB Smart Chain, and Avalanche C-Chain.
How can I verify a Kite transaction?
Use the official mainnet explorer at https://kitescan.ai/. The developer docs also list https://testnet.kitescan.ai/ for testnet activity.
What is Kite Passport?
Kite Passport is the project's agent identity and control layer. It is designed to bind agents to principals, scope authority through budgets and permissions, support short-lived sessions, and provide revocation and auditability.
Is Kite compatible with Ethereum tooling?
Yes. Official materials describe Kite Chain as EVM-compatible, and the developer docs provide EVM-style RPC/network settings and smart-contract deployment guidance.
Where can developers find code and documentation?
The official developer portal is https://docs.gokite.ai and the project GitHub organization is https://github.com/gokite-ai/.
External trackers
Choose a tracking site for Kite:





