> ## Documentation Index > Fetch the complete documentation index at: https://runinfra.ai/docs/llms.txt > Use this file to discover all available pages before exploring further. # Models > Name any compatible Hugging Face model in chat. RunInfra checks that it can read it and that it can serve it, before anything is charged. You give the agent a Hugging Face model id. Before the run costs you anything, RunInfra checks that your workspace can actually read that repository and that its weights can be served.

## Support is decided before pricing When you select a model for optimization, RunInfra shows one of three verdicts before it shows a charge: | Verdict | Meaning | | - | - | | **Supported** | RunInfra can measure and optimize the model. | | **Benchmark only** | RunInfra can measure a baseline, but it cannot optimize this model shape. | | **Not yet supported** | RunInfra refuses the optimization for the stated reason and lists the model families it can optimize. | A temporary metadata outage is separate from a permanent refusal and offers **Retry**. A refused model creates no hold, reservation, or ledger entry. RunInfra decides the refusal before any charge preview appears. ## Every refusal names one next action | Situation | What to do | | - | - | | The model is gated or private and no token that can read it is connected | Connect a Hugging Face account with access from **Settings > Connected clouds**, then accept the runbook again. | | Hugging Face rejected the connected token | Reconnect a valid token from **Settings > Connected clouds**, then accept again. | | The connected account cannot read the model | Open the model page on Hugging Face, accept its license and request access with that same account, then accept again. Choosing an ungated model also unblocks the runbook. | | The model is gated and access could not be confirmed for the connected account | Accept the model license on Hugging Face with that account, then accept again. | | The repository publishes only adapter weights (LoRA or PEFT) | An adapter cannot be served on its own. Merge it into its base model and point the runbook at the merged repository, or choose a model that ships full weights. | | The repository publishes only GGUF files | This optimization path cannot load GGUF. Point the runbook at a safetensors or bin build of the same model. A local runtime format is something a run can produce for you as an output, not something it can start from. | | The id does not resolve to a Hugging Face repository | Point the runbook at a verified `owner/repo` model id, then accept again. | ## Naming a model Three forms, all resolved to the same Hugging Face id: ```text theme={"dark"} Use Llama 3.1 8B for this pipeline Optimize @Qwen2.5-14B-Instruct with FP8 Deploy microsoft/Phi-3-mini-4k-instruct optimized for latency ``` A full `owner/repo` id is exact. A name or an `@` mention is resolved for you. A description ("a fast multilingual 7B") makes the agent recommend one. ## What can be served Large language models, embeddings, rerankers, vision-language models, speech-to-text, text-to-speech, and image generation, sourced from Hugging Face. Availability for a given model depends on the selected runtime and the deployment support for that modality, and the agent tells you before it provisions anything. You can also chain models into one pipeline, for example speech-to-text feeding a language model feeding text-to-speech for a voice assistant. ## Limits * The maximum context window is set by the model itself. A request that exceeds it is rejected. See [Errors](/docs/api-reference/errors) for the response shape. * Multimodal request limits depend on the selected model and runtime. The agent reports the limits that apply to your configuration before it provisions. * A rerank deployment answers its own rerank route, not the chat-completions route. Some rerank models are text-only, and where the deployed model supports it, document `content` arrays carry text, images, and video. The agent reports the route and the accepted content types for your deployment. * Some model licenses carry commercial-use or user-count gates. RunInfra passes them through and you agree to them on your own Hugging Face account. RunInfra adds no restrictions of its own. * Fine-tuning is external today. Train elsewhere, then bring the weights. Uploading model weights is an **Enterprise** capability. On other plans the upload is refused with an upgrade path. [Contact sales](https://runinfra.ai/contact?category=sales). An upload is a **folder**, not a file: the complete Hugging Face model repo you exported, with `config.json` at the root, safetensors or PyTorch `.bin` weights (plus the index file when sharded), and the tokenizer files. Extra files are stored as they are. The ceiling is 50 GB. Validation runs in the browser before any bytes move and again on the server. The stored model ends up either validated and ready for measured optimization, or stored incomplete with the specific reason. Interrupted uploads can be retried, and nothing is ever marked ready that is not. Uploaded models go through the same optimization path as any other, and you reference one by the name you gave it: ```text theme={"dark"} Use my uploaded model "fine-tuned-llama-7b" for this pipeline ``` Uploads live at [runinfra.ai/models](https://runinfra.ai/models). That page is not in the dashboard sidebar while the dashboard narrows around Model APIs, but the route, your bookmarks, and the command palette all still open it. ## Next steps Plan, filter, measure, rank, pick. Why your weights are left at full precision by default. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.