openai
OpenAI: GPT-4.1 Nano
openai/gpt-4.1-nano
A GPT-4.1 family candidate to evaluate for bounded outputs such as classification and short extraction. Measure errors that would require a second call before deciding on a cost baseline.
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: cmubxr2rt07xijn0zfhyur43i:3
Provider pricing fields · USD per indicated unit
{
"prompt": "0.0000001",
"completion": "0.0000004",
"web_search": "0.01",
"input_cache_read": "0.000000025"
}JEVROUTER INTEGRATION NOTES · REVIEWED 2026-09-22
What to check in your application
- Include ambiguous and out-of-scope examples when evaluating a classifier.
- Compare cost per accepted result, including retries, rather than token price alone.
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-nano",
"messages": [
{
"role": "user",
"content": "Classify this message as billing, technical, or other: My invoice has the wrong company name. Output one label."
}
],
"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.