The Socket in the Wall

The name has also turned into a dialect. A builder describes a gateway that offers a single OpenAI-compatible endpoint and key for GPT, Claude, Gemini, DeepSeek and Qwen, meant to spare builders a separate SDK and bill for each provider. Building to a single company's interface so that other companies' models can answer it says whose interface it is. The term Responses API turns up in posts about OpenAI's own models, about Azure deployments and about xAI's service, and a reply saying a fix is on the way agrees that "responses api support is table stakes." That is what a standard looks like from the inside: people don't have to like OpenAI to speak its interface.

The socket comes with a meter, and the meter is where people get stung. A job is "easy to do with openai API but it costs too much," says someone who wants something modest from it. In posts like that, the obstacle named is the bill rather than the model. The worry takes a sharper form for someone who says they were charged for credits they never approved and wants to know whether anyone was refunded.

Where there is a meter there is a hunt for a cheaper door, and the week's questions circle the one between a ChatGPT subscription and an API key. Someone weighing a production app they built for a medical organization asks whether the client should pay for tokens or whether the app should authenticate through a ChatGPT subscription, which they say could be significantly cheaper and which they are concerned about. What people want there is subscription pricing with API control. Someone else explains that a service-tier setting exists only on the API's billing side, and that a ChatGPT subscription can't switch it on. The two are sold as separate things.

The key itself is a recurring character: identity, wallet and liability in one string. After hardcoding a secret key into their code, one person reports, their "usage is toast" and the account says they "Owe Bigly." The same slip can land on someone else instead. A report about a key committed to a public repository says an attacker used it to generate malicious code that was injected into Hugging Face's model deployment pipeline.

The ground under the socket also moves. Someone who counted public n8n templates reports that some still call the Assistants API after it shut down and others pin model ids that are about to stop answering, calling them "workflows someone copied once and never opened again," which on their account means code written against the API can outlive the thing it was written for.

A telling movement is in what the API is said to do for you. The week before, a user complained that a coding agent kept stopping to wait for the word "Continue," and a reply said the API has no "keep going until blocked" mode, so any fix had to be an external loop; this week a post says OpenAI has opened an Agents API to developers, a hosted endpoint on the same harness as Codex, with durable sessions, tool use, subagents, context management and failure recovery, which the post sets against assembling the Responses API, an orchestration loop and a sandbox yourself. On that post's account, a job that sat with the builder the week before now sits with OpenAI.

Whether any of this is hard depends on who is asking. A user who says they are "scared of any type of coding whatsoever" plans to work through ChatGPT and Obsidian instead of the API. For that person the API is something to route around. Another user, answering a claim that the API is an advanced topic, disputes it, saying "click one button to generate the key, install codex, enter API key, done," and blames gatekeeping for the opposite view. Both are arguing about what it costs a person to start using the API: in effort, in credits, or both.

One post reports that the API pricing page had its pricing information removed and replaced with marketing content for ChatGPT Business and Enterprise plans. For anyone who builds on the socket, the wall belongs to someone else, and so does the page that says what plugging in will cost.