Skip to content

docs: add OpenZoo provider setup guide - #562

Open
staccDOTsol wants to merge 2 commits into
RooCodeInc:mainfrom
staccDOTsol:docs/openzoo
Open

docs: add OpenZoo provider setup guide#562
staccDOTsol wants to merge 2 commits into
RooCodeInc:mainfrom
staccDOTsol:docs/openzoo

Conversation

@staccDOTsol

@staccDOTsol staccDOTsol commented Sep 1, 2026

Copy link
Copy Markdown

Updated 2026-09-02: corrected — the hosted https://api.openzoo.fun/v1 endpoint answers HTTP 402 to a plain OpenAI client (it only serves calls that pay x402 or carry an OpenZoo subscription key, ozk_live_…). The page now sets up the local npx openzoo proxy (http://localhost:8402/v1), which pays x402 per call from a local burner wallet and ignores the API key.

Adds a provider guide for OpenZoo plus its index.json entry — the same shape as the merged ChatGPT Plus/Pro guide (#492).

OpenZoo works with Roo Code today through the existing "OpenAI Compatible" provider type; this page documents the local npx openzoo proxy as the base URL (http://localhost:8402/v1; the proxy ignores the API key, so any non-empty value works; billing is per call from the proxy's wallet), notes that the hosted endpoint needs x402 or a subscription key, and carries the tool-calling note per your openai-compatible requirements.

Disclosure: I operate OpenZoo. Verification: npx openzoo then curl http://localhost:8402/v1/models is free and lists model ids + pricing.

🤖 Generated with Claude Code

@staccDOTsol
staccDOTsol requested a review from mrubens as a code owner September 1, 2026 08:33
@vercel

vercel Bot commented Sep 1, 2026

Copy link
Copy Markdown

@jrsdunn123 is attempting to deploy a commit to the Roo Code Team on Vercel.

A member of the Team first needs to authorize it.

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.

2 participants