Appearance
Integrations
Open Settings → Integrations to connect provider credentials.
OpenRouter
OpenRouter is the primary provider integration. It is used for:
- Creating leaderboards.
- Running judge-based evaluations.
- Auto-selecting candidate models.
- Calling OpenRouter models attached to leaderboards.
- Creating and evaluating Dr.Gero model workflows that depend on OpenRouter.
The UI validates the token before saving it. OpenRouter tokens usually begin with sk-or-.
Hugging Face
Hugging Face is used for private or gated dataset access. It is strongly recommended when the leaderboard dataset is not public.
The UI validates the token before saving it. Hugging Face tokens often begin with hf_.
Validation behavior
When you save a provider token, the UI sends it to /api/integrations/validate with your signed-in Supabase session. The server validates:
- Hugging Face through the Hugging Face identity API.
- OpenRouter through the OpenRouter key API.
Common failures
| Symptom | Likely cause | Fix |
|---|---|---|
| Create Leaderboard is disabled | No OpenRouter token | Add and validate OpenRouter. |
| Hugging Face dataset check fails | Private/gated dataset without HF token | Add a Hugging Face token. |
| Auto-select models fails | Missing or invalid OpenRouter token | Re-save the OpenRouter integration. |
| Judge evaluation cannot run | Missing OpenRouter token or judge model issue | Validate OpenRouter and check the judge model ID. |