The Ethereum Foundation has launched zkAPI, a privacy-focused payment system designed to let users pay for AI models and other meEthereum Foundation Launches zkAPI for Private AI Payments
The Ethereum Foundation has announced zkAPI, a payment system designed to let users pay for AI models and other metered APIs without linking their billing identity to their requests.
Built by the Open Anonymity Project in collaboration with the foundation, zkAPI is live on Ethereum mainnet. The Ethereum Foundation’s October 1 announcement explains how zero-knowledge proofs separate payment authorization from API usage, allowing spending to be verified without identifying the deposit that funded it.
Key takeaways
The foundation describes funding with ETH, USDC and other credits; the current repository documents native ETH funding.
Zero-knowledge proofs verify spending authorization without revealing the underlying deposit or billing identity.
In its direct mode, zkAPI lets users send prompts to an AI provider without sharing them with the payment server.
Potential applications include blockchain RPC, image and video generation, VPN bandwidth and machine-to-machine payments.
IP addresses, timing information and prompt content can still reveal information or link sessions.
The public repository describes the protocol as experimental.
Separating AI usage from payment identity
Traditional AI APIs generally require an account or API key connected to a payment method. That creates a persistent relationship between a customer’s billing information and the requests they make.
zkAPI takes a different approach. Users first deposit funds into a vault on Ethereum, managed through a smart contract. The deposit is represented as a private note rather than a conventional account balance. When a user wants to access a metered service, software running on their device generates a zero-knowledge proof demonstrating that spending is backed by an eligible balance.
The proof does not reveal which deposit belongs to the user. In the direct runtime-key mode, the zkAPI server verifies payment authorization and issues a temporary API key with a spending limit. Prompts then travel directly from the user’s device to the AI provider.
The spending limit reserves funds rather than determining the final bill. At settlement, the private balance is charged for actual metered usage.
The system also uses nullifiers to prevent double spending. A nullifier acts as a cryptographic marker without exposing the private note behind it. These mechanisms draw on the broader role of cryptography in blockchain technology.
From Ethereum research to a mainnet implementation
The technology builds on a proposal published by Davide Crapis and Ethereum co-founder Vitalik Buterin on Ethereum Research on February 11, 2026.
Their proposal identified a privacy problem with existing API payment models. Linking every request to an account can allow providers to build long-term profiles of users, while making individual onchain payments for every request can be costly, inefficient and publicly traceable. The proposed solution was to allow users to deposit funds once and authorize multiple API calls privately.
zkAPI turns that concept into a functioning implementation. The project’s public repository includes the client, browser SDK, contracts and supporting infrastructure required for the protocol. It also provides an OpenAI-compatible local client, allowing compatible applications to interact with the system without requiring a completely different interface.
The launch fits into the Ethereum Foundation’s broader work around AI infrastructure, including payments, coordination and agent infrastructure.
Privacy has limits
zkAPI does not make an AI user’s entire activity anonymous. Network information can still expose users. A stable IP address, request timing and traffic patterns could potentially allow sessions to be correlated.
Prompt content creates another potential source of identification. Repeated personal information, writing patterns or unique project details could allow an AI provider to associate otherwise separate sessions.
The operating mode also matters. The direct mode separates prompts from the payment server, while a simpler proxy mode relays requests through the zkAPI server. In that mode, the relay can see the traffic it handles.
That distinction means zkAPI primarily addresses the link between payment identity and API usage, rather than providing complete network or content privacy.
The project’s GitHub repository describes the protocol as experimental. The launch announcement identifies Groth16 proofs over BN254, Poseidon hashing and a 32-level Merkle tree among its cryptographic components.
Beyond AI payments
Although private AI inference is the first major application, the same payment model can be applied to other metered services. The Ethereum Foundation lists blockchain RPC queries, image and video generation, VPN bandwidth and payments between autonomous machines as potential applications.
This could become particularly relevant as AI agents use cryptocurrency to interact with paid digital services without direct human involvement.
For now, zkAPI represents an attempt to solve a specific privacy problem: allowing a user to pay for digital services without making the payment relationship the permanent identity attached to every request.
Conclusion
The zkAPI launch moves Ethereum’s zero-knowledge research into a live system for private API payments. By separating payment authorization from service requests, the technology gives users a way to pay for AI services without automatically attaching their billing identity to their prompts.
Its protections remain limited by network metadata, information contained in requests and the operating mode used. The protocol is still experimental, but the mainnet release provides a working implementation of the private API payment design proposed by Crapis and Buterin earlier this year.
Disclaimer: This article is intended solely for informational purposes and should not be considered trading or investment advice. Nothing herein should be construed as financial, legal, or tax advice. Trading or investing in cryptocurrencies carries a considerable risk of financial loss. Always conduct due diligence before making any trading or investment decisions.
Trade with proof of Reserves
UEEx publish monthly audits and third party verification on every listed market.