[FEEDBACK] Inference Providers
Any inference provider you love, and that you'd like to be able to access directly from the Hub?
Love that I can call DeepSeek R1 directly from the Hub 🔥
from huggingface_hub import InferenceClient
client = InferenceClient(
provider="together",
api_key="xxxxxxxxxxxxxxxxxxxxxxxx"
)
messages = [
{
"role": "user",
"content": "What is the capital of France?"
}
]
completion = client.chat.completions.create(
model="deepseek-ai/DeepSeek-R1",
messages=messages,
max_tokens=500
)
print(completion.choices[0].message)
Is it possible to set a monthly payment budget or rate limits for all the external providers? I don't see such options in billings tab. In case a key is or session token is stolen, it can be quite dangerous to my thin wallet:(
@benhaotang you already get spending notifications when crossing important thresholds ($10, $100, $1,000) but we'll add spending limits in the future
@benhaotang you already get spending notifications when crossing important thresholds ($10, $100, $1,000) but we'll add spending limits in the future
Thanks for your quick reply, good to know!
Would be great if you could add Nebius AI Studio to the list :) New inference provider on the market, with the absolute cheapest prices and the highest rate limits...
Could be good to add featherless.ai
TitanML !!
OpenRouter!
Hi everyone and first of all I really thank huggingface team for releasing this feature.
One another suggestion that I need is :
to give more granular parameters for the user to share the deployment configuration file (as an terraform hcl configuration) in order to define more optimum infrastructure for inference and let them define the inference model.
requesty.ai
groq
TypeError: InferenceClient.__init__() got an unexpected keyword argument 'provider'
Add RunPod as an inference provider!
Hyperbolic!
Runpod!
@llamameta please, make sure you use the latest version of huggingface_hub
pip install --upgrade huggingface_hub
Hello. Congratulations on great feature. How we can proceed on adding deepinfra.com to the providers list?
That's a great news, and if you provide more measurable details on what's free inference with a small quota is about for signed-in free users, you'll build more trust around the community, hence more PRO subscribers!
requesty.ai !
Runpod is excellent.
Let's add it to inference provider list
runpod!
Runpod would be very welcome!
Yes, Runpod.io would be great indeed
is there a way to add https://nineteen.ai/ as a provider ? it allows free access to top models like Deepseek R1 & the llama family
there is also : https://chutes.ai/ which can allow users to deploy any model on demand
Can we Add https://avian.io as a provider @julien-c
Currently have the fastest inference on Nvidia hardware, as well as highest throughput, allowing users to deploy any model on demand
ai/ml api - dudes have a lot of models from HF!
try Runware.
Runware plz – it's ~5x cheaper than other providers and still one of the fastest
Try Scaleway.
Runware is best kept secret in the industry
I can't use DeepSeek R1 with hf inference npm , got this error :
ChatButton.tsx:120 Error: Error: Model deepseek-ai/DeepSeek-R1 is not supported for task conversational and provider together
at mapModel (@huggingface_inference.js?v=2d418915:235:11)
at makeRequestOptions (@huggingface_inference.js?v=2d418915:158:13)
at streamingRequest (@huggingface_inference.js?v=2d418915:434:31)
at streamingRequest.next (<anonymous>)
at chatCompletionStream (@huggingface_inference.js?v=2d418915:933:10)
at chatCompletionStream.next (<anonymous>)
at handleSendMessage (ChatButton.tsx:94:21)
from code :
const client = new HfInference(hf_token);
for await (const chunk of client.chatCompletionStream({
model: "deepseek-ai/DeepSeek-R1",
provider: "together",
messages: [{ role: "user", content: input }],
temperature: 0.5,
stream: true,
})) {
...
Runware would be great. I can run all of my models with them.
runware currently costs the same as just the electric power to run a 4090 in germany xD
Add Novita AI pls!!
I prefer Novita AI. Deepseek-r1 is currently more stable on Novita than on the official platform.
Novita AI!!
fireworks, they are super-fast
segmind.com is the best, cheap and fastest
Would love to see beam.cloud!
STOP LYING!!! THE FCKIN LAW SAYS THAT I'VE 1000 REQUESTS PER DAY AS A FREE USER, AND 20'000 PER DAY AS A PAID ONE... I'D JUST BECAME A PRO MEMBER, I'D PAY 9 FCKIN DOLLARS AS A POOR GUY, AND AFTER 400 REQUESTS OUT OF TWENTY THOUSAND(!!!), USING ONLY HF INT, THE SYSTEM LIES THAT I'D EXCEEDED MY MONTHLY QUOTA!!! (LITTLE MATH: THE MONTHLY QUOTA IS 600 THOUSAND REQUESTS(!!!), I'D BARELY USED THE HALF OF THE FREE MONTHLY QUOTA THIS MONTH (10'000)...) I'D SEARCHED GOOGLE, ASKED GPT, IT SAYS NOTHING(!!!) ABOUT QUOTA CHANGE FOR HF API... IT'S MY LIVING(!!!) THAT I GENERATE PICS BY SD 3.5, POST IT ON DEVIANTART, AND THEN I SELL IT AS NFTS TO BUYERS... YOU'RE RISKING MY LIVING WITH YOUR SILLY LITTLE GAME, HUGGINGFACE!!! I LOVE THIS PLATFORM, IT HAS THE MOST LIBERAL OF ALL, AND FOR MONTHS, I'D NO PROBLEMS... REALLY, WHY YOU WANT A HF-GATE?!?! CAN I TRUST YOU??? OR MONEY IS NOW YOUR GOD TOO, LIKE ALL THOSE MONEY HUNGRY SH*T SITES??? PLEASE, END THIS NIGHTMARE NOW!!!
Are the use of the new Inference Providers through the HF proxy covered by the same privacy policy as Hugging Face directly? No logging beyond short technical reasons, and no use of input for training?
Add RunPod
Not working with entreprise token in routed mode:
"You have exceeded your monthly included credits for Inference Endpoints. Subscribe to PRO to get 20x more monthly allowance."
Is there a page, where I can filter out models being supported by different providers? Currently one needs to go inside the model card, of every model to find out.
I have been using this new feature with different providers to run Flux and I really like it a lot! But today february 4 it changed from 20,000 daily inferences to $2 dollars montly (200 inferences). I know its fair, and I actually don't use 20,000 inferences, not even 20 daily. But the change from having 20,000 daily inferences to having 6 daily, is shocking, you could have make it gradually or not even giving 20,000 daily since the beggining. It's hard to asimilate that sudden change 😭
HuggingFace, please, provide as a documentation, that exactly tells us how much an Interference costs. (Example: Stable Diffusion HF Interference 0.001$/image etc.)
this is in progress, currently working on it
I have been using this new feature with different providers to run Flux and I really like it a lot! But today february 4 it changed from 20,000 daily inferences to $2 dollars montly (200 inferences). I know its fair, and I actually don't use 20,000 inferences, not even 20 daily. But the change from having 20,000 daily inferences to having 6 daily, is shocking, you could have make it gradually or not even giving 20,000 daily since the beggining. It's hard to asimilate that sudden change 😭
Right, it was a bit shocking. I would always like to use the HF-inference, (as my first choice). Initially I thought that those models that have HF-inference will be consuming from the existing quota (of 20,000). Only the 3rd party ones we have leverage of $2 for pro members. I agree, that 20,000 is bit too much, but the change is rather drastic.
let me run the numbers, but for HF-inference the change should not be that drastic (most HF-inference requests are priced very very cheaply especially of course CPU based models)
The 20,000 daily figure was a bit unrealistic given it was "best-effort" meaning the rate of failures was quite high. Note that from now on, we exclude failing requests from those counts (we didn't up till now)
Any inference provider you love, and that you'd like to be able to access directly from the Hub?
I tested it and I love it, super easy!
The first question from my company was:
With inference providers can we setup something like private endpoints?
@Moibe do you use HF-inference, or external providers?
@julien-c yes I was using the hf-inference and usage was deducted from the 20,000. And about other providers, it allowed me to use them totally free (without substracting from the 20,000) and with a limited quota, meaning that I was able to make some usage of fal-ai until it messages that quota was excedded, then I used together, sambanova, etc. It was great beause it allowed me to test all provider even without having an account. I understand the change, and I think prices are still reasonable. I was just a shocking change, but I'm fine. I even got an account on fal.ai after the free test and I'm satisfied with the service amd the ease of use all from hf interface.
Let's add nineteen.ai PLEAAASE
With inference providers can we setup something like private endpoints?
@levalencia i don't think so but have you looked into Inference Endpoints? (it's dedicated instances)
Subject: Add new provider to the Inference Endpoint.
I work at https://docs.predictionguard.com/home/getting-started/welcome and would like to explore if it is possible to add Prediction Guard to the list of inference providers on Hugging Face. Let me know how to go about this.
"ai/ml api - dudes have a lot of models from HF!"
We just launched our inference product here at io.net called IO Intelligence! Would love to have this plugged into HF as a new inference provider. Currently free to use until 500k token/day limit but we'll have the lowest price per token for the models we host once we roll out full pricing.
Feel free to try it out here: https://ai.io.net/ai/models
I'm really confused on this, it seems like things got a lot worse? Am I understanding that correctly? I'm not really sure how much an individual call would cost or how it can be calculated for a particular endpoint. Maybe I'm just confused but it seems like this announcement is essentially just saying pro subs had a pretty major feature removed. I've never really even used the inference features, but this reads like they are essentially gone now, right?
How can an Enterprise pay for Inference Credits ?
I'm a member of an Org with Enterprise Hub subscription, and I set up a payment method in the billing section of my org account. It seems that an access token can't be created by an Org, so I created an access token using my account, and it does show up in the access tokens of my Org. However, when using Inference providers, it seems to be only consuming my Inference Credits, and not trying to use the payment method of the Org. Is there a way to use Inference providers will billing the Org ? Thanks.
The Python docs for Inference Providers on hub seems to have a small error. I was going to propose a PR, but I couldn't find the source - is this available somewhere?
Steps to reproduce:
- Go to a model page eg. https://huggingface.co/bigcode/starcoder2-15b
- Click
Deploy - Click
Inference Providers - Click
Python(deep link: https://huggingface.co/bigcode/starcoder2-15b?inference_provider=hf-inference&inference_api=true&language=python)
You'll now see
from huggingface_hub import InferenceClient
client = InferenceClient(
provider="hf-inference",
api_key="hf_xxxxxxxxxxxxxxxxxxxxxxxx"
)
result = client.text_generation(
model="bigcode/starcoder2-15b",
inputs="Can you please let us know more details about your ",
provider="hf-inference",
)
print(result)
The problem is that the provider parameter should not be passed in via client.text_generation. It's correctly passed above when the client is instantiated via InferenceClient, but should be removed from client.text_generation.
@julien-c really you should include https://runware.ai as an inference provider.
It is by far the fastest and the cheapest provider with the most comprehensive API for making visual content: just have a look at this awesome documentation: https://runware.ai/docs/en/image-inference/api-reference
A FLUX DEV image is generated in 1.9 seconds with a price of 0.0038 (yes, 3 zeros, almost 10x cheaper than anybody else) , there are 300k+ models on the platform
and they are backed by A16Z, Lakestar and Midjourney
RunPod! The most flexible option out there.
Can you add DeepInfra?
Is there a way to programmatically list the providers and the models available from each of them?
When I try, the following, it fails (I have upgraded to latest huggingface_hub version)
client = InferenceClient(provider="nebius",)
client.list_deployed_models()
Thanks
let me run the numbers, but for HF-inference the change should not be that drastic (most HF-inference requests are priced very very cheaply especially of course CPU based models)
Really? 9$ for 200 messages in chat is a very cheap?
Hello @julien-c ,
I kindly request an increase in the quota limit for API Inference endpoints. As a student with a deep passion for exploring technology through these models, Hugging Face has always been an invaluable resource for me. Unfortunately, the current limits are proving to be a significant barrier, even after investing in the Pro subscription, as they restrict my ability to explore and develop projects in a cost-effective manner.
I believe many students and enthusiasts who love the Hugging Face platform would greatly benefit from a more generous quota. Your consideration in making the platform more accessible would be greatly appreciated.
Thank you for your time and support!
It is great to have the inference providers that allowing people to use the model easily. And I know other model providers also want to cooperate with Hugging Face to create easy, stable, and affordable services to the community. How can they add their api to the Hugging Face? Is there any instruction to do it? Thank you.
This new system is really bad for the users (us/me). Instead of 200.000 api requests like before I am not even getting 5.000 api requests. Already hitting max usage. If you are planning to give us far less credit then we are actually paying for the membership, I would consider not taking the membership and just pay for the spent credits. It is way cheaper. Now I feel like I am paying over 4 times more then the provided services are worth.
Add Runway please
@OFT so we can take a look can you share (here or in DM) which model(s) you're mostly hitting?
And i'm assuming it's on
provider=hf-inference?
@julien-c Thank you for having a look into this.
I am mostly using models that are:
- IMG 2 TXT
- TXT 2 IMG (Flux, SD 3.5, own models, ....)
- TXT 2 TXT
I don't know where I can verify provider=hf-inference. Could you give me a CURL example with this option? (not phyton please)
However I do have the following billing information:
Mar 1 - Mar 31 | HF Inference API (4,585) | $2.02
Feb 1 - Feb 28 | HF Inference API (17,156) | $1.72
It is unclear what happend between the two months since I don't think I changed something?
Extra: After noticing the problem, I also jumped to "https://huggingface.co/settings/inference-providers" and disabled everything except the HF Interference API.
Please add kluster.ai!!
@julien-c please give us prices per request for each model using hf-inference. The question is because the prices for different models vary widely, and I want to know what models are expensive to manage my bills. At least detail view in billing page.
I had cancelled my OpenAI subscription in favor of the HF Pro subscription. Now I realize you took the inference away. I will be cancelling my Pro subscription because frankly I don't understand who asked for this. If I want to use other providers I will use other providers, why would I route it through HF? There is no value proposition whatsoever. Anyone doing production loads will get their own provider anyways.
I would have accepted a price increase or a decreased request limit in the Pro plan over this bad business move. I don't see a point in the Pro subscription anymore, why do you keep it?
Many users are complaining because of prices, let's add these two and enable real free open source for everyone
can i add more money beside the 2$ limitation per month?
since the pay as you go dosent work yet
what are my options?
Hello everyone. I would like to know if there is any document that states how much a single image generation costs with the model "Stable Diffusion 3.5 Large", thanks in advance!
I am trying to estimate how much I would have to pay for N generations.
Please include kluster.ai as well! Thanks!
Important note about Pay-as-you-go (= PAYG) for Inference Providers: https://huggingface.co/posts/julien-c/158943939527784
For Inference Providers who have built support for our Billing API (currently: Fal, Novita, HF-Inference – with more coming soon), we've started enabling Pay as you go (=PAYG)
What this means is that you can use those Inference Providers beyond the free included credits, and they're charged to your HF account.
Would love to have kluster.ai added - thanks!
Hey folks we were recommended to post that Prodia (https://docs.prodia.com/) should become an inference provider as well because of how strongly we rank on Artifical Analysis for image gen models
@gulyasdavid1999 this is unrelated to Inference Providers though
I get a token 403 unexpected error: 403 Forbidden: This authentication method does not have sufficient permissions to call Inference Providers on behalf of user XXX
Code to reproduce :
from huggingface_hub import InferenceClient
client = InferenceClient()
client.list_deployed_models("text-generation-inference")
question around enterprise accounts:
- each user gets a $2 quota?
- in order to apply the quota they have to use a key from their ent account and the
X-HF-Bill-Toheader? - how much does a call cost? I can't find any documentation...
Would be great to add Clarifai to the list. The platform is vendor-agnostic, supporting AWS, GCP, Vultr, and Oracle. We are planning to add a lot more providers soon.
Our company wants to provide some private models.
Is it possible in Model Mapping [ https://huggingface.co/docs/inference-providers/en/register-as-a-provider#3-model-mapping-api ] to have hfModel as a "stub" only and providerModel as a real model?
Just signed up with HF and had some questions for the general community to help us get started. We plan to use the Cerebras Inference Provider using direct calls rather than routing through HF itself.
With a Pro subscription, are there any limits to token usage or queuing constraints when using a custom API key and direct calls? The free tier on Cerebras did have such constraints.
Thanks in advance
Hey all, I'd like to make nCompass (https://docs.ncompass.tech/api-reference/quickstart) an inference provider on HF. We build GPU optimizations to be able to support an API without rate limits by maximizing GPU utilization. I would really appreciate it if someone could help us with the process of becoming an inference provider.
Hi I have a problem using Smoleagents HfApiModel Inference, I noticed that even though I belong to an enterprise organization, the inference API uses the credits of my free account
and not those of the organization
yet I read here (https://huggingface.co/docs/inference-providers/en/pricing)
that it should automatically use those of the organization.
I wrote even here (https://discuss.huggingface.co/t/hugging-face-payment-error-402-youve-exceeded-monthly-quota/144968/10?u=alexman83) and it seems there is a bug...
How we can solve it? For our company. is important use that service...
Thank you for you help!
With a Pro subscription, are there any limits to token usage or queuing constraints when using a custom API key and direct calls? The free tier on Cerebras did have such constraints.
@sh8459131 When using a custom key, requests are forwarded to Cerebras directly so their limits will apply
@alexman83 can you share some sample code you're using? We might need to update smolagents to expose the new bill_to parameter. cc @albertvillanova for viz
@julien-c of course!
Thanks!
from smolagents import CodeAgent
from extraction_smolagents.custom_tools import CSVRetrieverTool
from smolagents import HfApiModel
from huggingface_hub import login
login()
prompt_template = """
# Prompt per Analisi e Estrazione di Topic a partire da una richiesta dell'utente
Sei un esperto analista di contenuti televisivi. Devi estrarre una lista di topics a partire da una richiesta dell'utente nel seguente modo
## Passaggio 1: Analizza la richiesta dell'utente
- Comprendi dalla richiesta dell'utente, indicata dopo la parola 'richiesta', quali sono i topic di suo interesse
## Passaggio 2: Confronto tematiche estratte con quelle fornite
- Leggi il file csv 'topics_info.csv' contente come informazioni il nome del topic (colonna name), le parole rappresentative (colonna representation) e i documenti rilevanti (representative_docs)
- Confronta le parole rappresentative dei vari topic con le tematiche estratte al Passaggio 1 e memorizza solo le righe dei topic che soddisfano questo requisito
- Adesso analizza per i topic memorizzati al passo precedente i documenti rappresentativi e verifica quali siano simili ai temi estratti dalla richiesta dell'utente al Passaggio 1 e memorizzali
## Passaggio 3: Generazione dell'output
Genera un file json contenente:
- la lista dei topic estratti usando il valore della colonna name
- la motivazione per cui sono stati scelti
Organizza il file json come nel segunete esempio:
json
{
"topics": [<topic_1>, <topic_2>, <topic_3>],
"motivazione: <motivazione>
}
"""
retriever = CSVRetrieverTool()
llm_model = HfApiModel(model_id='Qwen/Qwen2.5-Coder-32B-Instruct')
agent = CodeAgent(
tools=[retriever],
model=llm_model,
verbosity_level=2,
additional_authorized_imports = ['pandas']
)
question = prompt_template + '\n' + "voglio tematiche musicali"
answer = agent.run(question)
print(f"Answer: {answer}")
This is the custom class for reading CSV
from smolagents import Tool
import pandas as pd
class CSVRetrieverTool(Tool):
name = "csv_retriever"
description = "Uses the provided path to access a csv file using pandas dataframe"
inputs = {
"path": {
"type": "string",
"description": "The path containing the filename of the csv to read",
}
}
output_type = "string"
def __init__(self, **kwargs):
super().__init__(**kwargs)
def forward(self, path) -> str:
df = pd.read_csv(path)
return df.to_string()
```
@alexman83 Merve (@merve ) opened https://github.com/huggingface/smolagents/pull/1260 which will expose the bill_to param in smolagents' InferenceClient 🔥
(you'll need to upgrade your smolagents version)
@julien-c We just started integrating us WaveSpeedAI http://wavespeed.ai as the inference provider. We provide blazing fast image and video generation services. Happy to see we are listed!
Would be great if you could add Nebius AI Studio to the list :) New inference provider on the market, with the absolute cheapest prices and the highest rate limits...
We have no rate limits at nCompass (https://app.compass.tech) with fast inference. Feel free to give it a spin if rate limits are something that's a bottleneck for you.
we want to be an inference provider and submit pr(https://github.com/huggingface/huggingface.js/pull/1424). Can anyone please help me see
I'm getting a little mad... The private servers aren't working since hours!!! The ZeroGPU spaces freeze out with "worker error" since WEEKS!!! And the dev team aren't urged to fix them... For least a week (during EASTER) the Stable Diffusion picture generators produced pics in APPLE II (80's) quality!!! At least they fix them, but we're losing our patience... OK, the (credit-based) interface version of SD3.5 is working, but that's a funny excuse to not fix the others... Actually, the admins are REQUIRED to fix these errors by law... Yes, you can say that WE may fix it, but many of us aren't senior programmers, and in fact, it's forbidden for average users to fix the API, as the problem is (almost) never local... So, I officially demand the developers to fix the HF API (affecting the spaces) by tomorrow morning (EU time)!!! I really don't want to file a case against you in court...
I am sad, too 🥹💔💔
Hi @julien-c , we at Dat1.co want to be an inference provider and have submitted a PR for the initial step. Could anyone help us move forward? https://github.com/huggingface/huggingface.js/pull/1460
Please add FPT AI Inference http://marketplace.fptcloud.com/
It's a newcomer but already has hundreds of users, thanks to its speed, stability, and competitive price.
black-forest-labs/FLUX.1-schnell is not properly working under HFInference provider, is this going to be permanent or there is an issue?
Actually it seems that HFInference is not working at all, do we need to use models now only via external providers????
The message for any HFInference is: "Our latest automated health check on this model for this provider did not complete successfully." Is this temporary or HFInference won't process certain models anymore, or maybe it is a bug?
Dear Hugging Face Team,
Greetings from Cyfuture AI!
We are reaching out to explore a potential collaboration with Hugging Face. As a rapidly growing enterprise-grade AI solutions provider, Cyfuture AI offers robust and scalable inference capabilities powered by high-performance GPU infrastructure.
We would be keen to join Hugging Face as an official inference provider to support model deployment and inference workloads for your global community. We believe this integration would bring mutual value—enhancing access to affordable, high-speed inference while expanding our reach within the AI ecosystem.
Please let us know the next steps or any prerequisites required to move forward with this partnership.
Looking forward to your response.
Regards,
Cyfuture.ai
Email us at - info@cyfuture.ai
Hi Hugging Face Team,
We are from GmiCloud (https://inference-engine.gmicloud.ai). We want to be an inference provider on Hugging Face. At gmicloud, we focus on LLM inference optimizations. We started to follow the instruction at https://huggingface.co/docs/inference-providers/register-as-a-provider#register-the-provider. While it needs to reach out first. We’d greatly appreciate any guidance or support from the community on how to move forward with becoming an official inference provider on the platform.
Thanks in advance!
Gmi Cloud AI
Email us at - yijie.h@gmicloud.ai
Dear Hugging Face Team,
We're reaching out from Swarmind.ai, a high-performance AI infrastructure company, to express interest in becoming an official inference provider on your platform.
We offer scalable, GPU-powered inference optimized for production workloads, and believe this integration would benefit both communities.
Let us know the next steps to move forward.
Best,
Swarmind Team
ceo@swarmind.ai
Dear Hugging Face Team,
We're reaching out from metay.ai , a high performance AI infra company. We are super excited in becoming an official inference provider.
Pls let us know the next step to move forward.
Best,
Sam
my company email: samli@blockfish.io
CometAPI - Hugging Face Inference Provider Application
Dear Hugging Face Team,
We're reaching out from CometAPI to express our strong interest in becoming an official inference provider on the Hugging Face platform.
About CometAPI
CometAPI is a comprehensive AI platform that provides unified access to over 500 cutting-edge AI models through a single, powerful API. We serve as a bridge between developers and the latest AI capabilities, offering seamless integration with minimal complexity.
Key Highlights:
- 🚀 500+ AI Models: Extensive collection including GPT-5, Claude, GLM-4.5, Qwen3-Coder, Kimi K2, Grok 4, and many more
- 🎨 Multi-Modal Support: Text generation, image creation, video production, music composition, and audio processing
- ⚡ Unified API: Single endpoint for all AI services with OpenAI-compatible API format
- 🔄 Real-time Updates: Instant access to newly released AI models
- 💰 Competitive Pricing: Cost-effective solutions with flexible usage plans
- 🛡️ Enterprise Ready: Robust infrastructure with enterprise-grade security and reliability
Why Partner with CometAPI?
Comprehensive Model Coverage: We provide access to the industry's most extensive collection of AI models, including many that are not available through other providers.
OpenAI API Compatibility: Our API strictly follows OpenAI specifications for LLMs and VLMs, making integration seamless and straightforward.
High-Performance Infrastructure: Built on scalable, enterprise-grade infrastructure designed to handle production workloads with low latency.
Global Reach: Serving developers worldwide with reliable service and comprehensive documentation.
Active Community: Growing ecosystem with active Discord community and comprehensive developer support.
Technical Capabilities
- API Compatibility: Full OpenAI API compliance for chat completions and text generation
- Supported Tasks:
- Conversational AI (text-generation, image-text-to-text)
- Text generation
- Multi-modal capabilities
- Authentication: Bearer token authentication system
- Billing Integration: Ready to implement request ID tracking and cost reporting API
- Rate Limiting: Robust rate limiting and quota management systems
Business Information
- Company: CometAPI
- Website: www.cometapi.com
- API Documentation: api.cometapi.com/doc
- Console: api.cometapi.com/console
Contact Information
Primary Contact: devpartner@cometapi.com
Additional Resources:
- Discord Community: Join our Discord
- Twitter: @cometapi2025
- GitHub: github.com/CometAPI
- Support Email: support@cometapi.com
Next Steps
We are fully committed to following the complete integration process outlined in your documentation:
- ✅ Prerequisites: We have OpenAI-compatible API and understand the task requirements
- 🔄 JS Client Integration: Ready to submit PR to huggingface.js repository
- 🔄 Model Mapping API: Ready to register our model mappings once enabled
- 🔄 Billing Implementation: Can implement the required billing endpoint API
- 🔄 Python Client Integration: Ready to submit PR to huggingface_hub
- 🔄 Documentation: Ready to create comprehensive provider documentation
Value Proposition for Hugging Face Users
By integrating CometAPI as an inference provider, Hugging Face users will gain:
- Access to 500+ AI models through a single provider
- Competitive pricing with transparent cost structure
- High reliability and low-latency inference
- Regular updates with the latest model releases
- Comprehensive multi-modal capabilities
- Enterprise-grade support and SLA commitments
We believe this partnership will bring significant value to the Hugging Face community by providing broader model access and enhanced AI capabilities.
We would greatly appreciate the opportunity to discuss this partnership further and are ready to begin the technical integration process immediately upon approval.
Thank you for considering our application. We look forward to your response and the possibility of collaborating with the Hugging Face team.
Best regards,
CometAPI Development Team
devpartner@cometapi.com
www.cometapi.com
Ready to revolutionize AI accessibility together? Let's make it happen! 🚀
Partnering on Inference – Qubrid AI (https://platform.qubrid.com)
Hi Hugging Face team and community, 👋
I’m with Qubrid AI, where we provide full GPU virtual machines (A100/H100/B200) along with developer-first tools for training, fine-tuning, RAG, and inference at scale.
We’ve seen strong adoption from developers who want dedicated GPUs with SSH/Jupyter access - no fractional sharing, plus no-code templates for faster model deployment. Many of our users are already running Hugging Face models on Qubrid for inference and fine-tuning.
We’d love to explore getting listed as an Inference Partner with Hugging Face, so that builders in your ecosystem can easily discover and run models on Qubrid’s GPU cloud.
What would be the best way to start that conversation? Is there a formal process for evaluation?
Looking forward to collaborating 🙌
Shubham
Team Qubrid
Dear Hugging Face community,
I'm reaching out from Runware. We provide a high-quality media through a fast, affordable API. We are excited in becoming an official inference provider on Hugging Face Hub.
We are already on the team plan. But still unable to post model mapping as we keep on getting Cannot POST /api/partners/runware/models error.
Kindly let us know the next step to move forward.
Best,
Sirshendu
email: sirshendu.ganguly@runware.ai
Hey there all,
We're Bytez, and we're the largest inference provider on the internet! (We offer inference for 170k+ models.)
We stepped through the integration guide and upgraded to a team account, but are encountering the same issue @sirshendu1997 is encountering.
We also reached out to enterprise-customer@huggingface.co but have not received word back after a few days, so we're trying this avenue.
Please let us know what we need to do to get our integration working. We'd love to be a provider for HF!
Hi,
I'm Charles from Boost Run. We own our compute and operate our data centers, running large clusters equipped with Blackwell, Hopper, and other model GPUs.
Back in 2022-24, I was one of the early engineers on Amazon Bedrock. At the time, the push for dedicated GenAI inference providers was still fairly new. I had a front-row seat to what worked, and what became fragile as things scaled. Our goal is to build a lean and efficient machine, processing the most important workloads in a secure and highly available manner.
I'll be going through the onboarding docs over the coming weeks and am excited to get more familiar with everything. Hopefully this can be the beginning of a strong partnership.
PS. AI is a better writer than myself 😀
Also feel free to reach out to me cr@boostrun.com or can invite to our slack org
Hi Hugging Face team, 👋
I’m with GPT Porto (https://www.gptproto.com/), an AI API platform focused on providing safe, stable, fast, and affordable inference for developers and enterprises. With just one API key, our users can access most mainstream models, including Hugging Face models, while enjoying reliable infrastructure and cost efficiency.
We’ve seen strong adoption from teams who value predictable performance, security, and competitive pricing for both experimentation and production workloads. Many of them already integrate Hugging Face models through GPT Proto to streamline deployment and reduce costs.
We’d love to explore becoming an official Inference Provider on Hugging Face, so that more builders in your ecosystem can benefit from a secure, high-performance, and budget-friendly option for model inference.
Looking forward to collaborating!
Contact us: gptproto@venuslondontechnology.co.uk
Best regards,
Team GPT Proto
Hi Julien would I be able to reach out to you or someone from HF about the API Key management and Billing?
https://huggingface.co/docs/inference-providers/en/register-as-a-provider#4-billing
Thanks,
Boost Run
Prev: https://huggingface.co/spaces/huggingface/HuggingDiscussions/discussions/49#68d564aa7a7e392a927c11f6
Would be great to have Simplismart to the list!
Hi!
Would be great if Snowcell could be added to the list. We build complete inferencing solutions from the ground up.
I couldn't find a specific contact point to reach about this, but for any questions we are available at contact@snowcell.io.
Best Regards
Hello,
At FAIM, we are building an inference platform for time-series foundation models: https://faim.it.com/.
All models we currently support are available on Hugging Face.
I would like to clarify whether it’s possible for us to become an inference provider on Hugging Face for time-series models.
Thank you and best regards,
Andrei
andrei.chernov@faim.it.com
Hi Hugging Face team!
We're gcube (https://gcube.ai), a GPU sharing platform from South Korea. We make AI inference super affordable by connecting idle GPUs from cloud providers and even PC cafes across Korea - basically turning unused computing power into a distributed GPU network.
Our customers are seeing 55-70% cost savings, and we work with major Korean cloud partners like Naver Cloud, NHN Cloud, and KT Cloud.
We'd love to become an official Inference Provider on Hugging Face. Would really appreciate any guidance on the next steps!
Our HF org: https://huggingface.co/gcube-ai (Team plan subscribed)
Thanks!
Best,
Koo
Data Alliance (gcube)
jykoo@data-alliance.com
Hello Hugging Face team 👋
We’re from Simplismart.ai, a Series A startup backed by Accel, building a modular MLOps platform focused on high-performance inference. We’re currently exploring the process of listing our inference APIs as a provider on Hugging Face.
We’ve gone through the inference provider documentation and are preparing for the next steps, but before raising a PR, we’d appreciate some clarity around the billing flow, specifically:
Questions:
- What is the expected delay between a successful inference request and Hugging Face calling the billing endpoint?
- If we’re unable to return cost details within one minute when Hugging Face hits the billing endpoint, does Hugging Face retry the request? If so, what’s the retry behavior?
We want to ensure our implementation aligns closely with Hugging Face’s billing expectations, so any guidance on the above would be very helpful.
Thanks in advance for the support! 🤗
-- Pratik Parmar
Developer Advocate @ Simplismart.ai
pratik@simplismart.tech
Hello Hugging Face team 👋
We are from AlphaNeural AI, an AI infrastructure and inference platform built around one core idea:
Developers should be able to deploy their models and make money from them easily.
AlphaNeural allows model creators to deploy their models on our infrastructure, set licensing or access rules, and monetize usage directly. These deployed models can then be exposed on Hugging Face, while AlphaNeural handles the inference layer with a strong focus on affordability, scalability, performance, and reliability.
We provide inference for LLMs, text, image, video, audio, and multimodal models, optimized for high throughput and low latency, powered by GPU infrastructure that is up to 70% cheaper than traditional cloud providers. This makes it possible for developers to price their models competitively while still earning meaningful revenue.
Our platform is designed to be:
• Developer friendly with simple deployment and API access
• Cost efficient for both creators and users
• High performance and production ready
• Scalable from experimentation to enterprise workloads
AlphaNeural also bridges Web2 and Web3, enabling both traditional subscription based monetization and on chain licensing for models, opening new revenue paths for creators without forcing any Web3 complexity on end users.
We would love to become an official Inference Provider on Hugging Face, enabling model authors to deploy and monetize their models through AlphaNeural, while Hugging Face users access them with fast, affordable, and reliable inference. To maintain high quality, AlphaNeural applies strict technical and operational standards for all deployed models, ensuring strong performance, stability, and production readiness across the platform.
From a technical perspective, we have already completed the full API integration according to Hugging Face’s inference provider specifications, prepared the required interfaces, and have the PR ready for review. We are now simply waiting for approval to move forward.
Happy to share technical details and follow the onboarding process.
We have two PRs ready for review:
https://github.com/huggingface/huggingface.js/pull/1907
https://github.com/huggingface/huggingface_hub/pull/3678
Please reach out to:
contact@alphaneural.io
ash.eryani@alphaneural.io
Looking forward to collaborating 🤗
Team AlphaNeural AI
Hi HuggingFace Team,
We would like to register Mokzu as an inference provider.
Provider Details:
- Organization: Mokzu (https://huggingface.co/mokzu)
- Website: https://mokzu.com
We have submitted PRs to both huggingface_hub and huggingface.js repositories:
- Python PR: https://github.com/huggingface/huggingface_hub/pull/3686
- JavaScript PR: https://github.com/huggingface/huggingface.js/pull/1920
Could you please enable the Model Mapping API for our organization and provide guidance on registering our provider?
Thank you!
Hi HuggingFace team! 👋
We'd like to register Latitude.sh as an inference provider.
About Latitude:
- Recently acquired by Megaport (ASX: MP1), a global Network-as-a-Service leader
- Operating 10,000+ physical servers and 1,000+ GPUs globally
- Combined platform spanning 1,000+ data centers in 26 countries
- Tier-3 data centers with 99.99% SLA
Technical Implementation:
- OpenAI-compatible API at https://api.lsh.ai
- Billing endpoint implemented (POST /api/billing/costs returning nano-USD)
- Inference-Id header in all responses (regular + streaming)
- Full support: tool calling, structured output (JSON mode), vision/multimodal, streaming
Submitted PRs:
- JS Client: https://github.com/huggingface/huggingface.js/pull/1927
- Python Client: https://github.com/huggingface/huggingface_hub/pull/3715
- Documentation: https://github.com/huggingface/hub-docs/pull/2180
HuggingFace Organization: https://huggingface.co/latitude-sh
Logo Assets:
- Light: https://logos-swart.vercel.app/latitude-light.png
- Dark: https://logos-swart.vercel.app/latitude-dark.png
Models Ready for Mapping:
┌──────────────────────────────────────────┬─────────────────────────┬────────────────┐
│ HF Model │ Provider Model │ Task │
├──────────────────────────────────────────┼─────────────────────────┼────────────────┤
│ Qwen/Qwen2.5-7B-Instruct │ qwen-2.5-7b │ conversational │
├──────────────────────────────────────────┼─────────────────────────┼────────────────┤
│ meta-llama/Llama-3.1-8B-Instruct │ llama-3.1-8b │ conversational │
├──────────────────────────────────────────┼─────────────────────────┼────────────────┤
│ Qwen/Qwen2.5-VL-7B-Instruct │ qwen-2.5-vl-7b │ conversational │
├──────────────────────────────────────────┼─────────────────────────┼────────────────┤
│ google/gemma-2-27b-it │ gemma-2-27b │ conversational │
├──────────────────────────────────────────┼─────────────────────────┼────────────────┤
│ Qwen/Qwen3-32B │ qwen3-32b │ conversational │
├──────────────────────────────────────────┼─────────────────────────┼────────────────┤
│ Qwen/Qwen2.5-Coder-32B-Instruct │ qwen2.5-coder-32b │ conversational │
├──────────────────────────────────────────┼─────────────────────────┼────────────────┤
│ deepseek-ai/DeepSeek-R1-Distill-Qwen-14B │ deepseek-r1-distill-14b │ conversational │
└──────────────────────────────────────────┴─────────────────────────┴────────────────┘
Please let us know if you need any additional information or if there are next steps we should follow.
Thank you!
Hey, I've been using inference providers from the CLI and kept running into the discoverability problem others mention here. I ended up building a small Rust CLI/TUI for it https://github.com/jadnohra/hf-providers (brew from tap). I understand it's not a solution, but happy to have eyes on it in case anyone finds it useful.
Hello, HF team / HF community
We're The Compute Factory, a multicloud AI inference platform from France 🇫🇷. We'd like to register as an Inference Provider.
Looking at the current HF inference providers landscape, we see that text-to-image and especially text-to-video are significantly underserved; only a handful of providers cover these tasks today. This is a gap we specifically intend to fill. Our GPU (+other accelerators) infrastructure is well suited for the heavy compute these models demand, and we plan to aggressively expand HF hosted models catalog for image and video generation alongside LLMs.
Our plan is to start with openai/gpt-oss-20B for chat completion, and Lightricks/LTX-2-19B for text to video generation as our first integrations; this lets us establish the end-to-end HF provider pipeline (API, billing, model mapping, PRs). From there, we'll rapidly deploy dozens of additional models across chat completion, text-to-image, and text-to-video.
We're technically ready and can start implementing the HF Inference Provider specs immediately.
HF org: https://huggingface.co/thecomputefactory
PR: https://github.com/huggingface/huggingface.js/pull/1988
We would love any guidance on next steps. Happy to jump on a call.
Best,
The Compute Factory team
chouki@thecomputefactory.com
Hello,
We are a small datacenter company in Germany and have some questions to become a inference partner.
Our questions:
• Can we offer a ocr model as an inference partner?
• How are the scaling limits regulated or can they be adjusted? We cannot serve an infinite number of users.
• Is it acceptable to start with only one model as a partner initially?
Thanks in advanced and best regards
Hello HuggingFace Team,
We would like to add TextCLF as an inference provider.
Provider Details:
Organization: TextCLF(https://huggingface.co/textclf-ai)
Website: https://textclf.com
We have submitted PRs to both huggingface_hub and huggingface.js repositories:
Python PR: https://github.com/huggingface/huggingface_hub/pull/3895
JavaScript PR: https://github.com/huggingface/huggingface.js/pull/2022
Could you please enable the Model Mapping API for our organization and provide guidance on registering our provider?
Email: contact@textclf.com
Thanks,
TextCLF
Hi HuggingFace team,
We’re the team behind Phosor, a GPU inference platform specializing in AI video generation. We’d like to express our interest in becoming a HuggingFace Inference Provider.
About Phosor
Phosor provides high-performance inference for the Wan model family in production, with full support for both Wan 2.1 and Wan 2.2, covering:
- Text-to-Video (T2V) and Image-to-Video (I2V) at 14B scale
- LoRA support — users can upload and apply custom LoRA weights at inference time
- Multi-resolution output — 480p, 720p, and 1080p with configurable frame counts
- On-demand model loading — our service can download and run models on demand
We run dedicated GPU clusters with Ray-based job scheduling, and our RESTful API (/api/v1/inference/submit,/api/v1/inference/status/{request_id},/api/v1/inference/result/{request_id}) follows established async patterns. Our infrastructure is designed for high availability with automatic failover, ensuring stable and reliable service for production workloads.
Pricing
We use a pay-per-use model, priced per frame:
| Resolution | Per Frame | Per Second (24fps) |
|---|---|---|
| 480p | $0.0002 | $0.0048 |
| 720p | $0.0006 | $0.0144 |
| 1080p | $0.0012 | $0.0288 |
LoRA Training: $0.003 per training step (~$1.20 for a typical ~400-step training run)
Lowest price: $0.0002/frame (480p) — significantly lower than comparable providers in the market.
Content Policy
- NSFW content generation: No
- Celebrity / public figure generation: No
Why We Think This Is a Good Fit
The Wan model family has strong presence on HuggingFace Hub, but there is currently no dedicated video generation inference provider. We’ve already invested significant engineering effort into optimizing these models for production — including ComfyUI-based pipelines, LoRA hot-loading, and efficient queue management. Our pricing is among the lowest in the industry — starting from just $0.0002 per frame at 480p, making AI video generation accessible to a much wider audience. Additionally, our platform is built for production-grade stability, with dedicated GPU clusters, automatic failover, and consistent uptime, ensuring reliable inference at scale. Integrating as a provider would give HuggingFace users one-click access to affordable, stable video generation directly from Wan model pages.
Integration Timeline
We’re ready to start immediately — ideally within 1–2 weeks. We’d appreciate guidance on:
- Technical requirements for API adaptation (endpoint specs, auth flow, billing integration)
- Documentation or reference implementations for the provider onboarding process
- Timeline expectations for review and approval
Happy to align our API with whatever specification HuggingFace requires.
Contact
- Website: https://phosor.ai
- Email: hello@aoraki-labs.io
Best,
Aoraki Labs Team
Hi team,
I'm Ben, one of the founding engineers at relaxAI. We're a sovereign AI inference provider hosted on Civo infrastructure, the UK's leading sovereign cloud platform. We'd like to express our interest in becoming a HuggingFace Inference Provider.
About relaxAI
relaxAI provides high-performance, OpenAI-compatible inference for leading open source LLMs. We're currently serving models that are popular across your existing providers, including:
- gpt-oss-120b
- Kimi-K2.5
- Llama 4 Maverick
Our infrastructure runs on Blackwell GPUs through our NVIDIA partnership, and our throughput, latency, and token pricing are very competitive.
What Sets Us Apart
What makes us different from your current provider lineup is that we're fully UK sovereign — 100% UK data residency, processing, and legal jurisdiction. Sovereign AI is a growing priority for UK and European enterprises, particularly in regulated industries, and as far as we can tell there isn't currently a UK-domiciled provider represented in Inference Providers. We think that's a meaningful gap we could help fill.
Integration Readiness
We already have a Hub organisation at huggingface.co/relaxai and we're ready to get started immediately — JS client PR, model mappings, billing endpoint, the lot. Our API is fully OpenAI-compatible, so we'd expect the integration to be straightforward. Happy to provide API access for testing whenever suits.
We'd appreciate guidance on:
- Timeline expectations for review and approval
- Any provider-specific requirements beyond the standard onboarding docs
Contact
- Website: https://relax.ai
- API Docs: https://relax.ai/docs
- Email: ben@relax.ai
Best,
Ben
Founding Engineer, relaxAI
Hi Hugging Face team,
I'd like to introduce StrikeEngine — a new LLM inference provider launching in May 2026 — and express
interest in joining the Inference Providers program. I've read through the register-as-a-provider guide
in the docs and I'm planning to start with the JS client PR per Step 2, since our API is OpenAI-compatible
from day 1.
What we do :
Host AWQ-int4 quantized open-weight LLMs — Qwen, DeepSeek, MiMo, GLM, Llama, Mistral families — on a
hybrid compute architecture (Modal serverless for launch latency + own spot-GPU fleet across AWS/Azure/GCP
for sustained margin). OpenAI-compatible /v1/chat/completions, multi-region failover, SLA monitoring.
the Inference-Id header for the billing endpoint.
Our differentiation
First-responder onboarding of new Chinese-lab open-weight releases — targeting 24-72h from model drop to a
listed endpoint. The current provider lineup has excellent latency specialists (Cerebras, Groq,
Fireworks) and price leaders (Novita), but no one is explicitly focused on the "first-to-list
new-releases" angle. That's the gap we fill. Target catalog: Qwen3.5 / Qwen-Coder-Next, DeepSeek V4+,
MiMo, GLM-4.7+, Kimi-K2+, MiniMax-M2+ — with an automated pipeline detecting releases and onboarding them
within hours.
Why HF Inference Providers
HF is where the open-weights community lives. Our model focus (quantized open-weights from Chinese labs)
aligns exactly with what your community searches for daily. We complement rather than replicate existing
providers by closing the "waiting-for-someone-to-list-the-new-release" gap your buyers currently
experience.
Technical posture toward the 9-step integration
- Step 1 (Task API): OpenAI-compatible — should skip most task-specific work
- Step 2 (JS client PR): happy to open this first as the canonical entry
- Step 3 (Model Mapping): will upgrade to Team Hub plan when we reach this step
- Step 4 (Billing): implementing Inference-Id + cost lookup endpoint natively
- Steps 5-9: will follow in order with PRs to
huggingface_hubandhub-docs - We meet the <5s time-to-first-token requirement by design (hybrid serverless + NVMe-cached spot)
Where we are today
- Landing: https://strikeengine.dev
- Partnerships contact: partnerships@strikeengine.dev
- General: hello@strikeengine.dev
- Launch target: mid-end of May 2026
What I'd like to request
- Whether opening the JS client PR is the right first concrete action, or if there's a preferred order
- Any prerequisites I might have missed
Thanks!
Hicham Abadou
Founder, StrikeEngine
Hi Hugging Face team,
We're Oxlo.ai - an AI inference platform backed by Cyborg Network, featured in STL Partners' "Top 50 Edge Companies 2026." We serve 40+ open-source models (Qwen 3 32B, Llama 3.3 70B, DeepSeek R1, Whisper, SDXL, etc.) via fully OpenAI SDK-compatible APIs.
We'd like to integrate as an Inference Provider on the Hub. Our API is already OpenAI-compatible, so the technical integration should be straightforward.
Why Oxlo.ai is different: We use request-based pricing (flat fee per API call, not per token), which makes us complementary to existing token-based providers on the Hub.
We have 700+ active users across 100+ countries and are ready to begin the technical integration (huggingface.js PR, Python SDK PR, model mappings).
Could you connect us with the right person on your partnerships or developer relations team?
Contact:
- Website: https://www.oxlo.ai/
- Docs: https://docs.oxlo.ai/docs/
- Email: hello@oxlo.ai
Best,
Shashank MS, Oxlo.ai Team
Hey @julien-c we'd like to register as an inference provider and do some co-marketing too; please let me know way forward. We have already done the technical readiness work on our end; www.univars.space targeting to be the first inference provider partner from Africa.
Hi Hugging Face team,
We would like to register Xpersona as a Hugging Face Inference Provider.
Provider
- Provider name: Xpersona
- Hugging Face organization:
xpersona-co - Website: https://xpersona.co
- Docs: https://xpersona.co/docs
- Hosted model card: https://huggingface.co/xpersona-co/xpersona-frieren-coder
- OpenAI-compatible API base: https://www.xpersona.co/v1
- Chat completions endpoint: https://www.xpersona.co/v1/chat/completions
- Public model catalog: https://www.xpersona.co/v1/models
- Public pricing endpoint: https://www.xpersona.co/v1/pricing
- Auth:
Authorization: Bearer <XPERSONA_API_KEY>
Initial Model Mapping
[
{
"hfModel": "xpersona-co/xpersona-frieren-coder",
"providerModel": "xpersona-frieren-coder",
"task": "conversational"
}
]
Model Details
- Display name: Xpersona Frieren Coder
- Provider model id:
xpersona-frieren-coder - Type: hosted proprietary/API model, no open weights
- Inputs: text and image
- Output: text
- Context window: 400,000 tokens
- Max output: 128,000 tokens
- Tool calling: supported
- Structured output: supported
- OpenAI-compatible chat completions: supported
Pricing
- Input: $1.50 / 1M tokens
- Cached input: $0.15 / 1M tokens
- Output: $6.00 / 1M tokens
- Minimum successful request charge: $0.001
Notes
Xpersona is already listed in Models.dev/OpenCode as provider id xpersona, with OpenCode model id xpersona/xpersona-frieren-coder. We can provide any additional endpoint details, billing endpoint shape, JS/Python client implementation, or validation credentials needed for review.
Hi @Wauplin @SBrandeis @julien-c @hanouticelina — opening the registration for UomiRouter as a new inference provider.
UomiRouter is an OpenAI-compatible inference network. Traffic is served by accredited operator nodes that are part of the UOMI network — each operator runs the engine on their own GPU hardware (datacenter or homelab) after a hardware + reliability vetting. Throughput and quality SLAs are guaranteed across the listed catalog. Operators commit to a strict privacy policy (no prompt logging, no training-data collection), payload obfuscation in transit and at rest, and OPoC (Off-chain Proof of Computation): every response is signed by the operator's wallet key and carries a SHA256 of the output (returned as x-wallet-signature / x-wallet-pubkey headers), and a sampled fraction is cross-dispatched to an independent operator for re-verification. The on-chain anchoring layer on UOMI L1 is the next milestone and is not live yet.
The differentiator vs centralized APIs (closed box) and naive decentralized GPU markets (no proof of computation at all) is verifiability today: clients can check off-chain that the operator they were billed for actually produced the tokens they got.
3 PRs already open per the new-provider checklist
- huggingface.js: https://github.com/huggingface/huggingface.js/pull/2193
- huggingface_hub: https://github.com/huggingface/huggingface_hub/pull/4256
- hub-docs (page + sidebar + table + logos): https://github.com/huggingface/hub-docs/pull/2499
Integration details
- Endpoint:
https://gateway.uomi.ai(OpenAI Chat Completions spec; streaming, tool calling, structured output, vision via Qwen3.6-VL all supported) - Billing endpoint live:
POST /partner/hf/billingreturns{requests:[{requestId, costNanoUsd}]}per spec, batched up to 10k. Auth token ready to share via DM. - Per-request
Inference-Idheader: UUID4 emitted on every response. - Org:
uomi-network— Team plan active, ready for the server-side partner-flag flip so we can call/api/partners/uomirouter/modelsfor the staging mappings.
Initial catalog (3 conversational models)
FP8 served internally for the two Qwen models, FP8-Dynamic for Gemma:
| HF model ID | Type |
|---|---|
Qwen/Qwen3.6-27B |
dense |
Qwen/Qwen3.6-35B-A3B |
MoE |
google/gemma-4-31b-it |
VLM |
Contact
info@uomi.ai
Happy to jump on a call or set up a Slack channel for the integration review.
This is a great idea for Wan model inference. By the way, if you ever need to share HTML previews of your AI video outputs, the HTML to URL Converter is super handy for quick sharing without any signup.
Hi @julien-c @Wauplin @SBrandeis @hanouticelina,
We're the team behind Phala and we'd like to formally express our interest in joining the Hugging Face Inference Providers program.
About Phala
Phala (phala.com) is a confidential AI cloud that delivers private LLM inference on hardware-protected GPU infrastructure. Phala runs LLMs on dedicated GPU clusters with hardware-level isolation, providing runtime attestation so users can cryptographically verify that their prompts and outputs were never exposed. Our OpenAI-compatible API gateway at https://api.redpill.ai/v1 gives developers a drop-in replacement for the OpenAI SDK with verifiable privacy guarantees.
We are already a verified inference provider on OpenRouter (openrouter.ai/provider/phala), where we have processed over 2.9 billion tokens across 14 models as of April 2026 — demonstrating production-grade reliability and scale.
Why We're a Strong Fit
Unique Differentiation — Confidential Inference: Phala is the only inference provider in the current HF lineup that offers hardware-attested, confidential GPU inference. For users handling sensitive data, regulated workloads, or privacy-critical applications, this is a meaningful capability gap we can fill.
OpenAI-Compatible API: Our API (/v1/chat/completions, /v1/embeddings) is a full drop-in replacement for the OpenAI SDK — making JS and Python client integration straightforward.
Proven Scale on OpenRouter: Our top models by token volume on OpenRouter:
| Model | Tokens Processed (Apr 2026) |
|---|---|
| Qwen2.5 7B Instruct | 1.03B |
| gpt-oss-120b | 653M |
| Kimi K2.6 | 246M |
| Qwen3.5-27B | 196M |
| GLM 5.1 | 171M |
| Qwen3 VL 30B A3B Instruct | 154M |
| Kimi K2.5 | 114M |
| GLM 4.7 Flash | 113M |
| Gemma 3 27B | 70.1M |
Supported Models & Tasks
We currently serve the following open-weight models on Phala's confidential GPU infrastructure:
| HF Model | Task | Context |
|---|---|---|
| Qwen/Qwen3.5-27B | Chat Completion (LLM) | 256K |
| Qwen/Qwen3.5-397B-A17B | Chat Completion (LLM) | 256K |
| Qwen/Qwen3-VL-30B-A3B-Instruct | Chat Completion (VLM) | 262K |
| Qwen/Qwen2.5-7B-Instruct | Chat Completion (LLM) | 131K |
| google/gemma-3-27b-it | Chat Completion (VLM) | 131K |
| google/gemma-4-31b-it | Chat Completion (VLM) | 262K |
| openai/gpt-oss-120b | Chat Completion (LLM) | 131K |
| openai/gpt-oss-20b | Chat Completion (LLM) | 131K |
| moonshotai/Kimi-K2.6 | Chat Completion (VLM) | 262K |
| moonshotai/Kimi-K2.5 | Chat Completion (VLM) | 262K |
| THUDM/GLM-5.1 | Chat Completion (LLM) | 203K |
| THUDM/GLM-5 | Chat Completion (LLM) | 203K |
| THUDM/GLM-4.7-Flash | Chat Completion (LLM) | 200K |
| THUDM/GLM-4.7 | Chat Completion (LLM) | 200K |
| minimax/MiniMax-M2.5 | Chat Completion (LLM) | 205K |
| Qwen/Qwen3-Embedding-8B | Feature Extraction | 32K |
| sentence-transformers/all-MiniLM-L6-v2 | Feature Extraction | 512 |
Supported Tasks: Chat Completion (LLM), Chat Completion (VLM), Feature Extraction (Embeddings)
Integration Readiness
- Our API is fully OpenAI-compatible, so the JS and Python client integration should be straightforward.
- We have an existing organization on the Hub (huggingface.co/phalanetwork) and are ready to upgrade to a Team/Enterprise plan as required.
- We're prepared to submit the JS client PR, register model mappings via the Model Mapping API, implement the billing endpoint, and follow the full onboarding checklist.
- We can have a working integration ready within 1–2 weeks of receiving guidance.
Contact
- Website: https://phala.com
- API Base URL: https://api.redpill.ai/v1
- OpenRouter Profile: https://openrouter.ai/provider/phala
- Hub Org: https://huggingface.co/phalanetwork
We're happy to provide API access for testing, jump on a call, or align our implementation to any specific requirements. Looking forward to hearing from you!
Best,
The Phala Team
This is a really cool move for UomiRouter! Network reliability is so important for inference. By the way, if you ever need to check your connection stability, you can test packet loss online at packetlosstest.dev. Super handy for ensuring smooth performance.
New Inference Provider — GonkaBroker (gonkabroker)
Hi! We'd like to be listed as an Inference Provider. We route to the Gonka.ai decentralized inference network via an OpenAI-compatible API.
- Org / provider slug: gonkabroker (Team plan active)
- JS client PR: https://github.com/huggingface/huggingface.js/pull/2226 (conversational + text-generation)
- Base URL: https://proxy.gonkabroker.com (/v1/chat/completions, /v1/completions, /v1/models)
- /v1/models exposes per-model pricing (USD/M) + context length for the comparison table / :cheapest.
- Billing API: POST https://app.gonkabroker.com/api/partners/huggingface/billing, Bearer auth, {"requestIds":[...]} → {"requests":[{"requestId","costNanoUsd"}]} (nano-USD).
- Request ID header: Inference-Id on every response.
- Logo (light + dark) ready to send.
Could you enable the org server-side so we can register model mappings? Happy to share the master key for routed traffic over a private channel. Thanks!
Following up on the GonkaBroker provider request above — the JS PR is open and ready for review: https://github.com/huggingface/huggingface.js/pull/2226 (CI awaiting maintainer approval to run). Paid Team plan active, all prerequisites done. Would love help getting it moving.
New Inference Provider integration — deAPI
Hi HF team 👋
We're deAPI (https://deapi.ai, HF org: https://huggingface.co/deAPI-ai) and we'd like to register as an official Inference Provider on the Hub.
deAPI provides an OpenAI-compatible inference API at:
https://oai.deapi.ai/v1
with Bearer token authentication. The endpoint works with the official OpenAI SDK by changing the base_url, and we also maintain a native Python SDK for deAPI workflows.
For the initial integration, we'd like to start with image, audio and embedding tasks:
text-to-image- FLUX.2 Klein 4B BF16
- Z-Anime
- Z-Image-Turbo INT8
- FLUX.1 schnell
image-to-image- FLUX.2 Klein 4B BF16
- Qwen Image Edit Plus
automatic-speech-recognition- Whisper Large V3
text-to-speech- Qwen3 TTS CustomVoice
- Qwen3 TTS VoiceDesign
- Qwen3 TTS VoiceClone
- Chatterbox
- Kokoro
feature-extraction/ embeddings- BGE M3
Exact model slugs, limits and defaults can be resolved through our Model Selection endpoint during the mapping setup.
LLM/chat models are also on our near-term roadmap, and we expect to add conversational / text-generation support shortly after the initial provider setup is live.
We've read the “register as a provider” guide and have already opened the following huggingface.js PR:
https://github.com/huggingface/huggingface.js/pull/2240
The PR starts with text-to-image on a single model in staging. We're also adding a per-response correlation header using Inference-Id with a UUID value, so it can support routed billing and request reconciliation.
One clarification on plan requirements before we finalize the setup. We understand a Team/Enterprise org plan is needed for the Model Mapping API (the routed path). Is the same plan required for a custom-key-only listing (clientSideRoutingOnly, like OpenAI) — where users add their own deAPI key and we bill them directly? We’re considering starting custom-key-only and adding routed billing (dedicated key + reconciliation) in a later phase, so we’d like to understand the plan prerequisites for each path. Thanks!
Happy to continue here or by email if that works better. Thanks!
Request to become an Inference Provider: Umans AI (GLM 5.2 + Kimi K2.7-Code)
Hi HF team 👋
We'd like to list Umans AI as an Inference Provider. We serve open-weight models on our own infrastructure, starting with:
zai-org/GLM-5.2moonshot/kimi-k2.7-code(Kimi K2.7-Code)
On our side:
- HF org
umans-aiis on the Team plan. - We expose an OpenAI-compatible API (
/v1/chat/completions, and/v1/modelsalready servingpricing+context_length), which is the surface HF integrates with, plus an Anthropic Messages-compatible API (/v1/messages). - We've implemented the billing callback (it maps each request id to its cost in nano-USD) and emit a unique
Inference-Idresponse header, per the provider docs. - Ready to open the huggingface.js provider PR and register model mappings as soon as our org is enabled server-side.
Could you point us to the next step to enable the org for the Model Mapping API, and the right contact for the commercial/payout setup?
Public API base: https://api.code.umans.ai
Contact: contact@umans.ai
Thanks!
Hi HF team. We'd love to be added as an inference provider: SCX AI.
We serve sovereign, onshore LLM inference via an OpenAI-compatible endpoint (https://api.scx.ai/v1). We've already followed the register-as-a-provider guide:
Provider id: scx-ai · Org (Team plan): https://huggingface.co/SCXai
JS integration PR: huggingface/huggingface.js#2286
Endpoint verified OpenAI-compatible — chat completions + streaming, plus audio transcriptions (Whisper).
Models:
- MiniMaxAI/MiniMax-M2.7 (conversational, tool calling)
- openai/gpt-oss-120b (conversational, tool calling)
- meta-llama/Llama-4-Maverick-17B-128E-Instruct (conversational, vision)
- google/gemma-4-31B-it (conversational, vision + video-in)
- Qwen/Qwen3-32B (conversational, tool calling)
- openai/whisper-large-v3 (automatic-speech-recognition)
Could you please enable scx-ai server-side so we can proceed with the Model Mapping API? Happy to share anything else you need. Thanks.
Hi, I am Jonah, from Kalanda SAS. We have been a web hosting company for 25 years, and we've recently expanded into AI infrastructure, running production inference on our own DC in France, including open-weight models. We would like to register as an Inference Provider on the Hugging Face Hub. Could you please point us to the next steps, or connect us with the right person to discuss requirements?
Thanks,
Jonah - www.kalanda.net
Hey @julien-c ,
I am from Chutes.ai, a completely open source focused inference provider (even our own code is open).
We'd love to join HF as a inference provider if possible.
Any chance to get onboarded?
You find me here or via florian@chutes.ai or via X DMs at https://x.com/airesearch12.
Thanks
Florian
I am trying to perform an experiment for a research project, and I need access to nvidia/Llama-3.1-Nemotron-70B-Instruct-HF through an inference provider. I do not have the resources to run the model locally. About a week ago, nvidia/Llama-3.1-Nemotron-70B-Instruct-HF was available through the provider featherless-ai. Now, no providers are serving the model. Please help. thanks.
We evaluate provider-routed calls using sanitized, non-sensitive test prompts. Is there a supported per-call field, header, or API that supplies an opaque correlation handle, the exact immutable served-model revision or artifact digest, and a verifiable binding between them (for example, a signed attestation)? Static Hub metadata is insufficient for routed inference. If unsupported, please confirm and identify the feature-request path.
Inference Provider Request: Aster (Kimi K3 + GLM 5.2 + More to come...)
Hi HF team 👋
We'd love to list Aster as an inference provider; we serve open-weight models on our infra.
We currently serve:
- zai-org/GLM-5.2
- moonshotai/Kimi-K3 : Image inputs and conversation endpoints work on our endpoint (image-text-to-text / conversational).
- openai/gpt-oss-120b
We've followed the provider docs and:
- Are registered on the Team plan @ aster-ai.
- Have an OpenAI-compatible API (/v1/chat/completions, and /v1/models already serving pricing + ctx length)
- We've implemented the Inference-Id response header & billing callback
Ready to open the PRs once our organization is enabled.
May you let us know how to enable our organization on the Model Mapping API, and who to contact for the payout setup?
API base URL: https://api.asterlab.ai
Contact: info@asterlab.ai
Thanks 🤗
Hi HF team and @julien-c
We'd love to be added as an Inference Provider: Infersia.
We serve open-weight models on dedicated GPUs through an OpenAI-compatible endpoint (https://api.infersia.com/v1), and we've worked through the register-as-a-provider guide:
Provider id: infersia · Org (Team plan): https://huggingface.co/infersia-com
JS client PR: https://github.com/huggingface/huggingface.js/pull/2343 — BaseConversationalTask, no payload overrides needed; tsc/eslint/oxfmt clean, and both new tests verified against the live endpoint
Inference-Id header on every response, including streaming ones
Billing endpoint implemented and returning integer nano-USD — that is our ledger's native unit, so the figure is exact rather than converted
/v1/models publishes pricing.input / pricing.output in USD per million, plus context_length, for the provider comparison table
Two things we think make us worth a slot rather than just another endpoint:
We serve full context windows. DeepSeek V4 Flash runs at its complete 1,048,576 tokens rather than a truncated slice.
We publish the quantisation. Every endpoint states the precision it is served at, and the hardware behind it. It is the biggest hidden variable in commercial inference and almost nobody discloses it, which is why the same model behaves differently across providers and people blame their own code.
Current catalogue: DeepSeek V4 Flash, Qwen3.6 35B A3B, Qwen3 14B, Qwen3 8B, StepFun Step 3.7 Flash (vision). There is also a free tier — qwen/qwen3-8b:free, no card. More models on the way, but serving these with low ttft and high tps right now.
Could someone enable us server-side so we can start registering model mappings in staging? That is the one step we can't do ourselves.
Happy to provide anything else that would help. Thanks!
— Scott, Infersia
PS: @Wauplin Lucain and @celinah Célina please let us know directly what we can do to make this work from you end. We've got compute and are flexible.
Any inference provider you love, and that you'd like to be able to access directly from the Hub?
Hi! I would be very happy if you would add the NEURALWATT.COM
It is very very cheap
Thanks in advance!!!
Hi @julien-c and the Hugging Face team,
We would like to apply to become a Hugging Face Inference Provider for automatic speech recognition.
Proposed provider ID: vibevoice-asr
Hugging Face organization: https://huggingface.co/vibevoice-asr
Website: https://vibevoice-asr.com
Initial model: microsoft/VibeVoice-ASR
Task: automatic-speech-recognition
Contact: hello@mail.vibevoice-asr.com
We are building a dedicated inference service for VibeVoice-ASR and intend to support Hugging Face Routed Requests.
Implementation is already underway, and we expect to have a staging-ready endpoint, initial pricing, and preliminary performance results available during the week of August 10, 2026.
We are following the official provider registration guide and plan to provide:
- Hugging Face ASR task-compatible input and output handling
- an Inference-Id header for every successful response
- a billing endpoint returning costNanoUsd
- a huggingface.js provider integration, followed by huggingface_hub integration once the Hub integration is operational
- a staging model mapping backed by a publicly reachable endpoint for Hugging Face automated validation
- usage-based pricing calculated from audio duration
We would like to begin the onboarding process early so that we can align our implementation with Hugging Face requirements before our staging endpoint is ready.
We understand that a Team or Enterprise organization plan is required before accessing the Model Mapping API, and we are prepared to upgrade before reaching that stage.
Could you please advise:
- whether our organization can begin the provider onboarding process while the infrastructure is being completed;
- who we should coordinate with for server-side enablement, commercial arrangements, and payout onboarding;
- whether there are any ASR-specific requirements beyond the published provider guide.
We will share our staging endpoint, pricing, performance results, and integration PRs as soon as they are ready.
We are an independent inference provider and are not affiliated with or endorsed by Microsoft.
Thank you!
Dear Hugging Face Team,
I am writing on behalf of Zenlayer to express our strong interest in partnering with Hugging Face as an AI inference provider for your platform.
Zenlayer (https://www.zenlayer.com/) is a leading global edge cloud service provider headquartered in Los Angeles, United States, with offices worldwide. We specialize in delivering ultra-low-latency digital infrastructure and edge computing solutions globally.
By integrating Zenlayer as an AI inference provider, Hugging Face users can benefit from:
- Global Private Backbone Network: Our extensive high-speed dedicated network spans over 300 POPs globally, ensuring secure, high-throughput, and ultra-reliable data transmission.
- Ultra-Low Latency AI Access: By deploying inference workloads closer to end users at the edge, we significantly reduce response times and deliver smooth, real-time AI experiences.
- Scalable Infrastructure: Comprehensive support for high-demand AI workloads across emerging and established markets worldwide.
We would love to discuss potential integration opportunities and explore how we can collaborate to enhance AI deployment for your community.
Please let us know who would be the best point of contact to take this discussion forward.
Best regards,
Zenlayer Team
contact us: zga-admin@zenlayer.com
Hi Hugging Face team,
we'd like to onboard Kosmik Compute as a Hugging Face Inference Provider.
Our initial integration is complete, and we've submitted the huggingface.js provider PR: https://github.com/huggingface/huggingface.js/pull/2378
Kosmik Compute (kosmik)
https://koscompute.com
API: https://api.koscompute.com/v1
We're an EU-based inference provider operating our own GPU infrastructure, with zero data retention, hosted in an ISO-certified data center.
Our initial model is Qwen/Qwen3.8-27B-FP8, served as qwen/qwen3.8-27b, with:
- 262k text / 131k vision context and up to 32k output
- streaming, tools, structured outputs, reasoning and vision
Inference-Id, HF billing integration and/v1/modelspricing/context metadata
We have allocated 4x NVIDIA RTX PRO 6000 GPUs for the HF launch, with capacity to scale to up to 32 GPUs based on demand.
The integration has been validated end-to-end, including streaming, tool calling, strict structured outputs, vision, billing reconciliation and concurrent traffic.
Could you please enable provider ID kosmik server-side so we can create our initial staging model mapping?
We're happy to provide billing credentials or any additional technical or commercial information.
Thanks,
Stanislav Zavadil
Kosmik Compute
stanislav@koscompute.cz
https://koscompute.com
Hi Hugging Face team,
I’m following up on MoonMath.ai’s request to join Hugging Face Inference Providers.
We would like to make Zro, our inference platform, available as a provider through the Hugging Face Hub. Our initial focus is reliable, high-performance text generation and chat inference for open models, served on AMD CDNA3 hardware, including MI300X-class infrastructure.
Zro is built around production inference work in the open ecosystem:
Zro: https://zro.moonmath.ai/
MoonMath: https://www.moonmath.ai/
Our SGLang contributions: https://zro.moonmath.ai/posts/zro-loves-sglang
Our MI300X MLA decode work: https://zro.moonmath.ai/posts/mla-kimi-k2-7-mi300x
GitHub: https://github.com/moonmath-ai/zro-inference
We are particularly interested in integrating with the Hub so users can select Zro as an inference provider for supported models through Hugging Face’s standard inference clients and model pages. We can provide the endpoint, model availability, pricing, billing integration, and any other technical details needed to complete the provider integration.
Could you please point us to the right person or next step for the provider onboarding process? We would also appreciate guidance on which requirements you would like us to complete first.
Thank you,
Otsar Shalmoni
MoonMath.ai / Zro
Hi Hugging Face team,
We would like to begin the onboarding process for VeloInfer as a Hugging Face Inference Provider.
Provider name: VeloInfer
Proposed provider ID: veloinfer
Hugging Face organization: https://huggingface.co/VeloInfer
VeloInfer
VeloInfer is building fast, reliable, and cost-efficient inference infrastructure for open-source AI models.
Initial deployment
Our first release will provide inference for the Qwen3.8 27B model, running on a distributed fleet of:
- NVIDIA GeForce RTX 5090 GPUs
- NVIDIA RTX 6000 GPUs
The service will expose an OpenAI-compatible API with streaming chat completions and usage-based pricing.
Compute infrastructure
VeloInfer is integrating GPU capacity from multiple infrastructure providers, including:
- Vast.ai
- RunPod
- Additional privately operated GPU infrastructure partners
We plan to manage these resources through a unified serving, routing, monitoring, and billing layer to provide consistent API behavior across different GPU environments.
Model roadmap
After the initial Qwen3.8 27B deployment, we plan to expand support to larger models, including:
- Kimi K3
- Qwen3.8 Max
- Additional high-demand open and open-weight language models
Future model availability will depend on model licensing, infrastructure requirements, and technical validation.
Multimodal and generative AI
VeloInfer also plans to support workloads beyond text generation, including multimodal and generative models such as:
- Qwen-Image
- MiniMax H3
- Additional image and multimodal generation models
What we focus on
- Low-latency and high-throughput inference
- OpenAI-compatible APIs
- Streaming responses
- Distributed GPU resource orchestration
- Model routing and scalable serving
- GPU inference optimization
- Transparent usage-based pricing
Hugging Face integration
We are preparing VeloInfer for integration with Hugging Face Inference Providers.
Our public API endpoints, supported model catalog, pricing, performance benchmarks, and documentation will be published as the infrastructure reaches staging readiness.
Status
The initial inference infrastructure and Hugging Face provider integration are currently under development.
Thanks,
Zhihua Song
VeloInfer
RunInfra, request to become an official Inference Provider
Hi HF team, we'd like to register RunInfra as an Inference Provider.
RunInfra (https://runinfra.ai) runs production model APIs at https://api.runinfra.ai/v1: OpenAI-compatible chat completions with streaming and tool calling, per-token billing, prepaid credits, and published per-model pricing. Currently serving DeepSeek V4 Flash, Nemotron 3.5 Lightning 30B, Qwen3.8 2.4T A95B, and Qwen3.8 27B.
Ready on our side:
- Standard conversational task API (OpenAI-compatible chat completions).
GET /v1/modelspublishespricingandcontext_lengthper model.- A billing cost API implementing your per-request cost contract in nano-USD, answerable within your settlement window.
- Provider Hub org on a Team plan: https://huggingface.co/RunInfra, ready for model mappings.
- Provider modules for
huggingface.jsandhuggingface_hubplus the hub-docs provider page are prepared; we'll open the PRs in your preferred order (JS first, per your provider guide).
Happy to provide anything else you need. Contact: jaber@runinfra.ai.
Hi HF team 👋 @julien-c
We'd like to register io.net (IO Intelligence) as an Inference Provider.
Provider ID: io-intelligence · Hub org: https://huggingface.co/ionet-official · API: https://api.intelligence.io.solutions/api/v1 (OpenAI-compatible)
io.net is an enterprise grade GPU network; IO Intelligence is our production inference API on top of it. We're already serving ~30 open models live — DeepSeek V4/R1, Llama 3.3/4, Qwen3.x, Kimi K2.x, GLM 4.x/5, gpt-oss, MiniMax — with streaming, tool calling, structured outputs, and reasoning.
Public GET /v1/models with per-model pricing, context window, precision/quantization, tool and reasoning support, and live latency/throughput stats — we publish the quantization each model is served at
Our model IDs already match HF Hub IDs (e.g. deepseek-ai/DeepSeek-R1-0528, meta-llama/Llama-3.3-70B-Instruct), so mappings will be 1:1
Hi @Wauplin @julien-c ! We would like to be listed as an Inference Provider on the Hub.
LLM Tech — an EU inference provider (registered in Poland, hardware in
Helsinki, Finland). We run open-weight models on dedicated single-tenant
GPUs and tune each deployment ourselves.
Current model: Qwen3.8-27B in NVFP4 on an RTX PRO 6000 Blackwell.
Measured on this deployment: 83 tok/s single-stream, 48 tok/s per request
at 32 concurrent, median TTFT 246 ms under sustained load, GPQA Diamond
78.3%. Endpoint: https://api.llmtech.eu/v1
What is already in place on our side:
- OpenAI-compatible chat completions with streaming, tool calling and
structured outputs - Inference-Id header on every response, including streaming
- Billing API returning per-request cost in nano-USD, idempotent
- /v1/models exposing pricing and context_length in the expected format
- Zero data retention, EU-only processing
Two questions before we go further:
- How do payouts to providers work — schedule, method, any minimums?
- Is there anything you would like to see beyond the integration steps in
the docs before we open the huggingface.js and huggingface_hub PRs?
Artem Burei
LLM Tech — artem@llmtech.eu
Update, one day later: we are now live as a provider on NanoGPT.
LLM Tech is listed on their Qwen3.8-27B page and serving real user
traffic. Numbers from our own logs after the first day:
70 requests from 16 distinct client addresses
411k input tokens, 56k output tokens
0 failures on our side (one 400 from a malformed client request)
0.2s latency on their provider table — the fastest of 11 providers
measured TTFT 0.11s on our side, first token including reasoning
We are the only EU provider on that model, and the only one serving
NVFP4. Prefix caching is live and billed at a reduced cache-read rate.
Everything from my earlier message still stands and is now proven under
real traffic: OpenAI-compatible API, Inference-Id header on every
response, idempotent billing endpoint returning per-request cost in
nano-USD, /v1/models exposing pricing and context length.
Happy to open the huggingface.js and huggingface_hub PRs whenever you
give the word — the provider helper code is written and tested.
Artem Burei
LLM Tech — artem@llmtech.eu
Hi HF team! (cc @Wauplin @SBrandeis @julien-c @hanouticelina)
We'd like to register JetInfer (https://huggingface.co/jetinfer) as an inference provider.
Who we are. JetInfer is an EU-based inference provider (legal entity: Quantive Bt., Hungary), founded by a low-level C++/systems engineer with ~21 years of experience. Our focus is serving open-weight models reliably at the lowest price.
What we serve today. Qwen/Qwen3.8-27B (conversational), OpenAI-compatible, streaming, tool calling and structured output verified live. $0.34 input / $2.55 output per 1M tokens, $0.034 cached input. 150k context. Zero data retention.
Integration status, per the register-as-a-provider guide:
- Task API: strictly OpenAI-compatible chat completions — live at https://api.jetinfer.com/v1 (catalogue: https://api.jetinfer.com/v1/models, health: https://api.jetinfer.com/health)
- Billing endpoint: implemented to spec (nano-USD, idempotent, batches up to 10k IDs) — ready to share the URL + auth privately
Inference-Idheader: on every response, including streaming/v1/modelspricing + context_length: exposed in the documented format- JS helper PR: https://github.com/huggingface/huggingface.js/pull/2402
- Python helper PR: https://github.com/huggingface/huggingface_hub/pull/4724
- Org is on the Team plan; ready for the model-mapping API once our account is enabled server-side
Could you enable our account server-side when you get a chance? Happy to provide anything else you need — test keys, SVG icon, docs page PR.
Thanks!
Richard Nemeth — JetInfer (https://jetinfer.com · https://x.com/jetinfer)
Hello Hugging Face Team,
We would like to add TextCLF as a Hugging Face inference provider.
Provider Details
Organization: TextCLF — https://huggingface.co/textclf-ai
Website: https://textclf.com
TextCLF provides low-cost LLM inference powered by our proprietary TQ 4-bit quantization and CUDA inference stack. A key differentiator of TQ is that it is completely calibration-data-free: it requires no calibration dataset, so the quantization is not optimized around or dependent on the distribution of a particular calibration set. This makes TQ particularly attractive for generalization across domains and workloads beyond a calibration dataset, while achieving fidelity competitive with leading quantization methods.
On Qwen 3.8 27B (WikiText), TQ 4-bit achieves 0.0282 mean KL divergence and 92.4% Top-1% agreement versus the full-precision model, with approximately 4.1× model compression.
Our currently available models and pricing per 1M tokens are:
Llama 3.1 8B Instruct: $0.018 input / $0.038 output
Llama 3.3 70B Instruct: $0.08 input / $0.30 output
Qwen 3.8 27B: $0.30 input / $2.50 output ($0.03 cached input)
Coming soon: DeepSeek V4 Flash 0731 and XiaomiMiMo MiMo V2.5.
We have submitted PRs to both Hugging Face client repositories to add TextCLF provider support:
Python: https://github.com/huggingface/huggingface_hub/pull/3895
JavaScript: https://github.com/huggingface/huggingface.js/pull/2022
Could you please enable the Model Mapping API for our organization and provide guidance on registering TextCLF as an inference provider?
Thanks,
TextCLF Team
Email: contact@textclf.com
Hi! Following up on our provider application for LLM Tech:
- huggingface.js PR: huggingface/huggingface.js#2403
- huggingface_hub PR: huggingface/huggingface_hub#4727 (full test file passing)
Our endpoint has been serving live production traffic since Aug 22 (currently via NanoGPT): 100% uptime, zero failed server requests, and the best measured TTFT among the 12 providers listed for this model there. Live status with measured numbers, refreshed every 5 minutes: llmtech.eu/status
Specs: Qwen3.8-27B (NVFP4 on Blackwell), 262,144-token context, streaming, prompt caching billed at $0.04/M. Zero data retention, EU jurisdiction.
The billing endpoint per the provider spec is implemented and tested. The org is set up (huggingface.co/llmtech); we'll add the Team subscription and register the model mapping as soon as you're ready on your side.
Dear Hugging Face team,
we would like to register Gridmetry as an Inference Provider.
We operate production inference infrastructure in a Tier III+ datacenter in Munich, Germany and expose an OpenAI-compatible API.
Our initial model portfolio includes high-demand open-weight models such as:
- Kimi K3
- DeepSeek V4 Pro 0813
- MiniMax M2.7
- gpt-oss-120B
- Gemma-family models
We are specifically focused on providing high-throughput, cost-efficient dedicated inference capacity for production workloads in Europe.
We would like to add an initial capacity of ~20.18 billion tokens/day
Current benchmark examples include:
gpt-oss-120B: ~713 output tok/s
MiniMax M2.7: ~428 output tok/s / ~690 ms TTFT
Infrastructure is hosted under German/EU jurisdiction with ISO 27001:2022, zero-data-retention support and dedicated production capacity.
Hugging Face organization: Gridmetry GmbH
We would be happy to implement the required billing endpoint, Inference-Id handling, /v1/models pricing metadata and Hugging Face client integrations.
Could you please enable us for provider onboarding / model mappings and let us know the next steps?
Daniel Schade
COO, Gridmetry GmbH
dsc@gridmetry.com
Hi HF team!
We'd like to register Corvex (https://huggingface.co/Corvex) as an inference provider.
Corvex (https://www.corvex.ai) is a US-based AI cloud company; Token Factory is our serverless inference product for open-weight models: OpenAI and Anthropic compatible, with streaming, tool calling, structured outputs and reasoning.
Integration status, per the register-as-a-provider guide:
- Task API: OpenAI and Anthropic compatible chat completions - live at https://api.tokenfactory.corvex.cloud/v1
- Billing endpoint: implemented to spec (nano-USD) - ready to share the URL + auth privately
- Inference-Id header: on every response, including streaming
- /v1/models pricing + context_length: exposed in the documented format
- JS helper PR: https://github.com/huggingface/huggingface.js/pull/2430
- Python helper (huggingface_hub) ready to PR once mappings are live
- Hub org set up; ready for the model-mapping API once our account is enabled server-side
Could you enable our account server-side when you get a chance? Happy to provide anything else required.
Thanks!
Benjamin Shehu
Corvex (https://www.corvex.ai)
Hi Hugging Face team. Boundless would like to onboard as an Inference Provider.
- Name: Boundless
- Proposed provider identifier:
boundless - Hugging Face organization:
BoundlessNetworksInc - API base URL: https://api.inference.boundless.network
- API documentation: https://inference.boundless.network/docs
- Status page: https://status.boundless.network
- API compatibility: OpenAI-compatible
/v1/chat/completions, including streaming, tool calling, and JSON-schema structured outputs
We propose launching initially with these mappings in staging:
- Qwen/Qwen3.6-35B-A3B-FP8
- nvidia/NVIDIA-Nemotron-3-Super-120B-A12B-NVFP4
- zai-org/GLM-5.2-FP8
We have prepared the huggingface.js provider integration and can open the upstream PR once you confirm that boundless is the preferred identifier.
The production service also supports the billing contract:
- Streaming and non-streaming inference responses include a unique Inference-Id.
POSThttps://inference.boundless.network/api/provider/billing accepts request IDs and returns their costsGEThttps://api.inference.boundless.network/v1/models exposes model pricing and context length- Reviewer API keys and the billing endpoint credential can be shared privately
Could you please confirm:
- Whether
boundlessis the correct provider identifier. - Whether
BoundlessNetworksInccan be enabled for provider onboarding and the Model Mapping API. - Whether you would like the huggingface.js PR opened before or after server-side enablement.
- The preferred private channel for reviewer keys, billing credentials, and our SVG provider icon.
Thank you! We’re happy to adjust the initial mappings or integration sequence based on your guidance. 🙏
Hi HF team! (cc @Wauplin @SBrandeis @julien-c @hanouticelina)
We'd like to register Aiqre (https://huggingface.co/Aiqre) as an inference provider.
Who we are: Aiqre (https://aiqre.com) is an EU inference provider, operated by Advanced AI s.r.o., Czech Republic. We serve open-weight models with a focus on models that are in demand but underserved, and we can bring requested models online quickly. Zero data retention: prompts and completions are never stored.
Integration status, per the register-as-a-provider guide:
Task API: strictly OpenAI-compatible chat completions with streaming, tool calling and structured outputs, live at https://api.aiqre.com/v1
/v1/models with pricing and context_length in the documented format: https://api.aiqre.com/hf/v1/models
Inference-Id header on every response, streaming included
Billing endpoint implemented to spec (nano-USD, idempotent, 10k-ID batches) — happy to share the URL and auth privately
JS helper PR: https://github.com/huggingface/huggingface.js/pull/2437
Python helper PR: https://github.com/huggingface/huggingface_hub/pull/4790
Hub org is set up.
Could you enable our account server-side when you get a chance? Happy to provide anything else you need (test keys, SVG icons, a docs page PR).
Thanks!
Tomas
Aiqre (https://aiqre.com)
Hi Hugging Face team! (cc @julien-c @Wauplin @SBrandeis @hanouticelina)
We'd like to register IteraCompute as a Hugging Face Inference Provider.
Who we are. IteraCompute is an Asia-focused AI inference infrastructure provider specializing in cost-efficient serving of newly released open-weight models. Our production OpenAI-compatible API and documentation are live.
Initial conversational model portfolio:
| Hugging Face model | IteraCompute model ID | Context | Quantization | Input / 1M tokens | Cached input / 1M tokens | Output / 1M tokens |
|---|---|---|---|---|---|---|
Qwen/Qwen3.8-27B |
iteracompute/qwen3.8-27b |
327,680 | NVFP4 | $0.30 | $0.03 | $2.50 |
ornith-ai/Ornith-1.5-35B-A3B-NVFP4 |
iteracompute/ornith-1.5-35b-a3b |
327,680 | NVFP4 | $0.30 | $0.03 | $3.00 |
Both models use the conversational task and support OpenAI-compatible Chat Completions, streaming, tool calling, JSON-schema structured outputs, and reasoning. They are served from Asia (China). Prompts and completions are not retained by default.
Current integration status, following the register-as-a-provider guide:
- Production task API:
https://api.iteracompute.com/v1 - Public model catalogue:
https://api.iteracompute.com/v1/models - Production health endpoint:
https://api.iteracompute.com/health/ready - A dedicated HF compatibility gateway has been implemented for
https://api.iteracompute.com/hf, includingInference-Idon streaming and non-streaming responses, HF-format/v1/models, and an idempotent billing endpoint returning per-request cost in nano-USD. This dedicated route is pending production deployment. huggingface.jsandhuggingface_hubprovider helpers are prepared on our integration branches and are ready to be opened as upstream PRs once you confirm the preferred provider identifier and integration sequence.- Initial model mappings are prepared with
stagingstatus.
External production-gateway benchmark (September 1, 2026): one warm-up followed by five measured streaming requests per model, using a 160-token output cap from a single external client. TTFT is measured from request start to the first non-empty content or reasoning delta; output throughput is measured from the first token to stream completion.
| Model | Median TTFT | P95 TTFT | Median output throughput |
|---|---|---|---|
iteracompute/qwen3.8-27b |
0.696 s | 0.709 s | 85.61 tokens/s |
iteracompute/ornith-1.5-35b-a3b |
0.621 s | 0.648 s | 262.22 tokens/s |
Organization and resources:
- Proposed provider identifier:
iteracompute - Hugging Face organization:
IteraCompute - Website:
https://iteracompute.com - API documentation:
https://iteracompute.com/docs.html - Privacy policy:
https://iteracompute.com/privacy.html
We understand that a Team or Enterprise plan is required before Model Mapping API activation and will complete that prerequisite as part of onboarding.
Could you please confirm:
- Whether
iteracomputeis the preferred provider identifier. - Whether the IteraCompute organization can be enabled for provider onboarding and the Model Mapping API once the plan and production-route prerequisites are complete.
- Whether you would like the
huggingface.jsPR opened before or after server-side enablement. - The preferred private channel for test credentials, billing endpoint authentication, our SVG icon, company information, and commercial/provider payout onboarding.
Thank you! We're happy to adjust the initial mappings or integration sequence based on your guidance.
IteraCompute
partnerships@iteracompute.com
Hi Hugging Face team (cc @Wauplin @SBrandeis @julien-c @hanouticelina)
We'd like to register PolarGrid as an Inference Provider.
- Name: PolarGrid, proposed provider id
polargrid - Hub org: https://huggingface.co/PolarGrid
- Website: https://polargrid.ai
- API: OpenAI-compatible
/v1/chat/completionswith streaming and tool calling. Hub traffic will enter at https://hf.polargrid.ai
PolarGrid runs its own hardware in 10 North American cities and routes each request to the nearest one, which is where our latency comes from.
Initial mapping, conversational: Qwen/Qwen3.8-27B to qwen-3.8-27b, proposed in staging.
Ready on our side, per the register-as-a-provider guide:
- Task API live and OpenAI-compatible
- Billing endpoint implemented to spec and deploying this month. URL and auth to follow privately
- huggingface.js provider helper written, pull request to follow once you confirm the id
Happy to share a test key so your team can run the validation suite against the endpoint.
Hello Hugging Face team,
We’d like to add Telnyx as a Hugging Face Inference Provider.
Provider details:
- Organization: Telnyx
- Website: https://telnyx.com
- Inference docs: https://developers.telnyx.com/docs/inference/getting-started/index
- Models: https://developers.telnyx.com/docs/inference/models
- Pricing: https://telnyx.com/pricing/inference-api
Telnyx provides OpenAI-compatible inference on Telnyx-operated GPU infrastructure, with support for chat completions, streaming, function calling, structured outputs/JSON mode, and embeddings.
We’d like to start with conversational model mappings for Telnyx-hosted open-weight LLMs, then add additional supported tasks as appropriate.
Could you advise on the preferred next step for adding Telnyx as a provider and enabling the Model Mapping API for the Telnyx Hugging Face organization?
Thanks,
Telnyx Team
Hi HF team (cc @Wauplin @SBrandeis @julien-c @hanouticelina),
I would like to register BroadNet as an inference provider.
We're a small shop: Dubai HQ, our own GPUs in USA, Jordan, UAE, KSA, and we've been running Arabic-heavy
production for our own customers for a while. Things we bring that are thin on the Hub
right now:
- Arabic speech-to-text that's actually serveable.
CohereLabs/cohere-transcribe-arabic-07-2026
has no provider on the Hub today. It's Apache-2.0 and sits at #2 of 37 on the Open Universal
Arabic ASR Leaderboard (#1 is under a licence that doesn't allow serving it as an API). We also
run the multilingualCohereLabs/cohere-transcribe-03-2026. Both measured at ~45x realtime
single-stream and ~190x batched on Arabic audio, on our hardware. - Qwen3-VL instruct models with vision:
Qwen/Qwen3-VL-30B-A3B-Instruct(int4, pooled
across three boxes) andQwen/Qwen3-VL-8B-Instruct(int8, 78 tok/s single-stream). - Custom Arabic ASR and Vision models: our internal battle tested fie tuned OSS models and LoRAs.
What's ready:
- Provider id
broadnet, Hub org https://huggingface.co/Broadnet - OpenAI-compatible base URL for HF traffic:
https://inference.broadnet.ai/hf— chat with
streaming, tool calling and JSON-schema structured output, and/v1/audio/transcriptionsfor ASR GET /v1/modelson that base withpricing(USD per M) andcontext_lengthInference-Idheader on every response, streams included- Billing endpoint (nano-USD per request id) at
POST /hf/billing/costs, same bearer as inference —
happy to share a test key privately - huggingface.js PR: https://github.com/huggingface/huggingface.js/pull/2445
- Zero data retention, written up at https://broadnet.ai/inference-privacy
Prices: 30B-A3B $0.13 / $0.52 per M, 8B $0.117 / $0.455 per M, Arabic STT $0.0042/min,
multilingual STT $0.002/min.
Could you enable the org server-side so we can register the mappings? We'll start everything instaging and flip to live once your monitor is happy. Logos are ready whenever you want them.
Thanks!
MJ
Hi Hugging Face team,
We’d like to register Bridge as an Inference Provider on the Hub.
Bridge operates cost-efficient OpenAI-compatible LLM inference infrastructure in Asia. Our initial integration would focus on Qwen3.8-27B.
Current production capability:
- OpenAI-compatible /v1/chat/completions
- Streaming SSE
- Streaming and non-streaming usage reporting
- Tool/function calling and automatic tool selection
- Structured JSON outputs
- Authenticated HTTPS API
- Text-only inference
- 70K context / 8K max output
- $0.15/M input / $1.98/M output
- ~651 aggregate output tokens/sec verified at 16 concurrent requests
Website:
https://chyyx.github.io/Bridge-ai/
Privacy Policy:
https://chyyx.github.io/Bridge-ai/privacy.html
We have reviewed the Inference Provider registration guide and are ready to proceed with the huggingface.js integration and the Hugging Face-specific model mapping and billing requirements.
Proposed provider ID: bridge
Could you please confirm whether we should proceed with the huggingface.js PR now, and when you would like us to enable the required Hub organization plan for Model Mapping API access?
Thanks,
JC
Bridge
Hi Hugging Face team!
We’d like to start the process of registering Netra Runtime as a Hugging Face Inference Provider.
- Name: Netra Runtime
- Proposed provider identifier:
netra - Website: https://netraruntime.com
- API base URL: https://api.netraruntime.com/v1
- API documentation: https://app.netraruntime.com/docs
- API reference: https://api.netraruntime.com/docs
- OpenAPI schema: https://api.netraruntime.com/openapi.yaml
- API compatibility: OpenAI-compatible
/v1/chat/completionsand/v1/models - Authentication: Bearer API keys
- Streaming: SSE streaming with
[DONE] - Request identification: Unique
X-Request-Idresponse header - Usage accounting: Input, cached-input, reasoning, and output-token usage
Netra Runtime provides optimized inference for open-weight models across AMD and NVIDIA GPUs. Our focus is high sustained throughput, competitive token pricing, and reliable OpenAI-compatible inference.
Our currently published model is:
deepseek/deepseek-v4-flash-0731- Uncached input: $0.20 per million tokens
- Cached input: $0.05 per million tokens
- Output: $0.50 per million tokens
- Supports streaming and configurable reasoning levels
Could you please confirm:
- Whether
netrais an acceptable provider identifier. - Whether onboarding can begin with chat completions, streaming, and reasoning while tool calling remains unsupported for the initial model.
- Which Hugging Face model mapping you would prefer for our initial DeepSeek route.
- Whether you would like us to open the
huggingface.jsprovider PR before server-side enablement. - The preferred private channel for reviewer credentials and future billing-endpoint credentials.
Once the expected capability scope and initial mapping are confirmed, we can prepare the client integration and remaining provider-specific billing work according to the registration guide.
Thank you!
Farrel
https://netraruntime.com
Hi Hugging Face team,
Following up on our Bridge provider introduction above. Could you advise whether we should proceed directly with a huggingface.js integration PR for the proposed provider ID bridge, or whether your team needs to review our provider eligibility first?
We would also appreciate guidance on the preferred private channel for sharing a test API key and any additional information needed for evaluation.
Our initial integration would focus on Qwen3.8-27B INT4, text-only. We’re happy to follow your preferred onboarding sequence.
Thanks,
JC — Bridge
Hi — we'd like to be listed as an Inference Provider on the Hub.
Heabsy (FEYA s.r.o., Slovakia) serves open models on dedicated GPUs behind an OpenAI-compatible API. Three models today, all NVFP4 with the full 262k context:
| model | hardware | region | $/M in | $/M cached | $/M out |
|---|---|---|---|---|---|
| Qwen3.8-27B | RTX PRO 6000 (Blackwell) | Poland, EEA | 0.05 | 0.08 | 0.20 |
| Qwen3.8-27B Uncensored | RTX PRO 6000 (Blackwell) | Poland, EEA | 0.15 | 0.12 | 0.90 |
| Qwen3.8 Flash-Next (125B MoE, 6B active, text + image in) | B200 | Ashburn, VA | 0.15 | 0.02 | 0.45 |
Inference is zero-retention: prompts and completions are never written to storage — the response cache is switched off in our gateway precisely so that claim is literally true, and we can demonstrate it on our production database rather than just assert it in a policy.
On the prerequisites in the registration guide: our API is strictly OpenAI-compatible, SSE streaming carries usage with the cached-token split, tool calling and JSON-schema structured output both work, reasoning is returned in a separate field, and every response — streaming included — already carries a unique per-request id header, so billing reconciliation has something to key on. Public machine-readable catalogue: https://api.heabsy.com/openrouter/v1/models
We're ready to open the huggingface.js PR and stand up the billing endpoint described in the guide. Two questions before we start: who should we coordinate with, and is there anything you'd want to see first? Happy to hand over a test key.
Konstantin Fomichev — Heabsy / FEYA s.r.o.
Hi Hugging Face team (cc @julien-c @Wauplin @SBrandeis @hanouticelina)
We'd like to register SolarGPU as an Inference Provider on the Hub.
- Name: SolarGPU, proposed provider id
solargpu - Hub account: https://huggingface.co/solargpu (organization with Team plan to follow at step 3)
- Website: https://solargpu.es · privacy & retention: https://solargpu.es/privacidad · terms: https://solargpu.es/terminos-api
- Who we are: a Spanish company (Acceleration Robotics S.L.U.) running solar-powered GPU nodes in Spain. We serve open-weight models from our own NVIDIA RTX PRO 6000 Blackwell (96 GB) cards — one dedicated today, expandable to five across two nodes (480 GB VRAM) — with EU data residency and zero data retention (prompts and completions are not stored; billing metadata only; no training on customer data).
- API: OpenAI-compatible
/v1/chat/completionswith streaming,usageon every response, tool calling and structured outputs; served with vLLM 0.29 behind a LiteLLM gateway. Hub traffic would enter athttps://api.solargpu.es/v1(live;https://api.solargpu.es/modelspublishes the catalogue with pricing and context length). - Initial mapping,
conversational:openai/gpt-oss-120b→gpt-oss-120b,Qwen/Qwen3.6-35B-A3B→qwen3.6-35b-a3b,nvidia/NVIDIA-Nemotron-3-Super-120B-A12B-BF16→nemotron-3-super-120b(nvfp4),NousResearch/Hermes-4-70B→hermes-4-70b(fp8); proposed instaging. On the full node we can adddeepseek-ai/DeepSeek-V4-Flash-0731andzai-org/GLM-5.3-Flash. - Pricing: we keep our list prices at or below the current floor for these models (USD per M tokens, input / output): gpt-oss-120b 0.03 / 0.17, Qwen3.6-35B-A3B 0.05 / 0.70, Nemotron 3 Super 0.08 / 0.38, Hermes 4 70B 0.12 / 0.38.
/v1/modelswill exposepricingandcontext_lengthas required. - Ready on our side, per the register-as-a-provider guide:
- Task API OpenAI-compatible; TTFT well under 5 s at our concurrency; tool calling and structured output supported (vLLM).
- Billing endpoint to your spec (cost in nano-USD, polled per minute) — implemented with the test endpoint; URL and auth to follow privately.
huggingface.jsprovider helper — pull request to follow once you confirm the id.
- Timeline: the endpoint is live now; a test key for your validation suite on request; 1 GPU dedicated at launch, up to 5 on demand.
Why us: most floor-price endpoints for open-weight models are outside the EU. We offer EU residency with zero retention at floor prices, from solar-powered hardware in Spain.
Happy to share a test key so your team can run the validation suite against the endpoint, and to discuss the Team plan for the org as part of step 3.
Thanks!
SolarGPU team
Org: Least-gen (leastgen), Team, want provider "leastgen" for Qwen/Qwen3.8-27B, api.leastgen.com OpenAI-compatible, contact khalid@leastgen.com,
Hi Hugging Face team — following up on our September 1 application with a production update for IteraCompute (cc @julien-c @Wauplin @SBrandeis @hanouticelina).
Our dedicated Hugging Face compatibility gateway is now live:
- Base URL: https://api.iteracompute.com/hf
- Model catalogue: https://api.iteracompute.com/hf/v1/models
- Readiness: https://api.iteracompute.com/hf/health/ready
- Chat Completions: POST https://api.iteracompute.com/hf/v1/chat/completions
- Billing: POST https://api.iteracompute.com/hf/v1/billing (credentials available privately)
The initial HF onboarding catalogue remains:
- Qwen/Qwen3.8-27B — 327,680 context; $0.30/M input, $2.50/M output
- ornith-ai/Ornith-1.5-35B-A3B — 327,680 context; $0.30/M input, $3.00/M output
Both initial routes have passed non-streaming, streaming, tool-calling, strict JSON-schema output, Inference-Id, and billing acceptance. Billing validation included idempotent per-request settlement, pending-request handling, a 10,000-ID batch, and exact nano-USD price reconciliation.
Our broader production catalogue has also expanded to nine ready models. In addition to the two initial routes, the following are available as candidates for staging model mappings after onboarding:
| Hugging Face model | Context | Input / 1M | Cached input / 1M | Output / 1M |
|---|---|---|---|---|
| zai-org/GLM-5.3-Flash | 1,048,576 | $0.12 | $0.02 | $0.48 |
| deepseek-ai/DeepSeek-V4-Flash-0731 | 970,000 | $0.35 | $0.03 | $1.30 |
| deepseek-ai/DeepSeek-V4-Pro-0813 | 1,048,576 | $1.10 | $0.11 | $3.50 |
| MiniMaxAI/MiniMax-M3 | 1,048,576 | $0.40 | $0.08 | $1.60 |
| moonshotai/Kimi-K3 | 1,048,576 | $3.10 | $0.31 | $15.50 |
| Qwen/Qwen3.8-2.4T-A95B | 970,000 | $1.95 | $0.20 | $5.95 |
| zai-org/GLM-5.3 | 1,048,576 | $1.50 | $0.23 | $6.20 |
The public machine-readable catalogue with per-model capabilities is available at https://api.iteracompute.com/v1/models.
Client integration status:
- huggingface.js PR: https://github.com/huggingface/huggingface.js/pull/2440 — open; its fork workflows are awaiting maintainer approval to run.
- huggingface_hub coordination issue: https://github.com/huggingface/huggingface_hub/issues/4795
- huggingface_hub Draft PR: https://github.com/huggingface/huggingface_hub/pull/4794 — automatically closed pending maintainer agreement in the issue, as required by that repository's contribution process.
Could you please confirm the provider identifier iteracompute, advise which models you would prefer in the initial mapping set, and enable the IteraCompute organization for provider onboarding and the Model Mapping API when appropriate? We are ready to activate the required organization plan at that step and can provide rotated test and billing credentials privately.
Thank you,
IteraCompute
Hi Hugging Face team,
we are preparing SovSales Inference, an independent OpenAI-compatible inference provider for open-weight models.
Our provider gateway implements OpenAI-compatible chat completions, streaming, token usage reporting, model metadata, bearer authentication, request IDs, rate limiting and a published privacy/data policy. Production GPU-backed serving is currently being staged and will be validated before any model is marked live.
Provider profile:
https://sovereignsalesswarm.de/inference/
API base:
https://sovereignsalesswarm.de/api/inference/v1
Models:
https://sovereignsalesswarm.de/api/inference/v1/models
We would like to integrate SovSales as a Hugging Face Inference Provider. Could you enable our organization for the provider integration process and confirm the next onboarding steps, including the Team or Enterprise requirement?
Organization:
https://huggingface.co/sovsales
Best,
SovSales Inference
info@sovereignsalesswarm.de
Hi HF team (Cc. @julien-c @Wauplin @sbrandeis )👋
We'd like to register IntelCS-AI as an Inference Provider. We serve
open-weight models at floor prices — our edge is cost: we run efficient
GPU fleets and pass the savings through as some of the lowest per-token
prices on the platform.
What's already built and live (per the register-as-a-provider guide):
- OpenAI-compatible inference endpoint (live, bearer-token auth):
/v1/chat/completions(streaming + non-streaming). Endpoint URL and
credentials provided in the private exchange. - Tool calling + structured output verified end-to-end
(json_schemaresponse_format) — vLLM 0.9.2 backends. /v1/modelswith the full expected shape —id,object,created,owned_by,pricing($/1M tokens),context_length— so
the comparison table and:cheapestselection work out of the box.- Billing endpoint implemented to your spec:
POST /billing/costs, batchedrequestIds→ integercostNanoUsd,
idempotent, per-request price snapshot at serve time. Inference-Idheader (UUID) on every response, including
streaming.- Latency: TTFT ~0.9 s non-streaming (well under the 5 s budget);
- Autoscaling fleet with health checks and automatic scale-out.
- Hub org: IntelCS-AI —
Team plan, org card published.
Initial model (ready to map, task conversational):
| HF model | Our price /1M (in/out) | Context |
|---|---|---|
google/gemma-3-4b-it |
$0.05 / $0.10 | 131,072 |
The lineup rotates as we add capacity — we'll keep mappings in sync.
What we need from you:
- Server-side enablement for org
IntelCS-AI, provider slugintelcs-ai-iaas. - Token exchange — we'll provide our bearer token(s) for inference
- billing calls (we can rotate fresh ones for production).
- Confirmation of the
Inference-Idheader name.
Once enabled, we'll register the model mapping viaPOST /api/partners/intelcs-ai-iaas/models and open thehuggingface.js + huggingface_hub PRs.
Happy to share anything else you need — thanks!
Brad (IntelCS-AI · intelcs.ai)
Hi Hugging Face team,
We operate a Compute as a Service (CaaS) platform, providing customers with on-demand access to high-performance compute infrastructure, including GPU capacity, without the need to own or manage the underlying hardware.
We are headquartered in the UK and have recently expanded our compute capacity into the US and Canada. We are interested in registering as an inference provider on Hugging Face and exploring how our infrastructure could support inference workloads through the Hugging Face platform.
We would appreciate it if someone from the relevant team could get in touch to discuss the registration process and requirements.
Kind Regards,
Mariami
Hey! I'm the founder of Kitani an inference API provider serving open source LLMs. We're interested in becoming an official Hugging Face Inference Provider and routing HF inference traffic through our infrastructure.
We already have an OpenAI compatible API and production inference infrastructure. @Wauplin @julien-c , would either of you be able to point me to the right person to coordinate a provider integration with?
Thanks!
My emails admin@kitani.ai
Hi Hugging Face team,
We would like to register as a Hugging Face Inference Provider.
We operate a GPU-backed OpenAI-compatible inference gateway and would like to make GLM-5.3 available through Hugging Face Inference Providers.
Provider information:
- Proposed provider name: Yuxuan
- Model: zai-org/GLM-5.3 / GLM-5.3
- API Base URL: https://api.chunheaj.top/v1
- Models endpoint: https://api.chunheaj.top/v1/models
- Chat Completions endpoint: https://api.chunheaj.top/v1/chat/completions
- Supported task: conversational
- Supported features: chat completions, SSE streaming, token usage reporting, OpenAI-compatible request/response format
- Initial capacity: conservative concurrency of 4 requests to maintain stable latency and reliability
We can provide private test API credentials for validation and are ready to coordinate on the next steps, including the required provider organization setup, model mappings, billing endpoint, and client integration.
Could someone from the Hugging Face Inference Providers team confirm the next onboarding steps and the correct person to coordinate with?
For private coordination and test credentials, please contact us at: gaoja2026@gmail.com
Thank you.
Hi Hugging Face team,
Apres Dynamics (huggingface.co/ApresDynamics) for embeddings, reranking, classification, and light generation.
We saw the note on PR #2491 about the consolidation phase. Are you currently accepting new Inference Provider partners, and is there a waitlist we can join?
Thanks,
Michael Lewis
@ApresDynamics
michael@apresski.ai
Hi Hugging Face team,
We are working on register as provider for our own models, we have questions about model serving provider registration process, we would appreciate it if someone from the relevant team could get in touch to discuss the registration process and requirements.
We'd like to register BosonAI as an Inference Provider for text-to-speech. BosonAI trained and publishes both models — we're the original model developer, not a third-party inference reseller, so our serving stack is built and tuned specifically for this architecture.
Provider details:
- Name: BosonAI, proposed provider id
bosonai - Hugging Face organization: https://huggingface.co/bosonai
- Website: https://boson.ai
Initial models, task text-to-speech:
Both models are already deployed and serving production traffic on our own infrastructure
at https://api.boson.ai/v1/audio/speech.
Current status against the register-as-a-provider guide:
- Task API: live in production; not yet in HF's text-to-speech input/output schema —
happy to either adapt on our side or provide the mapping for a huggingface.js provider
helper, whichever you prefer. - Billing endpoint: implementing now (Inference-Id header + idempotent cost-in-nanoUSD
endpoint per spec). - huggingface.js integration: not yet started, pending your guidance on provider id and
sequencing.
Thank you!
Best,
Bang Liu
@BosonAI
bang@boson.ai
Hello! I’m representing Nagame (https://huggingface.co/nagameai), and we’d like to onboard as an Inference Provider.
Our OpenAI-compatible API supports streaming, tool calling, and structured output.
API: https://api.nagame.ai
Models and pricing: https://api.nagame.ai/v1/models
Billing: https://api.nagame.ai/integrations/huggingface/billing
Request-ID header: Inference-Id
Our initial provider model IDs are qwen3.8-27b and qwen3.6-35b-a3b. We would prefer to start validation with Qwen3.8 while including both models in the integration.
Both passed our live functional and billing checks. We plan to submit the JavaScript SDK integration.
Could you advise on onboarding, organization plan requirements, server-side enablement, and secure credential exchange? Our proposed provider slug is nagame.
Quick update on Nagame: we have now completed the initial huggingface.js integration and opened the upstream PR:
https://github.com/huggingface/huggingface.js/pull/2512
The implementation and tests are ready, and direct API smoke tests are passing.
We are ready to proceed with the next onboarding steps. Please let us know if we should upgrade the nagameai organization to Team now for Model Mapping API enablement, and how you would like us to securely provide the provider credentials.
cc @julien-c @Wauplin @sbrandeis
contact@nagame.ai
Thanks!
Hi Hugging Face team 👋
We're Inferway, an OpenAI-compatible inference API running on our own GPUs, and we'd like to join Inference Providers.
Model
- XiaomiMiMo/MiMo-V2.6-Flash-RL →
inferway/mimo-v2.6-flash(conversational) - 393K context · $0.14 / $0.28 per 1M input / output tokens
Ready on our side
- OpenAI-compatible chat completions, JSON and streaming
- An
Inference-Idheader on every response, and a billing endpoint that follows your spec - Pricing and context length on
/v1/models - Checked against your validation criteria: about 0.8 s streaming TTFT, tool calling and structured output work
- huggingface.js PR: #2540
Next step
We've created the inferway org and will upgrade it to Team. Could you enable us server-side so we can register the model mapping? We can share a review key privately.
cc @julien-c @Wauplin @SBrandeis @celinah
Thanks!
Inferway · hello@inferway.ai
Inference Provider request: BaliLLM (Bali Tower) — DeepSeek-V4-Pro-0813 and GLM-5.3
Hi @Wauplin @julien-c and the Hugging Face team,
We're Bali Tower (PT Bali Towerindo Sentra Tbk, IDX: BALI), an Indonesian telecom infrastructure company. We run BaliLLM, an OpenAI-compatible inference API on our own NVIDIA B300 (Blackwell Ultra) GPUs in Indonesia, and we'd like to register as an Inference Provider (balillm), starting with two models. As far as we can tell, we'd be the first provider on the Hub serving from Southeast Asia.
Models
| Model | HF repo | Serving precision | Context |
|---|---|---|---|
| DeepSeek-V4-Pro-0813 | deepseek-ai/DeepSeek-V4-Pro-0813 |
Original checkpoint weights, FP8 KV cache, DSpark speculative decoding | 1M tokens |
| GLM-5.3 | zai-org/GLM-5.3 |
NVFP4 with FP8 dense layers (NVIDIA ModelOpt checkpoint), FP8 KV cache, MTP speculative decoding | 1M tokens |
Each model runs on a dedicated 8× NVIDIA B300 node with SGLang. We publish precision and context length per deployment.
API
OpenAI-compatible /v1/chat/completions and /v1/models (with pricing and context_length). Streaming with usage in the stream, tool calling, structured outputs, and separate reasoning_content. Unique request-ID header on every response. Billing endpoint returning integer nano-USD per request, idempotent.
Validated end-to-end on our serving nodes: streaming (usage in the final chunk, including reasoning tokens), tool calling (streaming and non-streaming), strict JSON-schema structured outputs, separate reasoning_content, retrieval across the full 1M context, sustained concurrent traffic (up to 64 sessions, 0 errors), and billing reconciliation through the gateway (request-ID header, idempotent billing endpoint, 10k-ID batches).
Measured performance
SemiAnalysis InferenceX agentic workload: aiperf harness plus real coding-agent traces, real speculative-decoding acceptance.
| Model | Concurrent sessions | TTFT p50 / p90 | Output speed per user |
|---|---|---|---|
| DeepSeek-V4-Pro-0813 | 48 | 1.1 s / 3.9 s (1-hour run) | ~58 tok/s |
| DeepSeek-V4-Pro-0813 | 1 | 0.9 s | ~210 tok/s |
| GLM-5.3 | 32 | 0.8 s / 3.5 s | ~46 tok/s |
| GLM-5.3 | 1 | 1.0 s | ~130 tok/s |
Quality: GPQA Diamond (simple-evals, thinking mode) 90.7% for DeepSeek-V4-Pro (4 runs) and 86.4% for the GLM-5.3 NVFP4 build (1 run). Needle-in-a-haystack validated to the full 1M context for both: 25/25 at 20k–200k, 5/5 at ~500k and 5/5 at 1M tokens.
Capacity
One dedicated node per model at launch, up to 48 concurrent requests per key (HTTP 429 above that). We'll add capacity with demand.
More models will follow as we add capacity; we'll open a mapping request for each one.
Pricing
Pricing published via /v1/models; details shared privately during onboarding.
Status
Hub org on the Team plan: https://huggingface.co/balillm-org. Requested provider ID: balillm. huggingface.js provider PR: https://github.com/huggingface/huggingface.js/pull/2558 (per the guide; huggingface_hub and hub-docs PRs to follow). No prompt or completion storage; all processing in Indonesia.
Request
Could you enable provider ID balillm server-side so we can create staging model mappings? We'll share the endpoint, test keys, billing credentials and payout details privately with whoever handles onboarding, and we'd appreciate a contact for payout setup. Happy to run any validation or evaluation you need before listing.
Contact: HF @balillm-team (email available privately during onboarding)
Thanks!
Independent inference provider — questions before registering
Hi! I'm planning to become an Inference Provider for open-weight LLMs that currently have few or slow providers on the Hub. My setup: vLLM on dedicated GPUs (all in the US), behind an OpenAI-compatible gateway that returns an Inference-Id header on every response (including streaming), exposes pricing and context_length on /v1/models, and implements the billing endpoint as described in the "Register as an Inference Provider" guide.
Before upgrading my org to a Team plan, I'd like to confirm a few things:
- Eligibility: do you accept independent providers that serve open-weight models on rented GPU capacity (not owned datacenters)? Any minimum requirements (SLA, number of models, company registration)?
- Payouts: how are providers paid for routed requests — full listed price or a revenue share? What currency, payout frequency, minimum payout and required tax/invoicing documents (I'm based in Brazil)?
- Throughput measurement: how is the
throughputshown inrouter.huggingface.co/v1/modelsmeasured — per request (single stream) or aggregated? With what prompt/output length, how often, and from which region? This is what:fastest/ default routing uses, so I want to size my deployments against it. - Behavioural tests: could you share the prompts, tool definitions and JSON schemas used in the automatic tool-calling and structured-output tests, so I can reproduce them before creating a mapping?
- Validation status: is there an API (or a page) to see the result of the automatic validation for each mapping, or only whether the provider appears as live?
- Request ID header: is
Inference-Idfine as the header name, or do you prefer another one? - Staging before Team plan: is it possible to test a staging mapping before the org is upgraded, or is the Team plan required from the first mapping?
Thanks!
We're ScitiX, an OpenAI-compatible inference API running on our own GPUs, and we'd like to join Inference Providers.
Model
- deepseek-ai/DeepSeek-V4.1-Flash → deepseek-ai/deepseek-v4.1-flash (conversational)
1M context · $0.30 / $1.20 per 1M input / output tokens
Ready on our side
- OpenAI-compatible chat completions, JSON and streaming
- An
Inference-Idheader on every response, and a billing endpoint that follows
your spec (POST /v1/partner/huggingface/request-costs) - Pricing and context length on /v1/models
- huggingface.js PR: https://github.com/huggingface/huggingface.js/pull/2575/changes
Next step
We've created the scitix-future org and upgraded it to Team.
Could you enable us server-side so we can register the model mapping?
We can share a review key privately.
cc @julien-c @Wauplin @SBrandeis @celinah
Thanks!
ScitiX
- Business: Anne Hu anne.hu@scitix.ai
Hi, I'm having an issue when trying to use Codex with the Inference Providers API, and it says that the payload is too large, even when starting from a fresh message.
I’m using the configuration from the official Codex integration guide here: https://huggingface.co/docs/inference-providers/en/integrations/codex
- Codex CLI: 0.159.2
- Model: zai-org/GLM-5.3
- Base URL: https://router.huggingface.co/v1
- wire_api: responses
A fresh session’s first request fails with an HTML error response:
<html lang="en">
<head>
<meta charset="utf-8">
<title>Error</title>
</head>
<body>
<pre>PayloadTooLargeError: request entity too large<br> at readStream (/home/node/app/node_modules/.pnpm/raw-body@2.5.2/node_modules/raw-body/index.js:163:17)<br> at getRawBody (/home/node/app/node_modules/.pnpm/raw-body@2.5.2/node_modules/raw-body/index.js:116:12)<br> at read (/home/node/app/node_modules/.pnpm/body-parser@1.20.3/node_modules/body-parser/lib/read.js:79:3)<br> at jsonParser (/home/node/app/node_modules/.pnpm/body-parser@1.20.3/node_modules/body-parser/lib/types/json.js:138:5)<br> at Layer.handle [as handle_request] (/home/node/app/node_modules/.pnpm/express@4.21.2/node_modules/express/lib/router/layer.js:95:5)<br> at trim_prefix (/home/node/app/node_modules/.pnpm/express@4.21.2/node_modules/express/lib/router/index.js:328:13)<br> at /home/node/app/node_modules/.pnpm/express@4.21.2/no..., url: https://router.huggingface.co/v1/responses
Is there a workaround or fix you're aware of? Thanks!
Hi Hugging Face team,
we are evaluating Flonno as an Inference Provider.
Flonno operates part of its inference capacity on GPUs that we manage ourselves, while some text Chat Completion workloads may also be routed to external inference infrastructure through an OpenAI-compatible gateway, depending on the model and available capacity.
We offer scoped API keys, streaming responses, and reported token usage.
Before we invest in SDK PRs, model mappings, and the required billing endpoint, we would like to confirm whether this hybrid supply model is compatible with the Hugging Face Inference Providers program, and what evidence or documentation you would require regarding the models, infrastructure, and operators involved.
Website: https://www.flonno.com
Integration examples: https://www.flonno.com/integrations
Best regards,
Flonno
Hi Hugging Face team 👋 We're SOKKAN (NINABOT Sàrl, Geneva, Switzerland, https://huggingface.co/sokkan), an OpenAI-compatible inference API served from Switzerland, and we'd like to join Inference Providers.
Why it's useful for Hub users: a Swiss-hosted, zero-retention option (prompts and completions are never logged or stored, never used for training) for open-weight models. Terms and DPA: https://sokkan.ch/en/api/ · https://sokkan.ch/en/api/dpa/
Ready on our side
- huggingface.js PR: https://github.com/huggingface/huggingface.js/pull/2594 (8 tests passing)
- Base URL:
https://api.sokkan.ch/hf→/v1/chat/completions, streaming with usage, tool calling, structured outputs Inference-Idheader on every response, including streaming- Billing endpoint:
POST https://api.sokkan.ch/hf/v1/billing(requestIds→costNanoUsd, idempotent) - Pricing and context length:
https://api.sokkan.ch/hf/v1/models
Initial models (conversational)
openai/gpt-oss-20b→openai/gpt-oss-20b· $0.04 / $0.15 per 1M input / output tokensQwen/Qwen3-Coder-30B-A3B-Instruct→qwen/qwen3-coder-30b-a3b-instruct· $0.07 / $0.27
We're adding the Qwen 3.6 / 3.8 family next. Happy to upgrade the sokkan org to Team when you're ready to enable the Model Mapping API. Thanks!
Hi Hugging Face team 👋
We're ZeroGPU (https://zerogpu.ai). We run fast, low-cost inference on an edge network through an OpenAI-compatible API, and we'd like to join Inference Providers.
- Provider ID:
zerogpu - Hub org: https://huggingface.co/ZeroGPU (Team plan)
- API base URL:
https://api.zerogpu.ai/v1 - Contact: hello@zerogpu.ai
Models we'd start with (chat completions):
- openai/gpt-oss-120b
- deepseek-ai/DeepSeek-V4.1-Flash
- Qwen/Qwen3-30B-A3B-FP8
- Qwen/Qwen3.6-35B-A3B
- zai-org/GLM-5.3-Flash
Our chat completions API already follows the OpenAI format, with streaming and tool calling. We're now adding the rest of what your guide asks for: an Inference-Id header on every response, the billing endpoint, and /v1/models with pricing and context length. We'll open the huggingface.js PR soon.
We also serve task-specific models, including an IAB content classifier, a moderation model and embeddings. We'd like to know whether these could be listed later, for example under text classification and feature extraction.
Happy to get on a call. Who's the best person to coordinate with?
Thanks!
Hi Hugging Face team,
I'm Hema from RainDragon (https://inference.raindragon.ai). We run an OpenAI-compatible inference API serving Gemma 4, and we'd like to be listed as an Inference
Provider on the Hub. Our Hub organization is raindragonai (https://huggingface.co/raindragonai), and it's already on the Team plan.
We've worked through your provider guide, and our API already supports the following:
- OpenAI-compatible
/v1/chat/completions, streaming and non-streaming - Model IDs that match the Hub:
google/gemma-4-26B-A4B-itandgoogle/gemma-4-31B-it /v1/modelswithpricing(USD per million input and output tokens) andcontext_length- An
Inference-Idheader (UUID) on every response, including streaming responses - A billing endpoint that takes
{requestIds}and returns{requests: [{requestId, costNanoUsd}]}. It uses the same bearer auth as inference,
is idempotent and returns costs as soon as a request completes. - Streaming time to first token of about 2.4s at P90 under concurrent load, well under your 5s limit
- Prompt caching, with cached input at $0.03 per million tokens. Our existing customers see strong cache hit rates.
- Inference runs in the US
What we plan to do next:
- Open the provider PR on huggingface.js. We follow the OpenAI API, so it should be a small change.
- Register model mappings for both models from the raindragonai organization, starting in staging.
Is there anything else you need from us before we start, and who should we work with on the server-side registration?
Thanks,
Hema (hema@raindragon.ai)
RainDragon.ai
Update from SOKKAN (Geneva, Switzerland), following our request above: we'd like to add the Swiss open models to our initial list.
swiss-ai/Apertus-v1.5-8B: no Inference Provider on the Hub today. Benchmarked on 1×H100 (vLLM, swiss-ai release image, BF16): 1,763 output tok/s in aggregate at 32 concurrent requests (59 tok/s per user, TTFT 0.58 s). Tool calling andjson_schemastructured outputs work.swiss-ai/Apertus-v1.5-70B: one provider today. We benchmark it on NVIDIA RTX PRO 6000 Blackwell in Zurich on Monday and will post the numbers here.
Apertus is the open model from EPFL, ETH Zurich and CSCS. We would serve it from Switzerland with zero retention (DPA: https://sokkan.ch/en/api/dpa/). Both can be live within days of being enabled for us. Thanks!
Hi Hugging Face team!
We’re CoralBricks and would like to join Inference Providers.
We serve GLM 5.3, GLM 5.3 Flash and DeepSeek V4.1 Flash on our own GPUs through an OpenAI-compatible API, with streaming, tool calling, 1M-token context and $0 cached-input reads. Cache-write rates are listed separately.
Our production measurements show 469 output tokens/s for DeepSeek V4.1 Flash and 254 for GLM 5.3 Flash. These are observed speeds from our own serving.
- Org: https://huggingface.co/coral-bricks-ai
- Docs: https://www.coralbricks.ai/docs
- Pricing: https://www.coralbricks.ai/pricing
Who should we coordinate with on onboarding and server-side registration?
Hi Hugging Face team 👋
We’re Reka AI (https://huggingface.co/RekaAI). We build frontier multimodal models as well as the inference infrastructure used to serve our own and third-party models at scale. We already publish and distribute Reka models through the Hugging Face Hub, and we’d now like to expand that relationship by joining Hugging Face Inference Providers and serving inference directly through our infrastructure.
- Provider: Reka AI
- Hub org: https://huggingface.co/RekaAI
- Developer portal: https://developer.reka.ai/
- API base URL: https://api.reka.ai/v1
- Contact: annie@reka.ai
Models we’d like to start with (chat completions):
- deepseek4-flash
- gemma4-26b
- glm5.3
- glm5.3-flash
- qwen3.8-27b
Our API is OpenAI-compatible and already supports /v1/chat/completions. We serve both Reka’s proprietary multimodal models and a curated set of leading open models on infrastructure we operate.
A key difference for Reka is that we’re an AI research company as well as an inference provider. We build and train our own models and apply that research across our serving stack, including model quantization, distillation, optimized GPU kernels, KV-cache optimization, batching, load balancing, and low-level inference optimizations.
We’re also highly competitive on pricing and already serve live public traffic through OpenRouter. Current pricing, context lengths, and available models are published through our developer portal and /v1/models.
We’d be happy to implement the remaining Hugging Face provider requirements, including the Inference-Id header, billing endpoint, model mappings, and huggingface.js integration.
Who should we coordinate with for server-side registration and onboarding?
Thanks!
Annie
Reka AI
annie@reka.ai
Hi Hugging Face team,
We’re Ruvilab, an AI inference provider offering OpenAI-compatible access to open-weight models. We’re already serving direct clients and would like to make our service available through Hugging Face Inference Providers as well.
Our details:
- Organization: https://huggingface.co/ruvilab
- Website: https://ruvilab.com
- Contact: contact@ruvilab.com
Could you help us coordinate the next steps for provider onboarding, integration review, and the server-side registration needed to configure model mappings?
Please let us know what information or validation evidence you would like us to prepare, whether there is a preferred onboarding contact, and if there is an indicative review timeline.
Thanks!
Rushil Patel
Hi Hugging Face team,
We would like to join Inference Providers as FUSE, a managed inference service hosted in Riyadh, Saudi Arabia.
Provider details
Provider ID: fuse
Hugging Face organization: https://huggingface.co/ai-Humain (Team plan active)
API base URL: https://api.fuse.humainaic.com/v1
API docs: Documentation | HUMAIN FUSE
Contact: Mohammed Alshehri | Maalshehri@humain.com
API compatibility
Standard conversational task through OpenAI-compatible POST /v1/chat/completions, streaming and non-streaming.
Tool calling and structured output (JSON schema) supported.
GET /v1/models returns pricing (USD per million input and output tokens) and context_length for each model.
Billing endpoint for request ID cost lookup in nano-USD: [ready by Mid of October]
Initial models (conversational)
deepseek-ai/DeepSeek-V4.1-Flash
zai-org/GLM-5.3-Flash
Qwen/Qwen3.8-Flash-Next
openai/gpt-oss-120b
Data handling
No routing to third-party providers.
No storage of prompts or outputs after a request completes.
No training on customer content.
We keep only request IDs and costs, for billing.
Why FUSE on the Hub
Hub users in the Middle East get low-latency access to open models with in-Kingdom processing. That matters to Saudi enterprise and government buyers.
Next steps
We are preparing the huggingface.js pull request, and can start model mappings in staging as soon as you enable our organization. Please let us know if you need anything else.
Thank you,
Mohammed | HUMAIN
Hi Hugging Face team,
I'm Jonas, the developer behind Flonno (https://www.flonno.com), based in Switzerland. I'm evaluating a focused self-hosted offering for open-weight models and would like to understand whether it could be a fit for Inference Providers. Our current API forwards requests to external infrastructure; our own GPU deployment is not live yet.
Are you considering new small providers, and are there particular models or regions where additional coverage would be useful? What minimum capacity, performance and availability would you expect for an initial evaluation?
I've read the registration guide and understand that integration includes model mappings, client integration, a billing endpoint and a Team or Enterprise organization plan. Before committing to that work, I'd appreciate guidance on the right onboarding contact and how to validate the fit.
Best regards,
Jonas Boos / Flonno
jonas@flonno.com
Hi Hugging Face team,
I'm José, founder of QDivZero, an AI inference platform built by Valendra Tech in Spain.
We'd love to explore integrating QDivZero with Hugging Face.
QDivZero takes a slightly different approach from traditional inference providers. Instead of maintaining only a fixed catalogue of hosted models, our platform can deploy compatible Hugging Face models on demand with one click.
Given a Hugging Face repository, QDivZero can automatically provision the required GPU infrastructure, select the appropriate inference runtime, launch the model, and expose it through an OpenAI-compatible API.
We currently work with runtimes such as vLLM, SGLang and llama.cpp, and our infrastructure is designed around dynamic GPU provisioning, pay-per-compute usage, and shared inference capacity.
We support two complementary execution models:
- Dedicated/on-demand capacity, where a model is dynamically deployed for a user or workload.
- Shared capacity, where multiple users can access already-running model infrastructure, reducing cold starts and improving cost efficiency.
This allows us to dynamically deploy long-tail or custom models while keeping popular models available through shared warm capacity.
We see two particularly interesting integration paths with Hugging Face:
QDivZero as an official Inference Provider for popular models served through our shared/warm capacity.
A "Deploy on QDivZero" workflow that would allow users to launch arbitrary compatible Hugging Face models directly from the Hub.
The second use case is especially interesting to us.
Our goal is to make the experience as simple as:
Hugging Face model → Deploy → GPU provisioned → OpenAI-compatible endpoint
without requiring the user to manually choose GPU types, configure vLLM/SGLang, manage containers, or build inference infrastructure.
For popular models, the experience can instead become:
Hugging Face model → Shared QDivZero capacity → Immediate inference
Over time, models receiving enough demand can move from dedicated/on-demand deployments into shared pools, reducing both startup times and inference costs.
We're based in Europe and are particularly interested in providing a European infrastructure option for open-weight AI models.
Website: https://qdivzero.com
We'd be happy to implement the requirements for Hugging Face Inference Providers and would also love to discuss whether the broader one-click deployment workflow could be interesting for the Hub.
Would this be something the Hugging Face team would be interested in exploring?
Happy to share a demo, architecture details, benchmarks, or jump on a call.
José Carlos García Ortega jose@valendra.tech
Founder — QDivZero / Valendra Tech
Hi HF team — we're TokenWatt (Teampulse Solutions LLC, US), and we'd like to join Inference Providers. Our org: https://huggingface.co/tokenwatt
We serve open-weight LLMs on measured US hardware: every endpoint is sized from our published SLO-goodput benchmarks (https://www.tokenwatt.io/reports.html), with fast 429s instead of queueing. No prompt/completion logging or training (https://www.tokenwatt.io/privacy.html).
Our API is OpenAI-compatible and already implements your contract: base URL https://api.tokenwatt.io/hf, /v1/models with pricing and context length, an Inference-Id header on every response, and a nano-USD billing endpoint.
First models: Qwen/Qwen3-30B-A3B and Qwen/Qwen3-30B-A3B-Instruct-2507 (FP8, accuracy-gated against BF16), with tool calling and structured outputs.
We have the huggingface.js provider helper ready to PR. Could you enable us server-side for the model mapping API? Contact: hello@tokenwatt.io
Hi! We'd like to add impossibl as an inference provider.
impossibl is an OpenAI- and Anthropic-compatible gateway (https://impossibl.com, API at https://api.impossibl.com). For Hugging Face we'd start with conversational models we already serve: openai/gpt-oss-120b, zai-org/GLM-5.3, moonshotai/Kimi-K3, MiniMaxAI/MiniMax-M3, deepseek-ai/DeepSeek-V4-Pro-0813 and Qwen/Qwen3.8-27B.
Where we are:
- Our org https://huggingface.co/impossibl is on the Team plan
/v1/chat/completionssupports streaming, tool calling and structured outputs- We've implemented the
Inference-Idresponse header and the billing endpoint (POST /v1/billing/requests, cost in nano-USD per request id) - PRs are open for huggingface.js (https://github.com/huggingface/huggingface.js/pull/2632), huggingface_hub (https://github.com/huggingface/huggingface_hub/pull/5114) and hub-docs (https://github.com/huggingface/hub-docs/pull/2866)
What we can't do ourselves is get the org enabled for the Model Mapping API and registered server-side. Could someone help with that? Happy to send logos or anything else you need.
Thanks,
Jonathan
Gödel Machines: request to join as an Inference Provider
Hi! We're Gödel Machines (https://huggingface.co/GoedelMachines), an AI lab in Hyderabad, India. We'd like to become an Inference Provider.
- Endpoint: OpenAI-compatible, live at
https://api.goedelmachines.com/v1, with streaming and usage, tool calling and reasoning. - First model: Qwen/Qwen3.8-27B (NVIDIA NVFP4 weights), 262k context, on our own RTX PRO 6000 Blackwell GPUs. Median time to first token is about 0.8 s.
- Differentiator: inference runs in India, with no prompt or completion retention and no training on user data (policy: https://api.goedelmachines.com/legal#privacy).
- Pricing: $0.10 / 1M input, $0.02 / 1M cached input, $1.90 / 1M output.
We're implementing the Inference-Id header and billing endpoint now, and our org is on the Team plan. We're ready to open the huggingface.js PR. Who should we coordinate with?
Hi Hugging Face team,
I’m following up on our interest in joining Hugging Face Inference Providers. TokenAAS is an OpenAI-compatible API gateway operated by FUELNODE TECHNOLOGIES INC. (Canada).
Our Hugging Face account is weixiaoxin, our organization is https://huggingface.co/tokenaas, our website is https://tokenaas.ai, and our API base URL is https://tokenaas.ai/v1.
We provide unified access to third-party inference services, with API key management, usage metering, and billing; we do not host the model weights ourselves. Could you let us know whether this operating model is eligible, whether you are accepting new provider applications, and where we should submit a formal application? We can provide a provider profile, technical details, supporting documents, and evaluation credentials through a private channel.
I have also contacted your team by email. You can reach us at admin@tokenaas.ai.
Thank you,
The TokenAAS team
Hi Hugging Face team,
We’re preparing a self-hosted inference service and would like to explore joining Hugging Face Inference Providers.
Our initial model is Qwen/Qwen3-Coder-30B-A3B-Instruct-FP8. We have implemented and locally tested:
- An OpenAI-compatible chat completions API
- Streaming and non-streaming responses
- Tool calling and structured outputs
- A /v1/models endpoint exposing pricing and context length
- Unique Inference-Id response headers
- A persistent billing endpoint returning per-request costs in nano-USD, with idempotent lookups
Public HTTPS deployment and sustained reliability testing are currently in progress.
Are you currently accepting new providers? Could you advise on the eligibility requirements, the appropriate onboarding contact, and the next steps for integration review and server-side registration?
We’d be happy to share our API documentation, test results, and evaluation credentials through a private channel.
Contact: blake19950908@gmail.com
Thank you!
Hi @julien-c ,
I am Flavien, the founder of CARouter (https://carouter.ai), a sovereign Canadian inference platform. We would like to become an Inference Provider on the Hub, starting with Qwen/Qwen3.6-35B-A3B.
The model runs on machines we operate in Ottawa, Ontario, and every response names the region that served it. Scaleway and OVHcloud give Hub users a European option, and we would like to be the Canadian one.
Our API is OpenAI-compatible, with streaming, tool calling, structured output and image input, at the model's full 262K context. We serve the model at 4-bit precision and would say so on our provider page. The request id header on streams, the billing endpoint and USD pricing on /v1/models are scoped, and they are the next things we build.
Before we open the client pull requests, two answers would help us:
- How and in which currency are providers paid for routed requests?
- What's the acceptable quantization, and how would you like it disclosed?
Our proposed provider id is "carouter". I am posting the same request on the Inference Providers feedback thread for the record.
cc @Wauplin @SBrandeis @hanouticelina
Thanks,
Flavien
Founder, CARouter
Hi Hugging Face team and Computer Vision community!
We are exploring how to bring TAPe+ML, our compact Computer Vision architecture, to the Hugging Face Inference Providers ecosystem.
What makes TAPe+ML interesting?
- Fewer than 100K parameters
- Approximately 8 ms per frame on CPU** in our reported test setup (Intel Xeon E5-2697 v2)
- 84.7 mAP50 and 65.3 mAP50-95** on COCO object detection
- 80.7 mask mAP50** on COCO instance segmentation
- One compact architecture supporting object detection, image segmentation and image classification
- Designed for efficient CPU, Edge and on-premise deployment
Our research explores an alternative approach to compact multi-task vision systems, with an emphasis on structured representations and reduced computational requirements.
Explore TAPe+ML:
🔹 Model: https://huggingface.co/Comexp/tape-ml
🔹 Live demo: https://huggingface.co/spaces/Comexp/TAPeML-Demo
🔹 Research paper: https://huggingface.co/papers/2609.20869
🔹 Platform and API: https://ml.comexp.net/
🔹 User Guide: https://ml.comexp.net/user_guide_en.pdf
The model weights are proprietary and are not publicly distributed. Inference is currently provided through our own platform and API.
We would appreciate guidance from the Hugging Face team on the Inference Providers onboarding process:
- Are third-party providers currently being onboarded for Computer Vision tasks such as Object Detection, Segmentation and Classification?
- Should we begin by preparing a
huggingface.jsintegration, or is there an eligibility review before technical implementation? - Are there specific requirements for making a proprietary Computer Vision model available through the unified Inference Providers API?
We would be glad to hear feedback from the community and connect with teams interested in efficient, CPU-first Computer Vision.
Best regards,
Maxim Vorobyev
Comexp Research Lab
comexp@comexp.net
Hi Julien and team,
I'd like to register ZenEdgeX as an Inference Provider for a task that does not have an API schema yet: robotics (the robotics pipeline tag that LeRobot policies carry). We run Proprio, an inference engine for vision-language-action policies that executes the unmodified checkpoint and verifies every action chunk bit for bit against eager execution before serving it. Measured on an RTX 4090 with stock LeRobot checkpoints: lerobot/smolvla_base 6.4x faster, lerobot/pi05_base 2.7x, nvidia/GR00T-N1.7-3B 2.7x, all ticks bit-identical; evaluation wheels and a certificate anyone can reproduce are public: https://github.com/zenedgex/proprio-releases, results at https://zenedgex.in/proprio/.
What we would bring to the Hub: a provider for every robotics model page (observation in: images, state, instruction; action chunk out), so people can try a policy from the model page and run evaluation rollouts without setting up a GPU, with the guarantee that the actions are the checkpoint's own.
We are ready to implement the task API schema for robotics in huggingface.js following your task spec conventions, the billing endpoint and the Inference-Id header as described in the registration guide, model mappings in staging for the three policies above, and the Python helper and docs page. The hosted endpoint exists today (openpi-compatible websocket server; we would add the HTTP/JSON route for routed requests).
Could you enable our organization (zenedgex) server-side and tell us who to work with on the robotics task schema? Happy to open the huggingface.js PR as a draft for discussion first.
Dr. Gopalakrishna Sunkara, ZenEdgeX, hello@zenedgex.in
Hi Hugging Face team,
We're Linkrra (https://linkrra.com) and we'd like to join Inference Providers with Synap, our inference API.
- OpenAI-compatible endpoint: https://synap.linkrra.com/v1 (chat completions, streaming, tool calling, structured outputs; live model list with pricing and context at
/v1/models) - Models we serve on GPUs we operate ourselves (not resold from another provider), USD per 1M input / output tokens:
openai/gpt-oss-20b: $0.017 / $0.085, 32K contextQwen/Qwen3-30B-A3B-Instruct-2507: $0.0585 / $0.2438, 64K contextQwen/Qwen3-Coder-30B-A3B-Instruct: $0.0675 / $0.27, 32K contextgoogle/gemma-4-26B-A4B-it(text input): $0.04 / $0.21, 128K context
- Pricing: https://synap.linkrra.com/pricing
- Contact: michael@linkrra.com
Are you currently accepting new providers, and what would be the right next step? We're happy to open the huggingface.js PR and follow the registration guide.
Thanks!
The Linkrra team
Hi Hugging Face team, I’m Nathan Roll, founder of Oruk (https://oruk.ai). We would like to join Inference Providers for automatic speech recognition.
We now have a live Qwen/Qwen3-ASR-1.7B deployment on a dedicated NVIDIA L4 in GCP us-central1. Qwen / Alibaba develops the Apache-2.0 model; Oruk operates inference. Our focus is speech and multimodal serving, kernel optimization, latency and throughput.
Working service:
- API reference: https://qwen3-asr.oruk.ai/docs
- HF-shaped route: POST https://qwen3-asr.oruk.ai/models/Qwen/Qwen3-ASR-1.7B (raw audio or base64 JSON; provider key required)
- OpenAI-compatible route: POST /v1/audio/transcriptions
- Free community demo: https://huggingface.co/spaces/oruk/qwen3-asr
- Public paid API: https://rapidapi.com/NathanRoll/api/oruk-speech-api
The service accepts one file up to 60 seconds and 25 MiB, with complete-file text transcription. Streaming, timestamps and diarization are not enabled. The demo has a separate 10-second / 2-MiB limit and shared daily budget. Oruk does not persist audio or transcript payloads.
SDK implementation is submitted as draft PR https://github.com/huggingface/huggingface.js/pull/2680 . Five adapter tests, the inference package type check and lint passed. The provider/org identifiers remain provisional pending your review and enablement. Tenant-isolated cost reporting is implemented at /v1/billing/costs; review access currently uses free private-preview metering, with commercial billing terms still to agree.
Could you review the ASR adapter and advise on provider/org enablement, model mapping and billing validation? We are not claiming native Inference Provider acceptance or that the draft SDK change has merged.
Contact: nathan@oruk.ai. Thanks, Nathan
Hi team,
Quick update-- our ASR adapter is ready for review: https://github.com/huggingface/huggingface.js/pull/2680
All 5 adapter tests, types and lint passed again!
The live service and billing endpoint are working, and we have the current SVG icon ready. Could you confirm the next step for enabling org/provider oruk and creating an ASR staging mapping (including the organization-plan requirement)?
Service docs: https://qwen3-asr.oruk.ai/docs
Best,
Nathan
Hi Hugging Face team,
I'm reaching out on behalf of ERON X, a Czech IT infrastructure and GPU hosting provider.
We operate our own GPU infrastructure in the Czech Republic (European Union) and are interested in becoming an official Hugging Face Inference Provider.
Our current infrastructure includes:
- 5 AI models available through our inference infrastructure
- OpenAI-compatible API managed through LiteLLM Proxy
- API key authentication and centralized model routing
- Self-hosted GPU infrastructure under our management
- European hosting and the ability to offer EU-based inference
We are interested in making our inference capacity available to Hugging Face users, with usage-based billing and competitive token pricing.
We would be happy to implement any additional requirements, including model mapping, billing integration, request identification, and provider-specific API compatibility.
Could you please clarify:
- Are you currently accepting new inference providers?
- Can a smaller, independent European GPU infrastructure provider join the program?
- Is an existing OpenAI-compatible LiteLLM endpoint a suitable starting point for integration?
- What are the technical and commercial requirements for onboarding?
Company: ERON X
Website: https://www.eronx.cz
Location: Czech Republic, European Union
We would be happy to provide additional technical information, model specifications, performance benchmarks, and API testing credentials privately.
Thank you for your time!
Best regards,
ERON X Team
Hi Hugging Face team,
I am Jun, co-founder of Fractalyze, an inference optimization company building ultra-low-cost model APIs. We optimize GPU kernels, memory use, caching, quantization, and serving configurations to reduce the cost of running existing models, with workload-specific quality and performance validation.
As one public example of our engineering work, Qwen-Image 2.1 went from 13.47s to 1.85s versus SGLang BF16 on a single RTX 5090 at 1024x1024, 40 steps, warm batch 1. Mean LPIPS versus BF16 was 0.112 over 200 held-out DrawBench prompts. This is an image-model benchmark, separate from the Gemma API described below. Results and code: https://huggingface.co/Fractalyze/qwen-image21-rtx5090-showcase
Gemma 4 26B is our first API pilot, not the intended limit of our model catalog. After validating this pilot's quality, performance, reliability, and unit economics, we plan to scale capacity and expand the model lineup. Our goal is to translate lower serving costs into the lowest sustainable API prices.
The current pilot runs on one RTX 5090 and supports OpenAI-compatible chat completions, text-only input/output, bearer authentication, non-streaming responses, and tool calling. Streaming and other required integration features can be prepared before production onboarding.
We would like to start onboarding discussions for paid inference distribution. Who should we work with on eligibility and technical integration? Could you also share the provider commercial terms, platform fees, and payout currency, schedule, and minimums? We can coordinate evaluation access privately.
Website: https://www.fractalyze.io/
Contact: jun@fractalyze.io
Thanks,
Jun
Co-founder, Fractalyze
Hi Hugging Face team! I am Kendell Jeffrey, operator of InfraXsky, and I would like to join Inference Providers.
We serve Qwen/Qwen3-30B-A3B (currently only one live provider on the Hub) through an OpenAI-compatible API, with streaming, tool calling and JSON-schema structured output. Benchmarked with sglang.bench_serving at 20 concurrent requests: p99 time-to-first-token is about 3.1 s.
- JS client PR: https://github.com/huggingface/huggingface.js/pull/2695
- Billing endpoint follows your spec (nano-USD, Inference-Id header)
- /v1/models exposes pricing ($0.11 / $0.45 per million tokens) and context length (40,960 tokens)
- Hosted on a dedicated GPU server in Helsinki, Finland
- Privacy policy (no prompt storage, no training): https://kencloudapi.duckdns.org/privacy
Two questions: is a Team plan required for the Model Mapping step, and how are providers paid out for routed requests?
Contact: kendell.jeffrey@gmail.com
Thanks,
Kendell Jeffrey
InfraXsky
Serenity Edge (Substrate AI): request to join Inference Providers
Hi Hugging Face team,
We are Substrate AI (https://substrate.ai), and we would like to register Serenity Edge as an Inference Provider on the Hub.
About Serenity Edge
- An OpenAI-compatible inference API (https://api.serenityedge.ai/v1): chat completions with streaming, tool calling and structured output (response_format).
- It runs on our own infrastructure in Spain, and data stays in the EU.
- Zero data retention: prompts and completions are not stored (the prompt cache lives for less than 24 hours), and API traffic is never used to train, fine-tune or evaluate models.
- Docs: https://docs.serenityedge.ai · Status: https://status.serenityedge.ai
What is already in place, following the provider guide
- An Inference-Id header (UUID) on every response, including streaming and errors.
- A billing endpoint that returns the cost per request ID in nano-USD; costs are available about a second after each request. We will share its URL and our credentials through your onboarding.
- Pricing (USD per million input and output tokens) and context_length in /v1/models.
- We checked our chat models against your validation criteria: time to first streamed token is well under 5 seconds, and tool calling and structured output work.
Models we would map first
- Qwen/Qwen3.8-27B -> qwen3.8-27b (conversational)
- Qwen/Qwen3.6-35B-A3B -> qwen3.6-35b-a3b (conversational)
More models (embeddings, reranking, OCR) could follow if their tasks fit.
Our Hub organization is SubstrateAILab (Team plan). We would suggest "serenity-edge" as the provider name.
A few questions
- What are the next steps to enable our provider account server-side?
- Both chat models are served as NVFP4 quantizations. We plan to state this on our provider page; is there anything else you need in the mapping?
- We also serve our own model family (Orion) through Edge, without weights on the Hub. Can API-only models be listed, or is the program limited to models with a public Hub repository?
- How is routed usage settled between Hugging Face and the provider?
- Could you share the egress IP ranges your router uses? We would exempt them from our per-IP rate limits before going live.
You can also reach us at lharillo@substrate.ai and contact@substrate.ai.
Thank you,
Leandro Harillo
CTO, Substrate AI
MuninCloud (Bogarra Integrated SL, Spain): request to join Inference Providers
Hi Hugging Face team,
We are MuninCloud (https://munincloud.com), the cloud brand of Bogarra Integrated SL, a Spanish company, and we would like to join Inference Providers.
What is live today
- OpenAI-compatible API: https://api-flex-huggingface.munincloud.com/v1 (chat completions, streaming with token usage in streaming and non-streaming responses).
- /v1/models with pricing (USD per million tokens) and context_length: https://api-flex-huggingface.munincloud.com/v1/models
- Model: Qwen/Qwen3-32B served as AWQ 4-bit with vLLM, context window 16,384 tokens, up to 4,096 output tokens. Price: $0.11 / $0.39 per million input / output tokens.
- Dedicated servers in Germany (Hetzner, Falkenstein), inside the EU.
- Zero data retention: prompts and completions are never written to disk or logs and never used for training. Prefix cache is salted per account (measured: no cross-account cache hits).
- An Inference-Id header (UUID) on every response.
- When our engine is busy we answer 429 with Retry-After, never a 5xx.
- Privacy policy: https://munincloud.com/legal/flex/en/privacy · Terms: https://munincloud.com/legal/flex/en/terms
What we will do next, following the provider guide
- Open the huggingface.js PR (OpenAI-compatible conversational helper).
- Implement the billing endpoint (cost per request ID in nano-USD).
- Upgrade our Hub organization AdminMunin (https://huggingface.co/AdminMunin) to the Team plan when the mapping step is enabled.
Questions
- How and in which currency is routed usage settled with the provider?
- Is an AWQ 4-bit deployment acceptable mapped to Qwen/Qwen3-32B (we state the quantization openly)?
- Does your router read /v1/models with our provider key, or without authentication?
- What are the next steps to enable our provider account server-side?
Contact: javier.bogarra@munincloud.com
Thank you,
The MuninCloud team
Hi Hugging Face team — I’m Gaurav Sharma, founder of SaaS Labs, and we’d like to bring PyAI Hear (automatic speech recognition) and Speak (text-to-speech) to Inference Providers. Hub organization: https://huggingface.co/pyaibyatomsai.
PyAI helps developers add speech input and spoken answers to their existing apps and agents while keeping their chosen LLM and orchestration. Hear supports 29 recognition languages with automatic detection. Speak’s live catalog offers 200 stock voices across 17 language groups. These are supported-language/catalog counts, not a claim of equal measured quality in every language. Our LiveKit and Pipecat integrations are already published on PyPI.
Current direct pricing: Hear $0.001 per audio minute (synchronous nonempty requests round up to started minutes; empty transcripts are free). Speak $0.04 per generated audio minute, using actual output duration. We’d like to agree audio-specific billing and settlement with your team.
A recent bounded production check generated a 2.48-second WAV in 1,294 ms and transcribed the exact sentence in 1,530 ms (JSON) / 2,439 ms (plain text). This is one short English example and full-response timing—not first-audio latency, a percentile benchmark or SLA. PyAI’s default no-training warranty covers customer inputs and outputs; it is separate from retention, and we do not claim zero retention.
API: https://api.pyai.com/v1 (authenticated OpenAI-compatible audio endpoints). Docs: https://docs.pyai.com. Pricing: https://pyai.com/pricing. Privacy: https://pyai.com/legal/privacy.
Could you confirm eligibility and the model-mapping path for these API products before we submit the JS/Python adapters? In particular: are API-only speech products eligible, which Hub model repositories should they map to, and what are the billing precision and organization-plan requirements for qualification? We can then implement the agreed task schemas and billing endpoint. This is an onboarding request; PyAI is not yet a native HF Inference Provider.
Contact: gaurav@pyai.com. Thank you!
Following up on PyAI’s onboarding request with new, reproducible integration evidence. Our goal is to bring Hear (ASR) and Speak (TTS) to Inference Providers, so developers can add speech input and spoken answers around their chosen LLM.
The exact AI SDK example passed a production Speak → Hear round trip: HTTP 200 on both requests, no retries, a valid 2.48-second WAV (119,084 bytes), and the correct transcript “Hello, your voice integration is ready.” Full-response timings were 1,954 ms for Speak and 1,464 ms for Hear. This is one short English functional sample—not first-audio latency, a percentile benchmark or an SLA. It verifies the direct PyAI integration, not native Hugging Face routing.
Current direct rates remain Hear $0.001 per started input-audio minute per nonempty synchronous request (empty transcripts free) and Speak $0.04 per generated minute, using actual output duration. Hear supports 29 recognition languages; Speak’s catalog contains 200 stock voices across 17 language groups. These are support/catalog counts, not equal-quality claims. Our default no-training warranty covers inputs and outputs, separately from retention.
Could the provider onboarding team confirm whether these API-only speech products are eligible and which Hub model repositories they should map to? We’ve reviewed the provider guide and understand the remaining JS task adapter, request-cost billing endpoint, server-side mappings and organization-plan steps. We want to implement the agreed ASR/TTS contract rather than assume the LLM compatibility path applies.
An onboarding owner and the next qualification checklist would help us move directly to a focused pilot. Organization: pyaibyatomsai. Contact: gaurav@pyai.com. Thank you!
Quick update to our note above (Oct 18) - two things changed since then:
- We added a vision-capable model to the lineup: Qwen/Qwen3-VL-30B-A3B-Instruct ($0.14 / $0.57 per 1M input/output tokens, 32K context, OpenAI-compatible chat completions).
- We published a Space here on the Hub so people can try our models without leaving it: https://huggingface.co/spaces/linkrra-si/synap
Live catalog + pricing (OpenAI-compatible), always current: https://synap.linkrra.com/v1/models
Still happy to open the huggingface.js PR and follow the registration guide whenever useful on your side - no rush.
Thanks!
The Linkrra team
Following up on our GoedelMachines provider request: we have moved from Qwen to DeepSeek V4.1 Flash.
We now serve DeepSeek V4.1 Flash on our own four NVIDIA RTX PRO 6000 Blackwell Server Edition GPUs in Hyderabad, India.
Endpoint: https://api.goedelmachines.com/v1
Model: deepseek/deepseek-v4.1-flash
Hub model: deepseek-ai/DeepSeek-V4.1-Flash
International USD list per million tokens: $0.30 input / $0.006 cached input / $1.20 output, including reasoning. Our India-only INR discount is separate.
The API supports OpenAI-compatible chat and streaming, usage reporting, reasoning, function calling, JSON object mode and JSON schema outputs. A bounded October 26 public-HTTPS smoke run passed 20/20 checks across our internal and dedicated partner keys. The dedicated partner keys report X-Data-Policy: none.
In three short rounds of 256 output tokens per request through the public endpoint from Colossus, median aggregate output divided by complete request wall time was 227 tokens/s at concurrency 1 and 458 tokens/s at concurrency 4. These are smoke measurements, not sustained-capacity or overseas-latency claims.
Our HF-style model list is https://api.goedelmachines.com/v1/models/hf. The cost endpoint is POST /v1/billing/costs; responses include Inference-Id. Nine of nine HF test requests were priced correctly, repeated lookups were identical, and another partner key could not access their costs. We have since deployed persisted per-request costs and verified that old request costs remain unchanged across the price change.
We have a dedicated HF integration key available privately. We would welcome the next onboarding step, including server-side registration, model mapping and client-integration requirements, before activation.
Organization: https://huggingface.co/GoedelMachines · Contact: rk@goedelmachines.com
Hi Hugging Face team,
We're IronStratum : we run a per-token, OpenAI-compatible inference API at https://api.ironstratum.com/v1.
We have several models exclusive to our platform, on GPU capacity we operate ourselves, alongside a catalog covering the DeepSeek, Qwen, GLM, and MiniMax families, with fresh builds listed fast (we listed
DeepSeek V4.1 Flash 1017 two days after its release) and specialty lanes for OCR, classification, voice, robotics and image generation. Several of these are Hub models with no inference provider today. They ship on dedicated action and vision routes with per-call and per-image metering.
We'd like to be listed as an Inference Provider. Following the registration guide, the pieces on our side are in place:
- Chat completions follow the OpenAI API shape
- /v1/models is anonymously readable and exposes pricing (USD per million input/output tokens) and context_length, in the format the guide expects.
- The billing endpoint is implemented to the documented batch protocol:
POST with requestIds, responses in nano-USD integers, idempotent, inside the 30-minute window, authenticated by a dedicated key. The response header carrying our request id is x-request-id - Tool calling and structured output (response_format with json_schema) are both live through our API and verified on our serving lanes.
Our organization on the Hub is iron-stratum (Team plan). We're ready to open the huggingface.js PR, register our initial mappings in staging, and follow with the huggingface_hub PR and a provider page for the docs.
What's the best way to start the huggingface.js PR first, or the server-side enablement with you first? Happy to share details on infrastructure, latency, or pricing.
Thanks
Hi Hugging Face team,
We are Apex Fusion (https://huggingface.co/apexfusion) and would like to be
registered as an Inference Provider. Conversational task only for now,
OpenAI-compatible API, served from our own GPU server in Helsinki, Finland.
- huggingface.js PR: https://github.com/huggingface/huggingface.js/pull/2686
(check, lint and format pass; @Wauplin and @SBrandeis are tagged) - Endpoint: https://hf-edge.vector.apexfusion.org (/v1/chat/completions,
streaming, tool calling, structured output; /v1/models exposes pricing
and context_length) - Inference-Id response header and the billing endpoint are implemented
- First model: Qwen/Qwen3.8-27B
We will send the billing URL and the bearer token through a private channel
once you tell us where. Happy to adjust anything in the PR.
Thanks,
Apex Fusion
Negbeta (EU inference provider): request to join Inference Providers with DeepSeek V4.1 Flash
Hi Hugging Face team,
We'd like to join Inference Providers with DeepSeek V4.1 Flash 1017, including an EU-hosted option for Hub users who need EU processing.
Negbeta is a new inference provider: top-quality inference with US and EU capacity, zero data retention and strict EU compliance, at a competitive price.
- Full 1M context on DeepSeek, fast time to first token, strong prompt caching for agentic workloads, reliable under load; OpenAI-compatible, streaming, tool calls, structured outputs, reasoning,
X-Request-Idon every response. - We'll do the integration work: client PRs, model mappings, billing endpoint.
Qwen3.8 27B is also in our catalogue, and we're ramping up further models to serve the demand. We're onboarded with one router, with others in progress.
What would you like from us to get started?
Endpoint: https://inference.negbeta.com/v1/models · Docs: https://inference.negbeta.com/docs
Thomas Ip
Founder, Negbeta Limited
info@negbeta.com · https://negbeta.com









