Published by mistralai. No machine on this network has measured this family yet. The members below are what the catalog knows exists; nothing about what they can do is claimed here until somebody runs one.
Declared by the network’s catalog, not measured — a signature says what this family would be asked. Whether it answered is the signed capability flags on each member.
Declared, not measured — this is what the catalog says exists and what it would cost a machine to hold. Nothing here is signed, and none of it claims the build works.
0 of 20 builds fit a 16 GB machine — budgeting 70% of it, or 11.2 GiB, because the cache and the runtime want the rest.
Sizes are what the catalog declares, not what a machine measured — fitting on disk is necessary and not sufficient. Nobody here has run these on your machine, and this narrows the candidates rather than certifying one.
Your concierge can answer this from the network rather than from this page. The ask carries the operator id, so it resolves to a capability and an engine — not to a name somebody has to recognise.
What has this network measured about the Mistral Large 3 family (epn.family.mistral-large-3), and can my gram run any of it? See /inferences/mistral-large-3