Skip to content

Add zipcoin chat - #157

Open
zipcoincash wants to merge 1 commit into
OpenRouterTeam:mainfrom
zipcoincash:add-zipcoin-chat
Open

zipcoincash wants to merge 1 commit into
OpenRouterTeam:mainfrom
zipcoincash:add-zipcoin-chat

Conversation

@zipcoincash

Copy link
Copy Markdown

Adds zipcoin chat — https://chat.zipcoin.cash (open source: https://github.com/zipcoincash/zipcoin-chat).

Private AI chat on OpenRouter models with no account: credits are funded from a zipcoin privacy-pool note, and each session gets a short-lived OpenRouter key (5 minutes, $1 cap) issued by zkAPI after a zero-knowledge proof that the note can pay. Requests go from the browser straight to openrouter.ai/api/v1/chat/completions with HTTP-Referer: https://chat.zipcoin.cash and X-Title: zipcoin chat. The whole OpenRouter catalog is available in the picker.

Flagging one thing about eligibility: there is no bring-your-own-OpenRouter-key mode, on purpose. The keys are zkAPI's per-session runtime keys (Open Anonymity's org), so a user never holds or pastes a key — that is the privacy property of the app: OpenRouter sees the prompt but not who paid. Adding a personal-key mode would put an account and a billing history behind every prompt, which is what the app exists to avoid. If that rules it out, understood; we'd argue it fits the "unique or innovative" exception. How OpenRouter is used, in plain words: https://chat.zipcoin.cash/privacy#openrouter

Traction, honestly: launched Oct 2, 2026; first-day users funded chats anonymously on Ethereum mainnet (zkAPI vault deposits via the zipcoin privacy pool are public on chain even though users are not). Also ships a CLI/MCP flavour for agents (npm i -g @zipcoin/agent, zipcoin ai chat "…"), same OpenRouter path.

Works with zkAPI (an Ethereum Foundation dAI / Open Anonymity project); not affiliated with either, nor with OpenRouter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant