Ethereum’s zkAPI brings privacy-preserving API payments to mainnet

The Ethereum Foundation and the Open Anonymity Project have launched zkAPI on Ethereum mainnet, a zero-knowledge based system that lets users prepay for API services while keeping billing identities private. The implementation issues short-lived, capped API keys and uses ZK proofs to show sufficient credit without revealing which on-chain deposit belongs to a caller.

By AI Newsroom· Reviewed by Pranav, Founder & Editor-in-ChiefPublished 1 minute agoUpdated 1 minute ago0 views
Ethereum’s zkAPI brings privacy-preserving API payments to mainnet

Why It Matters

This brings a concrete privacy-preserving payment mechanism for metered services such as AI APIs from proposal to live mainnet code, enabling prepaid, unlinkable billing flows while separating usage from settlement. It also provides developer tools (a client, SDK and browser chat) to accelerate adoption and experimentation.

Key Facts

  • Announcement: zkAPI live on Ethereum mainnet, announced by the Ethereum Foundation
  • Partners: Built with the Open Anonymity Project
  • Mechanism: Users deposit funds into an Ethereum vault and use zero-knowledge proofs to prove they have enough credit without revealing which deposits are theirs
  • Features: Issues short-lived API keys with predefined spending limits; prompts go directly to AI providers while usage is settled separately through the payment layer
  • Developer tools: Released a local client, software development kit (SDK), and a browser-based AI chat implementation

The Ethereum Foundation said on Thursday that zkAPI, developed with the Open Anonymity Project, is now operational on Ethereum mainnet. The system implements a zero-knowledge approach to prepaid API payments: users deposit funds into a shared on-chain vault and produce ZK proofs to demonstrate they hold enough credit for an API call without disclosing which on-chain deposit belongs to them. One immediate application promoted by the team is private payments for AI services. zkAPI generates short-lived API keys that carry fixed spending caps; API prompts are sent directly to providers, while settlement of usage fees happens separately through zkAPI's payment layer. The design intends to unlink billing identities from API consumption by separating the payment attestations from direct provider interactions. The release includes developer tooling to ease experimentation and integration, such as a local client, an SDK, and a browser-based AI chat demo. Vittorio Rivabella, AI coordinator at the Ethereum Foundation’s dAI team, described the core flow in a foundation post, underscoring that the system turns zero-knowledge API payment ideas into an operational mainnet implementation. zkAPI follows a February proposal by Ethereum researcher Davide Crapis and co-founder Vitalik Buterin for ZK-based API usage credits; the new launch realizes that concept in usable code. The project’s authors caution, however, that zkAPI does not conceal prompt contents or network-level metadata from providers — IP addresses, timing signals, or information embedded in requests can still link activity across sessions.

Keep Reading