You Can Pay an AI API Without Being Known. Ethereum Just Shipped That.

Opening & At a Glance

You open a chat with an AI model and ask something you would not put on a company Slack. Health. Money. A half-formed idea about a deal that is not public yet. The model answers. Somewhere in that path, an API key still points at an account, and the account still points at a card. Years of prompts become one profile. That is the quiet tax of metered AI today.

On 1 October 2026, the Ethereum Foundation's dAI team published a different path. zkAPI — built with the Open Anonymity Project — lets you deposit credits into an onchain vault, then authorise usage with a zero-knowledge proof instead of an identity. The Foundation says it runs on Ethereum mainnet now.

What Happened, in Plain English

You deposit into a vault contract. Your balance becomes a private note — digital cash only you can spend. When your local client needs to pay, it produces a short zero-knowledge proof that a funded note covers this spend and has not been spent before. The zkAPI server checks the proof and mints a short-lived, dollar-capped API key that lives in your device memory. Your prompts go to the provider with that key. When the key expires, a signed usage receipt settles against your private balance.

Deposits sit as commitments in a Merkle tree, so a proof can say "this note is one of the valid ones" without naming which. Every spend publishes a nullifier — a one-way serial from the note's secret — so double-spend attempts show up without revealing who you are. The blog names Groth16 on BN254, Poseidon hashes, and a 32-level Merkle tree. The vault verifies the same kind of proof at deposit, close, and escape, so your exit does not depend on a server staying honest.

Runtime-key mode keeps the payment intermediary off the prompt path. Proxy mode is easier to run, but the relay sees traffic. The client speaks OpenAI- and Ollama-compatible APIs on localhost. The Foundation lists AI inference first, then RPC, media jobs, VPN bandwidth, and agents that need to pay without an account.

Confirmed vs Analysis — Keep the Labels Honest

Why This Week's Privacy Stack Feels Different

Policy is still messy. We already covered how the U.S. Clarity Act stalled in the Senate — lobby dollars hit a wall, and market-structure clarity stayed unfinished. That fight is about who regulates exchanges. zkAPI is narrower: can you use a paid API without building a permanent dossier for whoever holds the billing relationship?

My take, labelled as opinion: the interesting part is not "ZK is cool." It is that the Foundation published the failure modes in the same post as the launch. No network anonymity. Prompt content can still fingerprint you. Proxy mode sees traffic. That honesty is rarer than another privacy-is-back headline. Same week, Aztec's zk.money return shows private payments waking up on a purpose-built L2 — with its own early caps and public deposit trail. Two layers. Same direction: privacy as product plumbing.

I'm less sure this becomes default for enterprise AI spend tomorrow. Procurement likes invoices with names. Compliance likes audit trails that name a human. zkAPI solves "the provider should not own my prompt history tied to my card" better than "my auditor needs a named cost centre." Both needs are real. They pull opposite ways.

Questions Readers Are Likely to Ask

Does zkAPI hide what I ask the model? No. The provider still sees prompts and responses. It hides the payment identity and the billing link between sessions.

Can I withdraw if the zkAPI server dies? The Foundation says yes for vault funds — close and withdraw onchain. That exit path does not depend on server honesty.

Is this the same as Aztec's zk.money? No. zk.money is a self-custodial wallet for private stablecoin payments on Aztec. zkAPI is private metered API credits on Ethereum. Related privacy week, different products.

Closing & Sources

Confirmed from the Ethereum Foundation's 1 October post: zkAPI is described as live on mainnet, separates payment from identity with vault notes and ZK spend proofs, and openly lists network and content limits. Aztec's 29 September zk.money relaunch is separate same-week context. Whether enterprises adopt unlinkable API spend — or keep demanding named invoices — is still open. At least the tooling argument moved from paper to a mainnet vault.

• Ethereum Foundation Blog — "Introducing zkAPI: private usage credits for any API" (Vittorio Rivabella, dAI Team, 1 Oct 2026)
• Ethereum Research lineage cited in the same post (Davide Crapis & Vitalik Buterin design)
• Decrypt — Aztec brings back zk.money (29 Sep 2026); Aztec Network posts for product/cap details

Methodology Note: Editorial synthesis of the Ethereum Foundation primary announcement. Aztec details from Decrypt and Aztec's own posts, labelled separate context. RogueGhost is not affiliated with the Ethereum Foundation, Open Anonymity, or Aztec. Not legal, tax, or investment advice. Analysis labelled as analysis.