BAAIJudgeLM 33B V1.0
JudgeLM is a specialized judge model developed by HUST and BAAI, fine-tuned from Vicuna. It is designed for research on evaluating the performance of large language models and chatbots.
Input
Output
Context
2K
Max Output
-
Parameters
33B
Technical Specifications
Input Modalities
Output Modalities
Capabilities
Loading capabilities…
Estimated GPU requirements for JudgeLM 33B V1.0
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 BAAI
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 JudgeLM 33B V1.0
Answered from the entry's own fields: context, license, modalities, evidence, serving and the memory to self-host.
JudgeLM 33B V1.0 advertises a context window of 2,048 tokens. The figure is the creator's published maximum; a given provider may serve less, and the gateway routes on what each provider actually serves.
Yes. JudgeLM 33B V1.0 is an open-weight model released under the Non commercial license, so the weights can be downloaded and self-hosted within that license's terms.
JudgeLM 33B V1.0 accepts Text and produces Text. The capabilities card on this page lists which API features each deployment honours, such as function calling and structured output, with the source each was checked against.
No published benchmark result for JudgeLM 33B V1.0 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; JudgeLM 33B V1.0 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 32.9 GB at INT8 for the weights and a default context, from the catalog's 33B 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, provider APIs and benchmark publishers, each tagged with its source.
Last updated: Nov 4, 2026
Put intelligence in the middle.
One gateway in front of every model, with your policies applied and every decision on record. Start on the free plan with 5,000 requests a month, no card required.