Hugging Face Inference Providers vs Jais 3

Hugging Face Inference Providers 79

Model reading. Fine-grained user access tokens that can be limited to the Make calls to Inference Providers permission, rotated and revoked, plus a public revocation endpoint for leaked tokens, and organisation approval of fine-grained tokens on paid plans (30). Hugging Face says it doesn't store user data for training, but data handling past the router follows each provider's policy, with no per-request filter to exclude providers that train or retain (12 of 20). Request bodies and responses aren't stored when routed and debug logs are kept up to 30 days without user data or tokens, with provider retention outside that statement (10 of 15). Usage by model and provider in account settings, an Enterprise usage API, and Team and Enterprise admins can disable providers and set a spending limit (13 of 15). SOC 2 Type 2 for the Hub, of which the docs say Inference Providers is a feature, and security.txt valid to 2030 per the Inference Endpoints check; no bug bounty found (14 of 20).

Jais 3 31

Read as software the owner runs. No account or key, ungated downloads, and server authentication is the owner's to add (12 of 30). A model that calls whatever tools the operator wires in. The cards rule high-stakes decisions without human oversight out of scope, but nothing in the model or template enforces approval (6 of 20). The template renders tool results in their own tool role, but string results go in as raw text (only non-string content is serialised with tojson), no escaping of special-token sequences in caller or tool text was found, and no injection guidance or results are published (4 of 15). No call log of its own. Visibility depends on the serving stack (5 of 15). Every launch command passes --trust-remote-code, so modeling_k2_horizon.py from the repository runs on the host. We read it and found only torch and transformers imports. No security.txt on ifm.ai (404 on 17 October, not re-read), no security contact on the cards and no safety evaluation found. Since 25 October the cards link a technical report on ifm.ai, which answered a Cloudflare bot check on 4 November, so what it covers is unread (4 of 20). 12 + 6 + 4 + 5 + 4 = 31.

Hugging Face Inference Providers 20

No x402, MPP or L402 (0). Per-token prices for every model and provider published without a login in the router's /v1/models and on model pages (20). No free tier since 7 October 2026, when free users lost their included monthly credits; PRO's $2.00 of credits needs a subscription (0). Sign-up, token creation and credit purchase are browser steps (0).

Jais 3 60

Self-hosted rule. Apache-2.0 weights with nothing to buy and no hosted option from the makers (20). Free to run with no card (20). Downloads are ungated and anonymous, so an agent can fetch the weights with no sign-up (20). No payment protocol (0). 20 + 20 + 20 + 0 = 60.

Hugging Face Inference Providers 25

Hosted lines. status.huggingface.co is a Better Stack page with 90-day component history for the Hub, Inference Endpoints, Spaces, the CDNs and Jobs, but no component for Inference Providers or the router (10 of 20). With no component, there is no readable incident history for the surface agents call, and the feed's 23 items from 10 June to 7 October 2026 don't name it (5). No rate limits for the router were found; the Hub rate-limits page gives numbers for Hub APIs, resolvers and pages only (0). No 429 or overload guidance for the router was found (0). No SLA found (0). Chat completions on the router is generally available; the Responses API is labelled beta (10). Routing between providers with :fastest or :cheapest softens a single provider's outage, which this checklist doesn't score.

Jais 3 48

Read with the local-software lines, since the owner serves the weights. Ungated weights on Hugging Face with stated runtimes (vLLM 0.30.0 or later, SGLang 0.5.20 or later, Transformers validated at 5.15.0, mlx-lm with shipped model code), but every launch command trusts remote code. The GGUF card still says to build llama.cpp from master or wait for a release, though llama.cpp's own tags carry K2 Horizon support from b11454 (6 October 2026) (16 of 20, held). No CI or test suite of the makers' was found, and the code repository is 'coming soon'. SGLang's cookbook reports a validation pass of the tool-call parser on all six checkpoints, and IFM's MLX cards describe conversion checks against the PyTorch code (3 of 25). No crash reports. On 4 November the six main repositories held seven discussions, six of them closed citation updates and one open MoVA-36B-A4B thread from 26 October with no reply yet. Two template fixes for OpenAI-style message history landed on 14 October, before the launch (15 of 25). No changelog or version tags, only public commit messages (2 of 15). Released as named final checkpoints with no preview label, though mlx-lm v0.32.2 still has no K2 Horizon model code of its own (12 of 15). 16 + 3 + 15 + 2 + 12 = 48.

Hugging Face Inference Providers 80

Model reading. huggingface_hub 2.4.0 tagged on 29 October 2026 and the Inference Providers docs updated daily by an automated job, last on 6 November (30). huggingface_hub 2.2.0, 2.3.0 and 2.4.0 and @huggingface/inference 4.13.28 to 4.13.32 in the 90 days (20). No dedicated changelog; the Hub has a forum and Discord, and GitHub issue replies were not read (8 of 15). Current official SDKs in Python and JavaScript (15). The Python client supports Python 3.10 and later, per the Inference Endpoints check; CI not read (7 of 10).

Jais 3 62

Read for an open-weight model released on 15 October 2026. The last change to the template or code was on 15 October, within 30 days. The cards gained a technical report link on 25 October and a citation update on 27 October, which change no file a runtime loads (30). One family release, with dated builds before it (FP8 from 29 September, MLX from 1 October, GGUF on 12 and 13 October) and template fixes on 14 and 15 October, but no deprecation notices or successor history to judge. K2 Horizon came on 1 September and Jais 2 in December 2025 (10 of 20, the model reading of this line, held). One outside question, on MoVA-36B-A4B on 26 October, had no reply on 4 November, and IFM's GitHub repositories weren't read. The template fixes match the problem IFM's MLX cards describe (7 of 25, held). Recipes in vLLM's and SGLang's own docs, K2 Horizon support in llama.cpp's tagged builds from b11454 and FP8, GGUF and MLX builds from IFM, but no native mlx-lm support (11 of 15). Current dependencies (Transformers 5.13 to 5.15, vLLM 0.30), with no CI visible (4 of 10). 30 + 10 + 7 + 11 + 4 = 62.

Hugging Face Inference Providers 71

Closed service under Terms of Service that name Inference Providers, with an Apache-2.0 Python client and an MIT JavaScript client (20). The security page and the docs agree on no training, no stored bodies and 30-day logs, but the privacy policy dates from 28 March 2023 and each provider's own data policy governs the rest (18 of 30). No deprecation policy found. Provider support changes and the 7 October removal of free credits are dated only in the docs repository history (5 of 20). The privacy policy lists 11 subprocessors with countries per the Inference Endpoints check, and the docs name every provider a request can reach, though not where each runs (15 of 20).

Jais 3 55

Apache-2.0 in every card's metadata, with staged training checkpoints as branches and training logs linked on Weights & Biases (not opened). There is no LICENSE file and the code repository is still 'coming soon'. A technical report is linked from 25 October but sits behind a bot check, so its data description is unread (24 of 30). Inputs stay on the owner's hardware because nothing is hosted, but no statement says so and no privacy document governs the weights (15 of 30). No deprecation policy, dated notices or version scheme (0 of 20). Safetensors weights carry no code, and the remote modelling and configuration code we read imports only torch, transformers and huggingface_hub, with no network calls. No telemetry statement (12 of 20). 24 + 15 + 0 + 12 = 51.

Hugging Face Inference Providers 62

No OpenAPI document for the router (openapi.json paths answer 404). The task reference pages are generated from typed JSON Schema specs in huggingface.js, and the router's /v1/models gives a machine-readable catalogue, so 12 of 25. llms.txt for the Inference Providers docs and a Markdown twin of every page via .md (10). Guides say what each task and policy is for, with a quick setup page for coding agents (14 of 20). Parameter tables with types for chat completion, though response_format and tool_choice show as unknown types (9 of 15). Examples in Python, JavaScript and curl on every task page, but no documented error responses for the router (9 of 15). No changelog of its own; the Hub changelog doesn't cover it and dated changes are only in the hub-docs history (8 of 15).

Jais 3 54

Read for a model the owner serves. No specification of its own. The contract is the Jinja chat template, which validates tool JSON Schemas (required fields must exist in properties) and rejects unknown options, plus the OpenAI-compatible servers in vLLM and SGLang with the k2_horizon parsers (10 of 25). The cards are Markdown on Hugging Face, and SGLang's docs have an llms.txt, but no llms.txt or Markdown docs from IFM were found and ifm.ai couldn't be read (5 of 10). Each card states intended use, four out-of-scope uses, limitations and per-size serving advice (15 of 20). reasoning_effort and tool_call_format are enums enforced with errors, and tools take JSON Schema. The 375B card describes low as no reasoning and omits medium, which the template accepts, and structured output isn't documented (10 of 15). Python examples for a reasoning call and a tool loop, commands for five runtimes, and named template errors, but no error reference for a served model (11 of 15). No changelog or version scheme. Training-stage branches and public commit history (3 of 15). 10 + 5 + 15 + 10 + 11 + 3 = 54.