Skip to content

[Docs] Add provider qualification checklist - #3371

Draft
roomote-roomote[bot] wants to merge 1 commit into
developfrom
docs/openai-provider-qualification-2wgzzbqis94gj
Draft

roomote-roomote[bot] wants to merge 1 commit into
developfrom
docs/openai-provider-qualification-2wgzzbqis94gj

Conversation

@roomote-roomote

Copy link
Copy Markdown
Contributor

​Opened on behalf of @mrubens. View the task or mention @roomote-roomote for follow-up asks.

What changed

  • Added a reusable qualification checklist for OpenAI-compatible inference providers and gateways.
  • Defined the evidence a compatibility report should include across model discovery, streaming, tool calls, multi-turn behavior, limits, and errors.
  • Directed provider maintainers to Roomote's issue-first review and contribution process.

Why this change was made

The existing guide explains how operators connect an endpoint, but provider maintainers had no concrete way to demonstrate compatibility or request review. The new guidance makes that path self-service without treating protocol compatibility as endorsement or adding an untested catalog provider.

Impact

Provider maintainers can submit focused, privacy-safe compatibility evidence, while maintainers receive a consistent review packet instead of an unsolicited integration pull request.

Screenshots

OpenAI-compatible provider qualification checklist rendered in Roomote Docs

@roomote-community

roomote-community Bot commented Oct 2, 2026 •

Copy link
Copy Markdown
Contributor

1 issue outstanding. See task

  • apps/docs/providers/inference/openai-compatible.mdx:75-76 Limit the credential-rejection check to endpoints that require bearer authentication.

Reviewed adcc351

same path a Roomote task uses:

1. Confirm `GET /v1/models` returns stable model IDs with the configured bearer
credential, and that a missing or invalid credential is rejected.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This makes authentication rejection a requirement for every qualifying endpoint, but this same guide explicitly supports endpoints without an API key (including local servers). Those endpoints cannot reject a missing credential, so they are incorrectly excluded from the checklist. Scope this assertion to endpoints configured to require bearer auth, and allow keyless endpoints to report that authentication is not applicable.

This branch has not been deployed

No deployments
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