EthereumETH, coin
DevelopingProtocol update

Ethereum Foundation and Open Anonymity Project put zkAPI live on Ethereum mainnet

Crypto.News reports zkAPI went live on Ethereum mainnet on October 1, letting users prove an AI API request is paid for without revealing who paid, while the provider still sees prompts.

Why it matters

The deployment separates hiding the payer from hiding the interaction, which Crypto.News notes is a narrower privacy claim than an anonymous conversation with a model. Whether it draws traffic is unestablished: one outlet carries the story, the mainnet vault holds USDC credits of unstated size, and no third party has verified the vault or its balances.

Key facts

The Ethereum Foundation and the Open Anonymity Project launched zkAPI on Ethereum mainnet on October 1.

Reported by Crypto.News

The system uses an onchain vault alongside offchain proof checks.

Reported by Crypto.News

A user can deposit credits and prove a later AI API request is paid for without giving the payment server an identity or the model provider the funding address.

Reported by Crypto.News

The model provider still receives the prompt, and the proof hides only which note pays for usage.

Reported by Crypto.News

One funded note can authorize a capped, short-lived API session rather than requiring one onchain payment per prompt.

Reported by Crypto.News

The payment server learns that a spend is valid and the session total.

Reported by Crypto.News

Proxy mode lets the zkAPI server see traffic, while direct runtime-key mode avoids a content relay.

Reported by Crypto.News

The mainnet vault holds USDC credits, and IP addresses, timing, reused context and personal details can still link sessions to one person.

Reported by Crypto.News

What happened

Crypto.News reports that the Ethereum Foundation and the Open Anonymity Project launched zkAPI on Ethereum mainnet on October 1, built around an onchain vault and offchain proof checks. A user deposits credits and can later prove that an AI API request is paid for, without giving the payment server an identity or the model provider the funding address. The same outlet stresses the limit of that design: the provider still receives the prompt, because the proof hides which note pays for usage while the provider runs the model and sees the request. One funded note can authorize a capped, short-lived API session instead of one onchain payment per prompt, and the payment server learns that a spend is valid along with the session total. Two modes are described, with direct runtime-key mode avoiding a content relay and proxy mode letting the zkAPI server see traffic. Crypto.News lists IP addresses, timing, reused context and personal details as factors that can link sessions despite a hidden payment source, and says the Ethereum Foundation technical announcement itself names network metadata and prompt content as remaining correlation points. The Foundation's account, relayed by Crypto.News, is the only description of the system available here, and no second outlet has reported the launch.

How the story developed

  1. Official statement

    Ethereum Foundation states zkAPI is live on mainnet with an onchain vault and offchain proof checks

    The Foundation technical announcement, relayed by Crypto.News, sets out what the proof hides and names network metadata and prompt content as remaining correlation sources. A public GitHub repository and a demonstration chat interface are linked from the announcement.

    Crypto.News

  2. First report

    First report by Crypto.News

    Ethereum’s zkAPI hides who pays for AI. The model still sees the prompt

    Crypto.News

  3. Update

    Crypto.News publishes the only account of the launch

    No other outlet in the evidence set reports the deployment or offers an independent description of the vault.

    Crypto.News

Affected entities

Original sources

PublisherReportRolePublished
Crypto.News
Crypto media
Ethereum’s zkAPI hides who pays for AI. The model still sees the promptOriginal