When you use hosted AI APIs (like OpenAI, Anthropic, or specialized model providers), two main things track you:
The Payment Layer: Credit cards, billing profiles, and KYC-bound accounts tie every single dollar spent directly to your identity.
The Usage Layer: Standard API keys link every prompt, query, and agentic workflow back to a persistent user profile.
Even if an AI company claims they don't train on your data, your usage patterns, prompt histories, and metadata remain tied to your payment account.
How zkAPI Works
Developed jointly by the Ethereum Foundation and The Open Anonymity Project, zkAPI operates as an "anti-tracking inference layer" built on Zero-Knowledge proofs (using the Groth16 scheme over BN254):
Vault Deposit: You deposit funds (ETH or USDC) into a smart contract vault on the Ethereum mainnet.
ZK Credit Proof: Your local client generates zero-knowledge proofs certifying you have available funds without revealing your wallet address, funding origin, or remaining total balance.
Ephemeral Credentials: The system issues short-lived, ephemeral local keys with dollar-denominated spending caps.
Decoupled Roles:
The Payment Layer sees the transaction/spend, but has zero visibility into what prompts or models were used.
The AI Provider receives and processes the prompt, but only sees an ephemeral key; they cannot link the request to a bank account, wallet, or persistent profile.
Why It Matters
Native Agent Economics: Autonomous AI agents need to hold capital and spend it independently. With zkAPI, AI agents can pay for their own compute on-demand without needing human-linked credit cards or exposing their operator's identity.
Plug-and-Play Integration: The local zkAPI client emulates standard OpenAI and Ollama API specifications. Developers can plug existing UIs, code editors, or agent frameworks into it simply by pointing requests to localhost.
Beyond AI: While designed for AI inference (where sensitive health, financial, or personal context is common), the same zero-knowledge credit architecture works for any usage-based API—such as blockchain RPC nodes, image generation, and cloud compute.
A Quick Caveat: While zkAPI completely decouples your identity from the financial transaction, the Open Anonymity team notes that the prompt text itself still goes to the model provider. Users still need to avoid embedding personal details or unique stylometric signatures in their prompts to maintain full operational security.