Alex GetmanAI 早期信号

GPT-4.1

OpenAI

已发布 更新于
上下文窗口
1M
1,047,576 token
最大输出
33K
32,768 token
输入 / 输出
文本, 图像 → 文本

API 价格

USD / 百万 token

输入输出缓存输入
  • $2.00
openai-pricing
  • $8.00
openai-pricing
  • $0.50
openai-pricing

时间线

  1. · API 开放 · 参考链接 · 参考链接 · 参考链接
  2. · 产品更新 · 参考链接 · 参考链接
输入/输出价格 · USD / 百万 token
模型参考链接输入/输出价格
gpt-4.1
batch
openai
API 路由不可用
$1.00 / $4.00
gpt-4.1
fast
openai
API 路由不可用
$3.50 / $14.00
gpt-4.1
standard
openai$2.00 / $8.00
openai/gpt-4.1
standard
openrouter$2.00 / $8.00
openai/gpt-4.1:batch
batch
openrouter$1.00 / $4.00
openai/gpt-4.1
standard
vercel-gateway$2.00 / $8.00
openai/gpt-4.1-batch
batch
vercel-gateway$1.00 / $4.00
  1. · 已确认使用 · OpenAI · official articles · Introducing GPT-4.1 in the API
  2. · 参考链接 · OpenAI · official articles
    摘录
    Introducing GPT‑4.1 in the API
  3. · 参考链接 · OpenAI · official articles
  4. · 参考链接 · OpenAI · official articles
  5. · 参考链接 · OpenAI · official articles
    摘录
    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
  6. · 参考链接 · OpenAI · official articles
  7. · 目录记录 · GitHub · openai/openai-node · code
    摘录
    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
  8. · 目录记录 · GitHub · openai/openai-agents-python · code
    摘录
    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
  9. · 目录记录 · GitHub · openai/codex · code
    摘录
    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 /// `

    此代码引用并不能证实这是实际使用中的模型标识符。

  10. · 目录记录 · GitHub · openai/codex · code
    摘录
    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 /// `

    此代码引用并不能证实这是实际使用中的模型标识符。

  11. · 目录记录 · GitHub · openai/openai-agents-python · code
    摘录
    `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

    此代码引用并不能证实这是实际使用中的模型标识符。

  12. · 目录记录 · GitHub · openai/openai-python · code
    摘录
    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
  13. · 目录记录 · GitHub · openai/openai-agents-js · code
    摘录
    _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
  14. · 参考链接 · OpenAI · Model release notes
    摘录
    Starting today, Plus, Pro, and Team users can access GPT-4.1 via the "more models" dropdown in the model picker
  15. · 参考链接 · OpenAI · news
    摘录
    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
  16. · 参考链接 · OpenAI · ChatGPT release notes
    摘录
    Starting today, Plus, Pro, and Team users can access GPT-4.1 via the "more models" dropdown in the model picker

信号 1

规格

GPT-4.1 是 OpenAI 的 AI 模型,于 2025-04-14 发布。 上下文窗口为1,047,576 token。 最大输出为32,768 token。 每百万 token 的价格为:输入 $2.00,输出 $8.00。

上下文窗口
1,047,576
最大输出
32,768
输入
文本 · 图像
输出
文本
输入 · USD / 百万 token
$2.00
输出 · USD / 百万 token
$8.00
缓存输入 · USD / 百万 token
$0.50

常见问题

GPT-4.1 的上下文窗口有多大?

上下文窗口为1,047,576 token。 最大输出为32,768 token。

GPT-4.1 的价格是多少?

每百万 token 的价格为:输入 $2.00,输出 $8.00。 缓存输入价格为每百万 token $0.50。

GPT-4.1 何时发布?

2025-04-14。