Skip to content

feat: add Codeify provider#3294

Open
whale9820 wants to merge 1 commit into
anomalyco:devfrom
whale9820:feat/codeify-provider
Open

feat: add Codeify provider#3294
whale9820 wants to merge 1 commit into
anomalyco:devfrom
whale9820:feat/codeify-provider

Conversation

@whale9820

Copy link
Copy Markdown

Summary

  • add Codeify as an OpenAI-compatible provider at https://codeify.cc/v1
  • add 25 models from Codeify's live catalog using canonical base_model metadata
  • add Codeify pricing and a compliant currentColor SVG logo

Sources

Validation

  • bun validate
  • git diff --check

@github-actions

Copy link
Copy Markdown
Contributor

Action items

  • [low] [possible mistake] providers/codeify/provider.toml:1 and providers/codeify/models/*.toml - Check: Reasoning-control API surface for an OpenAI-compatible provider. Why: All 25 models inherit reasoning = true from their base_model and every provider TOML sets reasoning_options = [], which asserts that Codeify exposes no caller-selectable reasoning control. Codeify is declared OpenAI-compatible at https://codeify.cc/v1, and the mirrored upstream models natively expose reasoning controls (OpenAI gpt-5.6/gpt-5.4 use reasoning_effort, Anthropic Claude uses effort, xAI Grok uses effort, Zhipu GLM uses a toggle). OpenAI-compatible gateways in this repo routinely forward reasoning_effort/thinking (see providers/anyapi/provider.toml and providers/alibaba-coding-plan/provider.toml, which document the exact HTTP form). The PR body cites catalog/pricing/docs pages but states nothing about reasoning request fields, so the empty-array claim is unsupported. Action: Verify against Codeify's API docs/playground whether reasoning_effort (OpenAI-style) or thinking (Anthropic-style) is accepted/forwarded for these model IDs; if so, author the matching reasoning_options and document the request syntax in provider.toml. If no control is verified, keep [] but add a brief note in the PR body (or provider.toml header comment) recording what was checked.

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