Shieldstral 1.0 3B
Shieldstral 1.0 3B is a 3-billion-parameter multimodal safety classifier built by Mistral. It is uniquely designed to evaluate content against user-defined safety policies expressed in natural language at inference time, without requiring retraining.
Input
Output
Context
262K
Max Output
-
Parameters
3.8B
Technical Specifications
Input Modalities
Output Modalities
Capabilities
Loading capabilities…
Estimated GPU requirements for Shieldstral 1.0 3B
Estimates based on INT8 quantization at up to 32K context. A count above one assumes tensor parallelism across the cards. Actual requirements vary by framework and configuration.
More models by Mistral
The creator's other models in the catalog, with their context, size and license where published.
Compare it, or keep browsing
Put this model beside its alternatives on the same evidence, or go back to the full catalog.
Frequently asked questions about Shieldstral 1.0 3B
Answered from the entry's own fields: context, license, modalities, evidence, serving and the memory to self-host.
Shieldstral 1.0 3B advertises a context window of 262,144 tokens. The figure is the creator's published maximum; a given host may serve less, and the gateway routes on what each host actually serves.
Yes. Shieldstral 1.0 3B is an open-weight model released under the Apache 2.0 license, so the weights can be downloaded and self-hosted within that license's terms.
The catalog has no modality record for Shieldstral 1.0 3B, so its inputs and outputs are shown as not available rather than assumed to be text.
No published benchmark result for Shieldstral 1.0 3B is in the catalog yet, so the model is shown as unmeasured. It is not ranked or estimated; the router treats it as unknown for every task until a suite measures it.
Not on the managed pool today; Shieldstral 1.0 3B is listed for reference and comparison. Connect your own provider key or endpoint that serves it and the gateway runs it on your account, with routing decisions recorded the same way.
About 4.1 GB at INT8 for the weights and a default context, from the catalog's 3.8B parameter count; FP16 needs roughly twice that, and long contexts or many concurrent requests add KV cache on top. The GPU section on this page lists cards that hold it, and the capacity planner sizes it for your context length and traffic.
Fields collected from public registries, host APIs and benchmark publishers, each tagged with its source.
Last updated: Aug 28, 2026
Put intelligence in the middle.
One gateway in front of every model, with your policies applied and every decision on record. Start with $5 of credit and 5,000 routing decisions a month, no card required.