Hi MiniMax-AI/MiniMax-Provider-Verifier maintainers,
EvalScope now supports MiniMax-Vendor-Verifier. This gives users another way to run the benchmark when they want a standardized evaluation workflow around OpenAI-compatible model endpoints, saved predictions, scoring, and report generation.
This may be useful for users who find this repository while setting up MiniMax-Vendor-Verifier and want a quick path to evaluate a hosted or locally served model.
Example:
evalscope eval \
--model YOUR_MODEL \
--api-url OPENAI_API_COMPAT_URL \
--api-key EMPTY_TOKEN \
--datasets minimax_verifier \
--limit 10
Docs: https://evalscope.readthedocs.io/en/latest/benchmarks/minimax_verifier.html
EvalScope repo: https://github.com/modelscope/evalscope
We can also open a small PR adding this as a README/Docs note, linked to this issue.
Hi MiniMax-AI/MiniMax-Provider-Verifier maintainers,
EvalScope now supports MiniMax-Vendor-Verifier. This gives users another way to run the benchmark when they want a standardized evaluation workflow around OpenAI-compatible model endpoints, saved predictions, scoring, and report generation.
This may be useful for users who find this repository while setting up MiniMax-Vendor-Verifier and want a quick path to evaluate a hosted or locally served model.
Example:
evalscope eval \ --model YOUR_MODEL \ --api-url OPENAI_API_COMPAT_URL \ --api-key EMPTY_TOKEN \ --datasets minimax_verifier \ --limit 10Docs: https://evalscope.readthedocs.io/en/latest/benchmarks/minimax_verifier.html
EvalScope repo: https://github.com/modelscope/evalscope
We can also open a small PR adding this as a README/Docs note, linked to this issue.