
GPT-4.1
OpenAI
- Context window
- 1M 1,047,576 token
- Pinakamahabang output
- 33K 32,768 token
- Input / Output
- teksto, larawan → teksto
Mga presyo ng API
USD / 1 milyong token
| Input | Output | Naka-cache na input |
|---|---|---|
|
|
|
Takdang panahon
- · Magagamit sa API · link sa ebidensiya · link sa ebidensiya · link sa ebidensiya
- · Update sa produkto · link sa ebidensiya · link sa ebidensiya
Presyo ng input / output · USD / 1 milyong token
| Modelo | Mga link sa ebidensiya | Presyo ng input / output |
|---|---|---|
gpt-4.1batch | openai Hindi available ang ruta ng API | $1.00 / $4.00 |
gpt-4.1fast | openai Hindi available ang ruta ng API | $3.50 / $14.00 |
gpt-4.1standard | openai | $2.00 / $8.00 |
openai/gpt-4.1standard | openrouter | $2.00 / $8.00 |
openai/gpt-4.1:batchbatch | openrouter | $1.00 / $4.00 |
openai/gpt-4.1standard | vercel-gateway | $2.00 / $8.00 |
openai/gpt-4.1-batchbatch | vercel-gateway | $1.00 / $4.00 |
- · Kumpirmadong paggamit · OpenAI · official articles · Introducing GPT-4.1 in the API
- · Mga link sa ebidensiya · OpenAI · official articles
Sipi
Introducing GPT‑4.1 in the API
- · Mga link sa ebidensiya · OpenAI · official articles
- · Mga link sa ebidensiya · OpenAI · official articles
- · Mga link sa ebidensiya · OpenAI · official articles
Sipi
On OpenAI-MRCR, a measure of long-context information retrieval, GPT‑5 outperforms o3 and GPT‑4.1, by a margin that grows substantially at longer input lengths
- · Mga link sa ebidensiya · OpenAI · official articles
- · Pagkakalista sa katalogo · GitHub · openai/openai-node · code
Sipi
s.openai.com/api/docs/models) for descriptions * of them. */ model?: | (string & {}) | 'gpt-5' | 'gpt-5-mini' | 'gpt-5-nano' | 'gpt-5-2025-08-07' | 'gpt-5-mini-2025-08-07' | 'gpt-5-nano-2025-08-07' | 'gpt-4.1' | 'gpt-4.1-mini' | 'gpt-4.1-nano' | 'gpt-4.1-2025-04-14' | 'gpt-4.1-mini-2025-04-14' | 'gpt-4.1-nano-2025-04-14' | 'o3-mini' | 'o3-mini-2025-01-31' | 'o1' | 'o1-2024-12-17' | 'gpt-4o' | 'gpt-4o-2024-11-20' | 'gpt-4o-2024-08-06' | 'gpt-4o-2024-05-13' | 'gpt-4o-mini' | 'gpt-4o-mini-2024-07-18' | 'gpt-4.5-preview' | 'gpt-4.5-preview-2025-02-27' | 'gpt-4-turbo' | 'gpt-4-turbo-2024-04-09' | 'gpt-4-0125-preview' | 'gpt-4-turbo-preview' | 'gpt-4-1106-preview' | 'gpt-4-vision-preview' | 'gpt-4' | 'gpt-4-0314' | 'gpt-4-0613' | 'gpt-4
- · Pagkakalista sa katalogo · GitHub · openai/openai-agents-python · code
Sipi
dels import get_default_model from ...models.interface import Model, ModelProvider from .litellm_model import LitellmModel # This is kept for backward compatibility but using get_default_model() method is recommended. DEFAULT_MODEL: str = "gpt-4.1" class LitellmProvider(ModelProvider): """A ModelProvider that uses LiteLLM to route to any model provider. You can use it via: ```python Runner.run(agent, input, run_config=RunConfig(model_provider=LitellmProvider())) ``` See supported models here: [litellm models](https://docs.litellm.ai/docs/providers). NOTE: API keys must be set via environment variables. If you're using models that require additional configuration (e.g. Azure API base or version), those must also be set via the environment variables that LiteLLM expects. If you have more advanced needs, we recommend copy-pasting this clas
- · Pagkakalista sa katalogo · GitHub · openai/codex · code
Sipi
ror> { let mode = if PARSE_IN_STRICT_MODE { ParseMode::Strict } else { ParseMode::Lenient }; parse_patch_text(patch, mode) } enum ParseMode { /// Parse the patch text argument as is. Strict, /// GPT-4.1 is known to formulate the `command` array for the `local_shell` /// tool call for `apply_patch` call using something like the following: /// /// ```json /// [ /// "apply_patch", /// "<<'EOF'\n*** Begin Patch\n*** Update File: README.md\n@@...\n*** End Patch\nEOF\n", /// ] /// ``` /// /// This is a problem because `local_shell` is a bit of a misnomer: the /// `command` is not invoked by passing the arguments to a shell like Bash, /// but are invoked using something akin to `execvpe(3)`. /// /// This is significant in this case because where a shell would interpret /// `
Hindi pinatutunayan ng pagbanggit na ito sa code ang isang ginagamit na identifier ng modelo.
- · Pagkakalista sa katalogo · GitHub · openai/codex · code
Sipi
ror> { let mode = if PARSE_IN_STRICT_MODE { ParseMode::Strict } else { ParseMode::Lenient }; parse_patch_text(patch, mode) } enum ParseMode { /// Parse the patch text argument as is. Strict, /// GPT-4.1 is known to formulate the `command` array for the `local_shell` /// tool call for `apply_patch` call using something like the following: /// /// ```json /// [ /// "apply_patch", /// "<<'EOF'\n*** Begin Patch\n*** Update File: README.md\n@@...\n*** End Patch\nEOF\n", /// ] /// ``` /// /// This is a problem because `local_shell` is a bit of a misnomer: the /// `command` is not invoked by passing the arguments to a shell like Bash, /// but are invoked using something akin to `execvpe(3)`. /// /// This is significant in this case because where a shell would interpret /// `
Hindi pinatutunayan ng pagbanggit na ito sa code ang isang ginagamit na identifier ng modelo.
- · Pagkakalista sa katalogo · GitHub · openai/openai-agents-python · code
Sipi
`openai/...` と `any-llm/...` のモデル名を混在させる場合は、[`MultiProvider`][agents.MultiProvider] を使用し、そこで `openai_use_responses_websocket=True` を設定します。 `MultiProvider` には、従来からの次の 2 つのデフォルト動作があります。 - `openai/...` は OpenAI プロバイダーのエイリアスとして扱われるため、`openai/gpt-4.1` はモデル `gpt-4.1` としてルーティングされます。 - 不明なプレフィックスはそのまま渡されず、`UserError` が発生します。 リテラルの名前空間付きモデル ID を要求する OpenAI 互換エンドポイントを OpenAI プロバイダーで使用する場合は、パススルー動作を明示的に有効にしてください。WebSocket が有効な設定では、`MultiProvider` にも `openai_use_responses_websocket=True` を維持してください。 ```python from agents import Agent, MultiProvider, RunConfig, Runner provider = MultiProvider( openai_base_url="https://openrouter.ai/api/v1", openai_api_key="...", openai_use_responses_websocket=True, openai_prefix_mode="model_id", unknown_prefix_mode="model_id", ) agent = Agent( name="Assistant", instructions="Be concise.", model="openai/gpt-4.1", ) re
Hindi pinatutunayan ng pagbanggit na ito sa code ang isang ginagamit na identifier ng modelo.
- · Pagkakalista sa katalogo · GitHub · openai/openai-python · code
Sipi
1-chat-latest", "gpt-5", "gpt-5-mini", "gpt-5-nano", "gpt-5-2025-08-07", "gpt-5-mini-2025-08-07", "gpt-5-nano-2025-08-07", "gpt-5-chat-latest", "gpt-4.1", "gpt-4.1-mini", "gpt-4.1-nano", "gpt-4.1-2025-04-14", "gpt-4.1-mini-2025-04-14", "gpt-4.1-nano-2025-04-14", "o4-mini", "o4-mini-2025-04-16", "o3", "o3-2025-04-16", "o3-mini", "o3-mini-2025-01-31", "o1", "o1-2024-12-17", "o1-preview", "o1-preview-2024-09-12", "o1-mini", "o1-mini-2024-09-12", "gpt-4o", "gpt-4o-2024-11-20", "gpt-4o-2024-08-06", "gpt-4o-2024-05-13", "gpt-aud
- · Pagkakalista sa katalogo · GitHub · openai/openai-agents-js · code
Sipi
_WINDOWS_1M = new Set([ 'gpt-6-astra', 'gpt-6-sol', 'gpt-6-luna', 'gpt-6.1-sol', 'gpt-5.6', 'gpt-5.6-sol', 'gpt-5.6-terra', 'gpt-5.6-luna', 'gpt-5.4', 'gpt-5.4-2026-03-05', 'gpt-5.4-pro', 'gpt-5.4-pro-2026-03-05', 'gpt-4.1', 'gpt-4.1-2025-04-14', 'gpt-4.1-mini', 'gpt-4.1-mini-2025-04-14', 'gpt-4.1-nano', 'gpt-4.1-nano-2025-04-14', ]); const SANDBOX_CONTEXT_WINDOWS_400K = new Set([ 'gpt-5', 'gpt-5-codex', 'gpt-5-mini', 'gpt-5-nano', 'gpt-5-pro', 'gpt-5.1', 'gpt-5.1-codex', 'gpt-5.1-codex-max', 'gpt-5.1-codex-mini', 'gpt-5.2', 'gpt-5.2-codex', 'gpt-5.2-codex-cyber', 'gpt-5.2-pro', 'gpt-5.3-codex', 'gpt-5.3-codex-spark', 'gpt-5.4-mini', 'gpt-5.4-nano', ]); const SANDBOX_CONTEXT_WINDOWS_200K = new Set([ 'codex-mini-latest', 'o1', 'o1-2024-12-17', 'o1-pro', 'o3', 'o3-2025-04-16', 'o3-mini', 'o3
- · Mga link sa ebidensiya · OpenAI · Model release notes
Sipi
Starting today, Plus, Pro, and Team users can access GPT-4.1 via the "more models" dropdown in the model picker
- · Mga link sa ebidensiya · OpenAI · news
Sipi
Introducing GPT-4.1 in the API—a new family of models with across-the-board improvements, including major gains in coding, instruction following, and long-context understanding
- · Mga link sa ebidensiya · OpenAI · ChatGPT release notes
Sipi
Starting today, Plus, Pro, and Team users can access GPT-4.1 via the "more models" dropdown in the model picker
Mga senyal 1
Mga espesipikasyon
Ang GPT-4.1 ay isang modelo mula sa OpenAI, na inilabas noong 2025-04-14. Ang context window ay 1,047,576 token. Ang pinakamahabang output ay 32,768 token. Ang presyo ay $2.00 sa bawat isang milyong input token at $8.00 sa bawat isang milyong output token.
- Context window
- 1,047,576
- Pinakamahabang output
- 32,768
- Input
- teksto · larawan
- Output
- teksto
- Input · USD / 1 milyong token
- $2.00
- Output · USD / 1 milyong token
- $8.00
- Naka-cache na input · USD / 1 milyong token
- $0.50
Mga tanong
Gaano kalaki ang context window ng GPT-4.1?
Ang context window ay 1,047,576 token. Ang pinakamahabang output ay 32,768 token.
Magkano ang GPT-4.1?
Ang presyo ay $2.00 sa bawat isang milyong input token at $8.00 sa bawat isang milyong output token. Ang naka-cache na input ay $0.50 sa bawat isang milyong token.
Kailan inilabas ang GPT-4.1?
Noong 2025-04-14.