[Docs] Add provider qualification checklist - #3371
Draft
roomote-roomote[bot] wants to merge 1 commit into
Draft
roomote-roomote[bot] wants to merge 1 commit into
roomote-roomote[bot] wants to merge 1 commit into
Conversation
Contributor
| 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. |
Contributor
There was a problem hiding this comment.
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
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.
What changed
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