OpenAI

How Much of Microsoft’s AI Revenue Actually Comes from OpenAI? Microsoft’s fiscal 2026 Form 10-K, filed with the SEC on August 5, 2026, reveals that the company recorded $24.1 billion in AI-related revenue from its partnership with OpenAI for the fiscal year ended June 30, 2026. According to Bloomberg’s analysis of the filing, this single customer relationship accounts for approximately 70% of Microsoft’s total AI revenue, which is estimated at $37–40 billion on an annualized basis. The disclosure offers the clearest public window yet into the financial architecture of one of the technology industry’s most consequential partnerships. ...

Scientific computing is undergoing a fundamental transformation as agentic AI systems take on increasingly complex roles in research software development. OpenAI’s July 2026 field report on eight agent-assisted scientific computing projects demonstrates that coding agents like Codex and Claude Code can modernize legacy research libraries, automate simulation workflows, and free scientists to focus on verification and discovery rather than implementation. This shift promises to accelerate research across life sciences, materials science, and beyond. ...

The Two Protocols Trying to Define How AI Agents Buy Things By mid-2026, two competing standards are vying to become the default way AI agents handle commerce: Google’s Universal Commerce Protocol (UCP) and OpenAI/Stripe’s Agentic Commerce Protocol (ACP). Both solve the same fundamental problem — how does an AI agent discover products, negotiate a purchase, and complete a transaction on behalf of a human — but they approach it from very different angles. ...

The AI agent API cost horror story in 2026 is not a single expensive prompt. It is usually a loop: an agent retries a tool, hands off to another agent, grows context, and keeps spending after dashboards have already warned you. The fix is hard runtime limits, not better vibes around prompt engineering. Why Are AI Agent API Cost Horror Stories Surging In 2026? AI agent costs are surging because the unit of failure changed. A chatbot request fails once. An agent request can fail for hours. ...

OpenAI Agents SDK vs LangGraph 2026 comes down to orchestration style: choose OpenAI Agents SDK for simple GPT-centric handoff chains, LangGraph for explicit stateful workflows, and Microsoft Agent Framework for Azure, .NET, and AutoGen or Semantic Kernel migrations. Quick Verdict: Which Framework Should You Choose in 2026? OpenAI Agents SDK vs LangGraph 2026 is a choice between lightweight OpenAI-native agent handoffs and explicit graph-based workflow control, with Microsoft Agent Framework now competing as the enterprise Microsoft option. As of June 15, 2026, GitHub showed LangGraph at 34,812 stars, OpenAI Agents Python at 27,167 stars, and Microsoft Agent Framework at 11,348 stars. Those numbers match what I see in implementation work: LangGraph has the broadest production workflow mindshare, OpenAI has the fastest path for GPT-first apps, and Microsoft is strongest where Azure, .NET, governance, and existing Semantic Kernel or AutoGen code matter. If you need a support bot that routes to specialized agents, use OpenAI Agents SDK. If you need a resumable, auditable claims workflow, use LangGraph. If procurement, Azure integration, and .NET teams drive the platform decision, use Microsoft Agent Framework. The takeaway: pick the framework whose control model matches your failure modes. ...

The GPT-6 API is not officially available in OpenAI’s API docs as of June 12, 2026. Build against GPT-5.5 and the Responses API today, then isolate model selection, evals, pricing checks, and rollout controls so a future GPT-6 model becomes a tested configuration change instead of a rewrite. Is the GPT-6 API Available in 2026? The GPT-6 API is not an officially documented OpenAI API model as of June 12, 2026, based on the current model catalog research brief for this article. The official flagship listed for complex reasoning and coding is GPT-5.5, with model ID gpt-5.5, a 1M token context window, 128K max output, and a December 1, 2025 knowledge cutoff. That matters because developers searching for a GPT-6 API setup guide can easily find rumor pages, but production systems need model slugs, SDK support, pricing, tool behavior, and migration notes from official docs. My recommendation is simple: do not hard-code a fake gpt-6 slug, do not promise GPT-6 behavior to users, and do not design launch plans around unconfirmed dates. Treat GPT-6 as a future model target while shipping on GPT-5.5-compatible architecture now. The takeaway: GPT-6 planning is useful, but GPT-6 production integration is premature until OpenAI publishes official API support. ...

If you are shipping on OpenAI Assistants API, migrate now because the platform has a fixed retirement timeline and the migration is an architecture rewrite, not a search-and-replace. The official deprecation notice was published with a one-year runway, so the hard part is usually your state model and tool integration, not endpoint syntax. In practice, you should move in phases: map resources, move prompts, manage history explicitly, and then harden observability before the 2026 shutdown. ...

GPT-5-Codex is OpenAI’s software-engineering-optimized model family, built specifically for agentic coding tasks like feature development, debugging, and large-scale refactoring. Unlike general-purpose GPT models, it runs exclusively through the Responses API and powers the OpenAI Codex platform, which reached 4 million weekly active developers by April 2026. What Is GPT-5-Codex? Understanding OpenAI’s SWE-Optimized Model Family GPT-5-Codex is a specialized series of language models from OpenAI, purpose-built for software engineering tasks that require long-horizon reasoning, multi-file context comprehension, and autonomous code execution. Unlike general-purpose models such as GPT-5.5, the GPT-5-Codex family is optimized for agentic workflows — meaning it can plan a multi-step coding task, interact with tools like shells and file systems, and iterate on results without continuous human intervention. The original gpt-5-codex model was released on September 23, 2025, priced at $1.25 per 1M input tokens and $10.00 per 1M output tokens, and was immediately positioned as the backbone of OpenAI’s Codex platform. A critical distinction developers must understand: GPT-5-Codex is available only through the Responses API, not the older Chat Completions API — this is not a minor implementation detail, but a paradigm shift in how you structure API calls, tool use, and conversation state. The model family has since expanded through GPT-5.1-Codex, GPT-5.2-Codex, and GPT-5.3-Codex, each improving SWE-Bench Pro scores while introducing better context compaction and reduced output token overhead. ...

GPT-5 Turbo — OpenAI’s fast, efficient variant marketed as GPT-5 mini and later GPT-5.4 mini — delivers native multimodal input (images and audio in a single API call), strict JSON structured outputs, and 400K-token context at roughly $0.15 per million input tokens. It is the practical choice for production applications where cost and latency matter more than raw intelligence ceiling. What Is GPT-5 Turbo? OpenAI’s Fast, Multimodal Model Explained GPT-5 Turbo refers to the fast, cost-optimized tier of OpenAI’s GPT-5 family — officially shipped as GPT-5 mini (August 7, 2025) and its successor GPT-5.4 mini (March 17, 2026). Just as GPT-4 Turbo was the speed-and-price-optimized version of GPT-4, GPT-5 Turbo is the developer-friendly workhorse of the fifth generation. GPT-5.4 mini runs more than 2x faster than the original GPT-5 mini while approaching flagship GPT-5.4 performance on reasoning and coding benchmarks. The model supports text, images, and audio natively — no add-on vision API, no separate speech-to-text pipeline. Context window reaches 400K tokens, more than 3x the 128K cap on GPT-4o mini. Pricing sits at approximately $0.15 per million input tokens and $0.60 per million output tokens. For developers building RAG pipelines, voice assistants, or document-parsing agents, GPT-5.4 mini hits the sweet spot between the budget Gemini Flash tier and the premium GPT-5.5 flagship. The result is a model that most real-world production apps can actually afford to run at scale. ...

OpenAI Agent Builder is a visual, no-code platform that lets you design, test, and deploy AI agents using a drag-and-drop canvas — without writing a single line of Python or calling the Agents SDK directly. Ramp built a production procurement agent in two sprints instead of two quarters; Rippling’s sales team automated five hours of weekly rep work with zero engineering involvement. What Is OpenAI Agent Builder? (And How It Differs from Custom GPTs and the SDK) OpenAI Agent Builder is a visual workflow platform — part of the OpenAI AgentKit ecosystem — that enables non-engineers to construct multi-step AI agents by connecting nodes on a canvas. Unlike Custom GPTs, which are essentially prompt wrappers around ChatGPT with optional file uploads, Agent Builder exposes the full reasoning loop: you can branch logic, chain sub-agents, add external tools, and define typed inputs and outputs. Unlike the Agents SDK (which requires Python code), Agent Builder operates entirely through a GUI. The key architectural difference is that Agent Builder agents are stateful by default, maintain conversation history across sessions, and can be exported as SDK-compatible code when you eventually need custom logic. According to OpenAI’s own announcements, LY Corporation built a complete internal work assistant agent in less than two hours using Agent Builder — something that previously required a dedicated engineering sprint. The global no-code AI platform market stood at $6.56 billion in 2025 and is projected to hit $75.14 billion by 2034, and Agent Builder is OpenAI’s direct answer to that demand curve. The takeaway: if you can use a spreadsheet, you can build an agent. ...