Tool support requires the appropriate API integration; a supported tool is not automatically active in every chat.
Supported API features and tools
Streaming, function calling, and structured outputs
Image input and prompt caching
Web search and file search
Code interpreter
Image generation through a tool
Apply patch and MCP
Before you choose
Deprecated: OpenAI schedules API shutdown for April 1, 2027.
No native audio or video support.
Fine-tuning is not supported.
Its knowledge cutoff is September 30, 2024; provide current evidence when the task depends on later facts.
Choose the reasoning effort
none · defaultlowmediumhigh
Choose none for a simple baseline and compare an explicit reasoning setting on harder cases. GPT-5.1 does not offer xhigh or max. Preserve a representative evaluation set so a later model migration measures behavior rather than just changes in wording.
Unsupported settings: minimal, xhigh, max.
Responses, Chat Completions, and Batch are supported. The built-in tools listed here refer to Responses integrations.
The documented snapshot is gpt-5.1-2025-11-13. Do not confuse this API model with separately retired chat or Codex variants.
OpenAI recommends GPT-6 Sol as the replacement before the April 1, 2027 shutdown.
Put it to work
Start with a more useful prompt.
Original examples from EZ Ai Assist. Adapt these to your task and the features available in your workspace.
Workflow 01
Explain unfamiliar code with evidence
Map behavior from supplied files without inventing missing dependencies.
Explain how this code handles the request shown in the example. Identify the entry point, validation, state changes, and returned result, citing the relevant functions. Separate behavior visible in the supplied code from assumptions about omitted dependencies. List three edge cases worth testing and the exact additional files needed to resolve any uncertainty. Do not propose a rewrite.
Workflow 02
Turn requirements into acceptance checks
Convert a small feature brief into tests with explicit expected outcomes.
Convert this feature brief into acceptance checks. For each requirement, provide the initial conditions, user action, expected result, and a negative case. Link each check to the requirement it covers. Flag ambiguous language and missing decisions rather than selecting defaults silently. Keep the tests within the requested feature and distinguish mandatory behavior from optional improvements.
Workflow 03
Prepare a safe handover
Produce a useful transition document from existing project evidence.
Create a handover from these project notes and test results. Include current behavior, completed changes, unresolved risks, commands that were actually run, and the next owner’s first three checks. Cite the note or result supporting each status claim. Do not call proposed work complete or infer that an unreported test passed. End with the information still needed for a safe transition.
Developer reference
OpenAI API pricing
These are OpenAI API reference prices, not EZ Ai Assist subscription prices.
The reviewed Standard table lists these rates without a separate long-context column for GPT-5.1.
Cached-input pricing requires eligible cached tokens. Other processing tiers and tool usage can add or change charges.
Confirm current pricing and plan migration before the scheduled API shutdown; published prices do not guarantee continued availability.
Common questions
A few things worth knowing.
Is GPT-5.1 still a good choice for a new integration?
OpenAI has deprecated it, with API shutdown scheduled for April 1, 2027. Evaluate the recommended GPT-6 Sol replacement for new long-lived work. Keep this guide as a reference for existing workflows and migration testing.
Which reasoning settings does GPT-5.1 support?
The API reference lists none, low, medium, and high, with none as default. It does not list xhigh or max. Do not copy effort settings from a later GPT model without checking compatibility.
Does the cutoff mean it knows nothing newer?
The September 30, 2024 cutoff describes its training knowledge boundary. You can supply newer documents or use supported tools through an appropriate integration, but current claims still need verification against those sources.
Does API deprecation mean the website page disappears?
No. This page remains available to explain the model and its migration path. The notice describes OpenAI’s API schedule, not the removal date of a marketing page or a guarantee of app availability.
Can I use this model with images and tools?
Image input and several Responses tools are documented, including web search, file search, and code interpreter. Native output is text. The surrounding application must supply and authorize the relevant tools.
Are API rates the same as subscription prices?
No. OpenAI charges direct API usage separately from EZ Ai Assist subscriptions. Check the website’s pricing page and your app account for plan costs and available features.
What should I preserve during migration?
Save representative inputs, expected outcomes, failure cases, and measured costs. Recheck tool permissions, effort settings, output validation, and latency on the replacement. Roll out gradually and keep a rollback path until the new workflow is verified.
Check the source
Official documentation
Specifications and API prices checked on . Example prompts and workflow advice are editorial guidance from EZ Ai Assist.