Conversation
Contributor
|
Thanks for updating your PR! It now meets our contributing guidelines. 👍 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue for this PR
Closes #
No issue — this follows the "Adding New Providers" path in
CONTRIBUTING.md.Type of change
What does this PR do?
Adds a Boundless entry to the provider Directory in
packages/web/src/content/docs/providers.mdx, placed alphabetically between Baseten and Cerebras. It follows the same four-step shape as the other API-key providers (console link →/connect→ paste key →/models).CONTRIBUTING.mdsays the catalog PR comes first, so that one is already open: anomalyco/models.dev#7342 (15 models, both checks green, reviewer bot reports no findings). This PR should land after it.No code changes are needed, for two reasons I checked in the source rather than assumed:
npm = "@ai-sdk/openai-compatible",api = "https://api.inference.boundless.network/v1",env = ["BOUNDLESS_API_KEY"]), soOpenAICompatiblePlugininpackages/core/src/plugin/provider/openai-compatible.tsalready constructs the SDK for it. It matches on the package name only, so nothing provider-specific is required.providerIconsPlugin()inpackages/ui/vite.config.tsfetcheslogos/<provider>.svgfor every provider inapi.jsononbuildStart, soboundless.svgand the regenerated sprite/types.tscome for free once the catalog PR merges. Committing them here would only create churn.I deliberately did not touch
popularProvidersinpackages/app/src/hooks/use-providers.tsor thefeaturedarray indialog-connect-provider.tsx— those are maintainer curation, not something a new provider should add itself to.How did you verify your code works?
bun installat the repo root fails on this machine while buildingtree-sitter-powershell(node-gyp), which is unrelated to docs, so I verified the page directly instead:providers.mdxwith@mdx-js/mdx+remark-gfmafter stripping frontmatter — compiles clean, 54###Directory entries, and the new heading sits betweenBasetenandCerebras.prettier --check packages/web/src/content/docs/providers.mdx— passes.The change is content-only inside an existing page: no new imports, components, or frontmatter.
Separately, while preparing the catalog entry I probed the live Boundless API to confirm what goes in
reasoning_options, so the/modelsstep reflects real behaviour — details are in the models.dev PR.Screenshots / recordings
Not a UI change.
Checklist
English
providers.mdxonly; the locale copies are handled by thedocs-locale-syncworkflow.