openai
OpenAI: GPT-4.1
openai/gpt-4.1
Use GPT-4.1 as a pinned comparison when evaluating instruction following or code review. Keep the same input, output cap and scoring rules across candidates.
Provider-supported parameters
These are upstream capabilities. Jevrouter supports the subset described in the API contract; chat input is currently text only.
Capabilities are imported from OpenRouter’s catalog. This does not mean every model has been independently tested by Jevrouter.
Catalog updated: 2026-09-22T08:51:50.371Z · Price version: cmub815uo021hjn0z3ru9qzfa:2
Provider pricing fields · USD per indicated unit
{
"prompt": "0.000002",
"completion": "0.000008",
"web_search": "0.01",
"input_cache_read": "0.0000005"
}JEVROUTER INTEGRATION NOTES · REVIEWED 2026-09-22
What to check in your application
- Separate context-window capacity from the output-token limit shown in this catalog.
- Provider-specific parameters outside Jevrouter's documented chat contract are rejected even if the upstream supports them.
Start with the example below, then test representative inputs against your own acceptance criteria.
Make a request
curl --no-buffer https://api.jevrouter.io/v1/chat/completions \
-H "Authorization: Bearer $JEVROUTER_API_KEY" \
-H "Content-Type: application/json" \
-d @- <<'JSON'
{
"model": "openai/gpt-4.1",
"messages": [
{
"role": "user",
"content": "Review this Python expression for empty input: sum(values) / len(values). Suggest a safe function and two edge-case tests."
}
],
"max_tokens": 1024
}
JSONPlan your integration
Related models to evaluate
Use identical inputs and scoring rules. No ranking is implied by this selection.
Source: OpenRouter model catalog. Imported descriptions and capabilities are provider declarations, not independent benchmark results. Jevrouter currently uses OpenRouter as its managed upstream.