{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibpbx6emizreezcj5qkxirrtbuyd5ifln3zc5kytgtue2izffpq6u",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mns6l4af5ke2"
  },
  "path": "/t/deprecation-notice-prompt-objects-in-the-api-will-be-shut-down-on-november-30th-2026/1382593#post_15",
  "publishedAt": "2026-06-08T16:54:26.000Z",
  "site": "https://community.openai.com",
  "textContent": "The costs will not skyrocket.\n\nThere is some misunderstanding here: The prompts feature is simply a way for you to have provided the same input to the AI model, but stored on the OpenAI servers.\n\nYou paid for the input data of a large instructions field in the model’s input cost regardless of whether it was added by use of a prompt’s “developer” message created in the platform site (no longer “playground” because prompts and the UI now is not fun), via the “instructions” field in the Responses API, or whether by self-managed chat turns with a “system” role message as guidance.\n\nThe only thing this feature might have saved you is some in-flight network time - but OpenAI’s backend services, and even Responses over Chat Completions, add latency also. And models now have thinking a long time before you see any output as a latency feature.\n\nCalls to the API should not be originating from mobile devices, calling OpenAI directly, that you have to “redeploy”. That indicates that your client code has the API key. You just gave every user the password to make their own API calls, only needing to be captured over the network or reversed out of the app.",
  "title": "Deprecation notice: Prompt Objects in the API will be shut down on November 30th, 2026"
}