continuedev / continuedev/continue

docs: PZERO OpenAI-compatible apiBase example

Open Beginner friendly
#13,198 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
36k
Forks
5.4k
PR merge metrics
No merged PRs in 30d

Description

Issue Category

Undocumented feature or missing documentation

Affected Documentation Page URL

https://docs.continue.dev/customize/model-providers/top-level/openai

Issue Description

The OpenAI page already documents provider: openai plus apiBase for compatible hosts. The "OpenAI API compatible providers" list has no named PZERO example, so users guess the host, key format, and whether to force /chat/completions.

PZERO is prepaid inference. Venice-only upstream. Bearer pzero_ key. Sign-in free. Usage paid. Min top-up 1 USDC on Base. No starter credits.

This is separate from the hosted MCP connector (already filed as a docs example for MCP). This request is the OpenAI-compatible chat path Continue already supports.

Expected Content

A named PZERO row or snippet on that page:

name: PZERO
version: 0.0.1
schema: v1

models:
  - name: PZERO
    provider: openai
    model: deepseek-v4-flash
    apiBase: https://api.pzero.studio/v1
    apiKey: pzero_YOUR_KEY
    useResponsesApi: false

apiBase is the /v1 root, not /v1/chat/completions. useResponsesApi: false keeps Continue on POST /v1/chat/completions for this model. PZERO also serves POST /v1/responses if a later Continue path wants it.

Get a key: https://pzero.studio/agents

Live text ids (public, no key): GET https://api.pzero.studio/v1/models

I am not asking for a first-party Continue provider. provider: openai + apiBase is the existing seam.

Every AI Credit is at least 20% off $1 list. Usage is paid. Do not start implementation on my behalf until the board says Ready; the YAML is for users today.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Open the OpenAI-compatible providers page at https://docs.continue.dev/customize/model-providers/top-level/openai and find the existing provider examples. Add a named PZERO example using the supplied YAML, API base, key placeholder, and chat-completions setting, then verify that the page explains where to get a key and what the /v1 base represents.

Written by the indexing model from the issue text.

Assessment

Tech stack
yaml
Domain
documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
85/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.