Skip to content

Update provider registration instructions for org plans #1853

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Jul 30, 2025
Merged

Update provider registration instructions for org plans #1853

Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
f423399
Update provider registration instructions for org plans
julien-c Jul 29, 2025
d4b0ac8
this is done no @SBrandeis?
julien-c Jul 29, 2025
f02ebae
update wording
julien-c Jul 30, 2025
a643f03
move to a better spot
julien-c Jul 30, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/inference-providers/register-as-a-provider.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -129,7 +129,7 @@ First step is to use the Model Mapping API to register which HF models are suppo

<Tip>

To proceed with this step, we have to enable your account server-side. Make sure you have an organization on the Hub for your enterprise.
To proceed with this step, we have to enable your account server-side. Make sure you have an organization on the Hub for your company, and upgrade it to a Team or Enterprise plan.

</Tip>

Expand Down Expand Up @@ -204,7 +204,7 @@ for TogetherAI) with **Write** permissions to be able to access this endpoint.
The endpoint validates that:
- `hfModel` is indeed of `pipeline_tag == task` OR `task` is "conversational" and the model is
compatible (i.e. the `pipeline_tag` is either "text-generation" or "image-text-to-text" AND the model is tagged as "conversational").
- (in the future) we auto-test that the Partner's API successfully responds to a
- we auto-test that the Partner's API successfully responds to a
Copy link
Member

@Vaibhavs10 Vaibhavs10 Jul 29, 2025

Choose a reason for hiding this comment

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

Suggested change
- we auto-test that the Partner's API successfully responds to a
- we automatically test whether the Partner API correctly handles huggingface.js/inference calls for the relevant task, ensuring the API specifications are valid.

suggestion: the earlier sentence read a bit weird to me

Copy link
Member Author

@julien-c julien-c Jul 30, 2025

Choose a reason for hiding this comment

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

thanks it's updated in f02ebae

huggingface.js/inference call of the corresponding task i.e. the API specs are valid.
Copy link
Member

@Vaibhavs10 Vaibhavs10 Jul 29, 2025

Choose a reason for hiding this comment

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

Suggested change
huggingface.js/inference call of the corresponding task i.e. the API specs are valid.

in case you accept the above suggestion.


### Delete a mapping item
Expand Down