[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"portal-settings:stajic:en":3,"public-menus:all":38,"post:openai-agents-api-vs-agents-sdk-vs-responses-api-what-should-you-build-on-in-2026:en":205,"related:post:openai-agents-api-vs-agents-sdk-vs-responses-api-what-should-you-build-on-in-2026:en:1":1115},{"statusCode":4,"data":5,"message":37},200,{"tenantId":6,"lang":7,"defaultLang":8,"siteUrl":9,"contactEmail":10,"brandName":11,"logoUrl":12,"siteName":11,"siteDescription":13,"ogImage":10,"robotsIndex":14,"socialLinks":10,"reservedSlugs":10,"seoPolicy":15},"stajic","en","de","https:\u002F\u002Fstajic.de",null,"Stajic Platform","\u002FLogo_Planet.svg","Stajic Portal",true,{"branding":16,"relatedContent":17,"crossDomainLinks":18},{"logoUrl":12},{"enabled":14},[19,22,25,28,31,34],{"url":20,"label":21,"isActive":14,"showInFooter":14,"includeInSameAs":14},"https:\u002F\u002Ffigure.rocks","figure.rocks",{"url":23,"label":24,"isActive":14,"showInFooter":14,"includeInSameAs":14},"https:\u002F\u002Floving.rocks","loving.rocks",{"url":26,"label":27,"isActive":14,"showInFooter":14,"includeInSameAs":14},"https:\u002F\u002Fbazify.com","bazify.com",{"url":29,"label":30,"isActive":14,"showInFooter":14,"includeInSameAs":14},"https:\u002F\u002Fbazify.de","bazify.de",{"url":32,"label":33,"isActive":14,"showInFooter":14,"includeInSameAs":14},"https:\u002F\u002Fbazify.at","bazify.at",{"url":35,"label":36,"isActive":14,"showInFooter":14,"includeInSameAs":14},"https:\u002F\u002Fbazify.ba","bazify.ba","Portal settings resolved",[39,45],{"id":40,"name":41,"location":42,"isActive":14,"isDefault":43,"items":44},1,"main-navigation","header",false,[],{"id":46,"name":47,"location":48,"isActive":14,"isDefault":14,"items":49},4,"main-menu","sidebar",[50,66,79,93,103,118,133],{"id":51,"title":52,"url":60,"target":61,"icon":62,"isActive":14,"type":63,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":64,"portfolioId":10,"children":65},"item-18",{"de":53,"en":54,"es":55,"fr":56,"it":54,"ru":57,"sr":58,"zh":59},"Startseite","Home","Inicio","Accueil","Главная","Почетна","首页","\u002Ffull-stack-web-developer-munich-performance-seo-and-maintainable-builds","_self","i-lucide-home","page",111,[],{"id":67,"title":68,"url":75,"target":61,"icon":76,"isActive":14,"type":63,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":77,"portfolioId":10,"children":78},"item-22",{"de":69,"en":69,"es":70,"fr":69,"it":71,"ru":72,"sr":73,"zh":74},"Vision","Visión","Visione","Видение","Визија","想象","\u002Fueber-uns-webdesign-muenchen-webaplikation","i-lucide-eye",113,[],{"id":80,"title":81,"url":89,"target":61,"icon":90,"isActive":14,"type":63,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":91,"portfolioId":10,"children":92},"item-19",{"de":82,"en":83,"es":84,"fr":83,"it":85,"ru":86,"sr":87,"zh":88},"Leistungen","Services","Servicios","Servizi","Услуги","Услуге","服务","\u002Fservices-dienstleistungen-muenchen","i-lucide-wrench",116,[],{"id":94,"title":95,"url":99,"target":61,"icon":100,"isActive":14,"type":63,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":101,"portfolioId":10,"children":102},"item-23",{"de":96,"en":96,"es":96,"fr":96,"it":96,"ru":97,"sr":97,"zh":98},"Blog","Блог","博客","\u002Fblog","i-lucide-book-open",112,[],{"id":104,"title":105,"url":114,"target":61,"icon":115,"isActive":14,"type":63,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":116,"portfolioId":10,"children":117},"item-32",{"de":106,"en":107,"es":108,"fr":109,"it":110,"ru":111,"sr":112,"zh":113},"Neue Technologien","New Technologies","Nuevas tecnologías","Nouvelles technologies","Nuove tecnologie","Новые технологии","Нове технологије","新技术！","\u002Fneue-webtechnologien","i-lucide-sparkles",122,[],{"id":119,"title":120,"url":129,"target":61,"icon":130,"isActive":14,"type":63,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":131,"portfolioId":10,"children":132},"item-20",{"de":121,"en":122,"es":123,"fr":124,"it":125,"ru":126,"sr":127,"zh":128},"Kontakt","Contact us!","Contacto","Contact","Contatto","Контакт","Контактирајте нас","联系我们！","\u002Fcontact","i-lucide-mail",115,[],{"id":134,"title":135,"url":144,"target":61,"icon":145,"isActive":14,"type":63,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":146,"portfolioId":10,"children":147},"item-21",{"de":136,"en":137,"es":138,"fr":139,"it":140,"ru":141,"sr":142,"zh":143},"Unsere Arbeit","Our Work","Nuestro trabajo","Nos réalisations","I nostri lavori","Наши работы","Наши радови","文件夹","\u002Fportfolio","i-lucide-briefcase",114,[148,161,175,181,193],{"id":149,"title":150,"url":144,"target":61,"icon":159,"isActive":14,"type":63,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":146,"portfolioId":10,"children":160},"item-24",{"de":151,"en":152,"es":153,"fr":154,"it":155,"ru":156,"sr":157,"zh":158},"Alle Projekte","All Projects","Todos los proyectos","Tous les projets","Tutti i progetti","Все проекты","Сви пројекти","所有项目","i-lucide-grid-3x3",[],{"id":162,"title":163,"url":171,"target":61,"icon":172,"isActive":14,"type":173,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":10,"portfolioId":10,"children":174},"item-29",{"de":164,"en":165,"es":166,"fr":167,"it":168,"ru":169,"sr":170,"zh":143},"Local Roots, Global Reach","Local Roots - Global Reach","Empresa local ","Entreprise locale","Azienda locale","Местная компания","Локално предузеће глобално тржиште","\u002Fportfolio\u002Flocal-roots-global-reach-communication-media-systems-for-modern-business","i-lucide-folder","custom",[],{"id":176,"title":177,"url":179,"target":61,"icon":172,"isActive":14,"type":173,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":10,"portfolioId":10,"children":180},"item-28",{"de":178,"en":178,"es":178,"fr":178,"it":178,"ru":178,"sr":178,"zh":178},"Solr Suggester","\u002Fportfolio\u002Fsolr-fuzzy-suggester-und-solr-infix-suggester-abfrage-ueber-ajax-und-filterung",[],{"id":182,"title":183,"url":191,"target":61,"icon":172,"isActive":14,"type":173,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":10,"portfolioId":10,"children":192},"item-27",{"de":184,"en":185,"es":186,"fr":187,"it":188,"ru":189,"sr":190,"zh":185},"Firmenwebseite SEO","Company Website SEO","Sitio web corporativo SEO","Site web d’entreprise SEO","Sito web aziendale SEO","Корпоративный сайт SEO","Пословна веб-страница SEO","\u002Fportfolio\u002Fseo-sem-branding-mobile-webseite-muenchen",[],{"id":194,"title":195,"url":203,"target":61,"icon":172,"isActive":14,"type":173,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":10,"portfolioId":10,"children":204},"item-31",{"de":196,"en":197,"es":198,"fr":199,"it":200,"ru":201,"sr":202,"zh":197},"Digitalisierungsportal","Digitalization Portal","Portal de digitalización","Portail de numérisation","Portale di digitalizzazione","Портал цифровизации","Портал за дигитализацију","\u002Fportfolio\u002Fdigitalisierungsportal-archiv-museum-bibliothek-ead-lido-mets-mods",[],{"statusCode":4,"data":206,"message":1114},{"id":207,"title":208,"slug":209,"content":210,"contentJson":211,"excerpt":796,"featuredImage":797,"featuredImageAlt":798,"featuredImageCaption":10,"featuredImageTitle":10,"featuredImageCopyright":10,"featuredImageAuthor":10,"featuredImageSourceUrl":10,"featuredImageLicense":10,"featuredImageIsAiGenerated":43,"status":799,"publishedAt":800,"createdAt":801,"updatedAt":802,"seoLocalePaths":803,"categories":812,"author":823,"translations":828},"473","OpenAI Agents API vs Agents SDK vs Responses API: What Should You Build On in 2026?","openai-agents-api-vs-agents-sdk-vs-responses-api-what-should-you-build-on-in-2026","{\"time\":1790352010644,\"blocks\":[{\"id\":\"75qcDhG72q\",\"type\":\"tableOfContents\",\"data\":{\"title\":\"Contents\",\"minLevel\":2,\"maxLevel\":3},\"tunes\":{}},{\"id\":\"intro\",\"type\":\"paragraph\",\"data\":{\"text\":\"OpenAI's agent stack changed materially in September 2026. The new Agents API introduced a managed Codex harness for durable cloud agents, while the older Agents SDK moved into a feature-complete maintenance phase. The Responses API remains the lower-level surface for applications that want direct model calls or to own the agent loop themselves. These are not three interchangeable wrappers around the same thing: they place the runtime boundary in different places.\"},\"tunes\":{}},{\"id\":\"direct\",\"type\":\"callout\",\"data\":{\"variant\":\"info\",\"title\":\"Direct answer\",\"body\":\"\u003Cstrong>For a new OpenAI-native agent application in September 2026, start with the Agents API unless you have a concrete reason to own more of the runtime.\u003C\u002Fstrong> Use the Responses API when your application should own the loop, state strategy, and orchestration. Keep the Agents SDK for existing applications or short-term gaps where the Agents API does not yet support a required capability. If you want the Codex harness itself but need to run it in infrastructure you operate, evaluate the Codex SDK rather than forcing the Agents SDK into that role.\"},\"tunes\":{}},{\"id\":\"date-warning\",\"type\":\"callout\",\"data\":{\"variant\":\"warning\",\"title\":\"Time-sensitive architecture decision\",\"body\":\"This article reflects OpenAI's platform state on \u003Cstrong>25 September 2026\u003C\u002Fstrong>. The Agents API launched in public beta on 10 September 2026. Beta surfaces, feature coverage, pricing, and migration guidance can change; verify current documentation before committing a production architecture.\"},\"tunes\":{}},{\"id\":\"model-note\",\"type\":\"callout\",\"data\":{\"variant\":\"note\",\"title\":\"The decision model used here\",\"body\":\"The Runtime Ownership Test below is a practical architecture model, not an OpenAI product taxonomy. It asks which parts of the agent runtime your team must control versus which parts you want OpenAI to operate.\"},\"tunes\":{}},{\"id\":\"h-boundary\",\"type\":\"header\",\"data\":{\"text\":\"The architecture changed: choose a runtime boundary, not a library\",\"level\":2},\"tunes\":{}},{\"id\":\"p-boundary-1\",\"type\":\"paragraph\",\"data\":{\"text\":\"The important decision is no longer simply “Which SDK should I install?” It is who owns the harness, the agent loop, durable session state, context compaction, recovery, execution environment, and application lifecycle.\"},\"tunes\":{}},{\"id\":\"p-boundary-2\",\"type\":\"paragraph\",\"data\":{\"text\":\"OpenAI's current Agents overview makes this boundary explicit. The Agents API runs a hosted Codex harness and manages orchestration plus durable session state. The Responses API provides model responses and hosted capabilities while your application owns the surrounding agent loop. The Agents SDK runs the loop in your application and is now feature complete rather than the forward path for major new agent features.\"},\"tunes\":{}},{\"id\":\"h-short\",\"type\":\"header\",\"data\":{\"text\":\"The short comparison\",\"level\":2},\"tunes\":{}},{\"id\":\"short-table\",\"type\":\"table\",\"data\":{\"withHeadings\":true,\"stretched\":false,\"content\":[[\"Option\",\"Best fit in 2026\",\"Who owns the agent loop?\",\"Session \u002F context responsibility\",\"Strategic status\"],[\"Agents API\",\"New OpenAI-native durable agents\",\"OpenAI-managed Codex harness\",\"OpenAI manages sessions, orchestration, compaction and recovery\",\"Recommended starting point for new agent apps; public beta\"],[\"Responses API\",\"Direct model integrations and custom agent runtimes\",\"Your application\",\"You choose response chaining, Conversations, storage and loop logic\",\"Core API primitive; recommended over Chat Completions for new projects\"],[\"Agents SDK\",\"Existing SDK applications or temporary capability gaps\",\"Your application via the SDK runner\",\"Your application operates deployment, storage and runtime behaviour\",\"Feature complete; maintenance and compatibility continue, major new features not planned\"],[\"Codex SDK\",\"Codex harness in infrastructure you operate\",\"Codex harness in your environment\",\"You operate harness hosting and lifecycle\",\"Separate option when you want the harness without the hosted Agents API runtime\"]]},\"tunes\":{}},{\"id\":\"h-agents-api\",\"type\":\"header\",\"data\":{\"text\":\"1. Agents API: managed harness, durable cloud agent\",\"level\":2},\"tunes\":{}},{\"id\":\"p-api-1\",\"type\":\"paragraph\",\"data\":{\"text\":\"The Agents API exposes the Codex harness through an OpenAI-managed service. OpenAI manages sessions, orchestration, context compaction, and recovery. Your application still provides tools and chooses the execution environment.\"},\"tunes\":{}},{\"id\":\"p-api-2\",\"type\":\"paragraph\",\"data\":{\"text\":\"That last distinction matters. “Managed agent” does not necessarily mean “all compute runs inside OpenAI.” The Agents API architecture supports no environment, an OpenAI-hosted environment, or a self-hosted environment connected to the hosted harness. With a self-hosted environment, your application owns provisioning, reconnection, shutdown, and persistent files while the harness remains managed.\"},\"tunes\":{}},{\"id\":\"p-api-3\",\"type\":\"paragraph\",\"data\":{\"text\":\"The Agents API is therefore a runtime service, not merely a request format. Sessions can persist, stream progress, receive additional tasks, use tools, work with files, and recover across long-running work.\"},\"tunes\":{}},{\"id\":\"h-api-gain\",\"type\":\"header\",\"data\":{\"text\":\"What you gain with the Agents API\",\"level\":3},\"tunes\":{}},{\"id\":\"api-gains\",\"type\":\"list\",\"data\":{\"style\":\"unordered\",\"meta\":{},\"items\":[\"A managed Codex harness instead of building and operating the main agent loop yourself.\",\"Durable sessions for work that spans turns and long-running tasks.\",\"Managed orchestration, context compaction, and recovery.\",\"OpenAI-hosted or self-hosted execution environments, depending on workload requirements.\",\"Streaming and webhooks for progress and lifecycle events.\",\"A platform direction that OpenAI explicitly recommends for new agent applications.\"]},\"tunes\":{}},{\"id\":\"h-api-own\",\"type\":\"header\",\"data\":{\"text\":\"What you still own\",\"level\":3},\"tunes\":{}},{\"id\":\"api-own\",\"type\":\"list\",\"data\":{\"style\":\"unordered\",\"meta\":{},\"items\":[\"Your product and application server.\",\"Function-tool implementations and business logic.\",\"Authorization and policy decisions around your own systems.\",\"The execution environment lifecycle when you choose self-hosted compute.\",\"Evaluation, acceptance criteria, domain-specific guardrails, and the decision of what the agent is allowed to do.\"]},\"tunes\":{}},{\"id\":\"h-responses\",\"type\":\"header\",\"data\":{\"text\":\"2. Responses API: own the loop, use the platform primitives\",\"level\":2},\"tunes\":{}},{\"id\":\"p-resp-1\",\"type\":\"paragraph\",\"data\":{\"text\":\"The Responses API is the lower-level choice when you want OpenAI model and tool capabilities without delegating the overall agent runtime. OpenAI describes Responses as the recommended API primitive for new projects and as an evolution of Chat Completions with built-in tools, multi-turn state options, multimodal input, and agentic tool use.\"},\"tunes\":{}},{\"id\":\"p-resp-2\",\"type\":\"paragraph\",\"data\":{\"text\":\"A Responses request can itself invoke tools, but your application remains responsible for the larger workflow when you build an agent around it. That means your code decides how to persist application state, when to continue, how to recover, how to coordinate specialists, how to compact long histories, and how to represent resumable work.\"},\"tunes\":{}},{\"id\":\"p-resp-3\",\"type\":\"paragraph\",\"data\":{\"text\":\"This is not inherently inferior. It is the right boundary when agent behaviour must be deeply embedded in existing application logic, when you need a custom state model, or when a managed harness would hide control you actually need.\"},\"tunes\":{}},{\"id\":\"h-sdk\",\"type\":\"header\",\"data\":{\"text\":\"3. Agents SDK: supported, but no longer the default forward path\",\"level\":2},\"tunes\":{}},{\"id\":\"p-sdk-1\",\"type\":\"paragraph\",\"data\":{\"text\":\"The Agents SDK remains an open-source framework for running agent workflows in your application. It provides agent definitions, tools, handoffs, guardrails, tracing, sessions, and the runner loop in TypeScript and Python.\"},\"tunes\":{}},{\"id\":\"p-sdk-2\",\"type\":\"paragraph\",\"data\":{\"text\":\"But its strategic status changed. OpenAI now labels the Agents SDK feature complete: maintenance, security fixes, critical bug fixes, and compatibility work continue, but major new features are not planned. OpenAI recommends the Agents API for new applications.\"},\"tunes\":{}},{\"id\":\"p-sdk-3\",\"type\":\"paragraph\",\"data\":{\"text\":\"That does not mean an existing SDK application should be rewritten immediately. It means the architecture should stop assuming that the SDK is where the next major agent-runtime capabilities will land.\"},\"tunes\":{}},{\"id\":\"sdk-warning\",\"type\":\"callout\",\"data\":{\"variant\":\"warning\",\"title\":\"Do not translate “feature complete” into “deprecated”\",\"body\":\"OpenAI has not described the Agents SDK as unsupported. Existing applications can continue to use it, and maintenance, security, critical bug fixes, and compatibility work continue. The important change is that major new features are not planned and new applications are directed to the Agents API.\"},\"tunes\":{}},{\"id\":\"h-codex-sdk\",\"type\":\"header\",\"data\":{\"text\":\"Where the Codex SDK fits\",\"level\":2},\"tunes\":{}},{\"id\":\"p-codex-1\",\"type\":\"paragraph\",\"data\":{\"text\":\"The current choice is not a simple three-way fork. OpenAI's runtime overview includes the Codex SDK as the option for running the Codex harness in infrastructure you operate. That is architecturally different from both the hosted Agents API and the Agents SDK.\"},\"tunes\":{}},{\"id\":\"p-codex-2\",\"type\":\"paragraph\",\"data\":{\"text\":\"If your real requirement is “I want the Codex harness, but I need to operate it myself,” the Codex SDK is the surface to evaluate. If your requirement is “I want to own the loop around model calls,” evaluate Responses. If your requirement is “I already have a working Agents SDK application,” the existing SDK can remain valid while you plan against its maintenance status.\"},\"tunes\":{}},{\"id\":\"h-test\",\"type\":\"header\",\"data\":{\"text\":\"The Runtime Ownership Test\",\"level\":2},\"tunes\":{}},{\"id\":\"p-test-intro\",\"type\":\"paragraph\",\"data\":{\"text\":\"A useful architecture decision starts by deciding what your team must own. Score each requirement as either must control, prefer to control, or prefer managed.\"},\"tunes\":{}},{\"id\":\"ownership-test\",\"type\":\"comparison\",\"data\":{\"title\":\"Runtime Ownership Test\",\"layout\":\"table\",\"columns\":[{\"id\":\"decision\",\"label\":\"Decision\"},{\"id\":\"managed\",\"label\":\"If you prefer managed\"},{\"id\":\"control\",\"label\":\"If you require control\"}],\"rows\":[{\"id\":\"loop\",\"label\":\"Agent loop\",\"values\":[\"\",\"\",\"\"]},{\"id\":\"session\",\"label\":\"Durable sessions\",\"values\":[\"\",\"\",\"\"]},{\"id\":\"harness\",\"label\":\"Harness runtime\",\"values\":[\"\",\"\",\"\"]},{\"id\":\"environment\",\"label\":\"Execution environment\",\"values\":[\"\",\"\",\"\"]},{\"id\":\"orchestration\",\"label\":\"Orchestration semantics\",\"values\":[\"\",\"\",\"\"]},{\"id\":\"portability\",\"label\":\"Provider \u002F transport flexibility\",\"values\":[\"\",\"\",\"\"]},{\"id\":\"ops\",\"label\":\"Operational burden\",\"values\":[\"\",\"\",\"\"]}]},\"tunes\":{}},{\"id\":\"h-tree\",\"type\":\"header\",\"data\":{\"text\":\"A decision tree for new systems\",\"level\":2},\"tunes\":{}},{\"id\":\"decision-flow\",\"type\":\"processFlow\",\"data\":{\"title\":\"Choose the runtime by the control boundary\",\"orientation\":\"auto\",\"steps\":[{\"label\":\"1. Is this a new agent application?\",\"description\":\"If no, do not migrate solely because a newer surface exists. Evaluate the current application's actual constraints first.\"},{\"label\":\"2. Do you want a managed long-running agent harness?\",\"description\":\"If yes, start with the Agents API as OpenAI's recommended path for new agent applications.\"},{\"label\":\"3. Do you need the Codex harness but must operate it yourself?\",\"description\":\"Evaluate the Codex SDK rather than rebuilding harness behaviour on top of the Agents SDK.\"},{\"label\":\"4. Do you need to own the agent loop and state model?\",\"description\":\"Use the Responses API as the lower-level platform primitive and build the loop around it.\"},{\"label\":\"5. Are you already on the Agents SDK?\",\"description\":\"Continue if it meets requirements; major new features are not planned, so treat future platform adoption as an explicit roadmap decision.\"},{\"label\":\"6. Is a required capability missing from the Agents API?\",\"description\":\"OpenAI explicitly allows the Agents SDK as a short-term option for new applications that need unsupported capabilities.\"},{\"label\":\"7. Validate with a production-shaped spike\",\"description\":\"Test tools, environment, approvals, latency, observability, failure recovery, and lifecycle before locking the architecture.\"}]},\"tunes\":{}},{\"id\":\"h-not-drive\",\"type\":\"header\",\"data\":{\"text\":\"What should not drive the decision\",\"level\":2},\"tunes\":{}},{\"id\":\"weak-rules\",\"type\":\"table\",\"data\":{\"withHeadings\":true,\"stretched\":false,\"content\":[[\"Weak decision rule\",\"Why it fails\",\"Better question\"],[\"“The newest API must be best.”\",\"Newer can be strategically preferred while still lacking a capability you need.\",\"Which runtime responsibilities should be managed versus application-owned?\"],[\"“We already know the SDK.”\",\"Team familiarity can preserve an architecture whose roadmap has changed.\",\"What is the cost of staying versus moving over the next product cycle?\"],[\"“Managed means no infrastructure.”\",\"Agents API can still use self-hosted environments and your application still owns product logic.\",\"Which infrastructure layer is actually being delegated?\"],[\"“Responses is only for simple calls.”\",\"Responses provides built-in tools and stateful primitives; it can be the foundation of custom agent loops.\",\"Do we need the platform to own the harness, or only model\u002Ftool primitives?\"],[\"“Feature complete means we must migrate now.”\",\"The SDK remains maintained for existing applications.\",\"What concrete future requirement is blocked by staying?\"]]},\"tunes\":{}},{\"id\":\"h-migration\",\"type\":\"header\",\"data\":{\"text\":\"Migration is an architectural change, not an import rename\",\"level\":2},\"tunes\":{}},{\"id\":\"p-migration-1\",\"type\":\"paragraph\",\"data\":{\"text\":\"Moving from the Agents SDK to the Agents API changes ownership. In the SDK, the loop runs in your application. In the Agents API, OpenAI runs the harness and session while your application integrates through tasks, events, tools, and environment boundaries.\"},\"tunes\":{}},{\"id\":\"p-migration-2\",\"type\":\"paragraph\",\"data\":{\"text\":\"A real migration plan therefore needs to map session state, custom orchestration, handoffs, tool execution, approvals, storage, tracing, retries, failure recovery, environment lifecycle, and any provider-specific abstractions. Code volume may fall while operational assumptions change.\"},\"tunes\":{}},{\"id\":\"h-migration-inventory\",\"type\":\"header\",\"data\":{\"text\":\"The migration inventory\",\"level\":3},\"tunes\":{}},{\"id\":\"migration-list\",\"type\":\"list\",\"data\":{\"style\":\"unordered\",\"meta\":{},\"items\":[\"Agent definitions and instruction ownership.\",\"Tool definitions and where each tool executes.\",\"Handoffs, manager\u002Fspecialist patterns, and subagent behaviour.\",\"Session identifiers, conversation state, resumability, and history retention.\",\"Human approvals and interruption semantics.\",\"Custom context trimming or compaction logic.\",\"Tracing, evals, observability, and production debugging.\",\"Self-hosted files, containers, private-network access, or other execution dependencies.\",\"Provider abstraction or non-OpenAI model dependencies.\",\"Retry, timeout, idempotency, recovery, and lifecycle assumptions.\"]},\"tunes\":{}},{\"id\":\"h-beta\",\"type\":\"header\",\"data\":{\"text\":\"Public beta changes the risk model\",\"level\":2},\"tunes\":{}},{\"id\":\"p-beta-1\",\"type\":\"paragraph\",\"data\":{\"text\":\"The Agents API is the recommended direction for new agent applications, but it is also in public beta. Those facts are not contradictory. Strategic direction answers “where is the platform going?” Beta status answers “how much interface and operational change should I budget for?”\"},\"tunes\":{}},{\"id\":\"p-beta-2\",\"type\":\"paragraph\",\"data\":{\"text\":\"For production systems, isolate the integration behind an application boundary. Keep domain state, permissions, audit data, and business rules outside vendor-specific session objects where possible. This makes it easier to absorb API evolution without turning the agent runtime into the source of truth for your entire product.\"},\"tunes\":{}},{\"id\":\"h-default\",\"type\":\"header\",\"data\":{\"text\":\"A practical default architecture\",\"level\":2},\"tunes\":{}},{\"id\":\"p-default-1\",\"type\":\"paragraph\",\"data\":{\"text\":\"For many new OpenAI-native applications, a reasonable 2026 default is: Agents API for the managed harness and durable session, application-owned domain services and authorization, explicit function tools for business actions, and either OpenAI-hosted or self-hosted execution depending on data and compute requirements.\"},\"tunes\":{}},{\"id\":\"p-default-2\",\"type\":\"paragraph\",\"data\":{\"text\":\"That keeps the agent runtime powerful without making it the owner of business truth. The application still decides what a user may do, which data is authoritative, which actions require approval, and how results are validated.\"},\"tunes\":{}},{\"id\":\"ref-reliability\",\"type\":\"referralArticle\",\"data\":{\"url\":\"https:\u002F\u002Fstajic.de\u002Fblog\u002Fai-agent-reliability-why-the-final-answer-is-not-enough\",\"title\":\"AI Agent Reliability: Why the Final Answer Is Not Enough\",\"excerpt\":\"A managed harness reduces operational burden, but reliability still requires traceable execution, explicit acceptance criteria and evaluation beyond the final answer.\",\"ctaLabel\":\"Read the reliability article\"},\"tunes\":{}},{\"id\":\"h-change\",\"type\":\"header\",\"data\":{\"text\":\"What would change this answer?\",\"level\":2},\"tunes\":{}},{\"id\":\"p-change-1\",\"type\":\"paragraph\",\"data\":{\"text\":\"The recommendation changes if the Agents API adds or removes capabilities, exits beta with different contracts, changes environment or pricing boundaries, or introduces migration tooling that reduces ownership differences. It also changes if your application depends on provider portability, custom orchestration semantics, local-only execution, or a capability the hosted harness cannot support.\"},\"tunes\":{}},{\"id\":\"p-change-2\",\"type\":\"paragraph\",\"data\":{\"text\":\"For an existing Agents SDK application, the answer also changes with migration cost. If the system is stable, well evaluated, and not blocked by the SDK's feature-complete status, immediate migration may create more risk than value. If the product roadmap depends on capabilities landing only in the Agents API, delaying migration can create a different kind of debt.\"},\"tunes\":{}},{\"id\":\"h-limitations\",\"type\":\"header\",\"data\":{\"text\":\"Limitations\",\"level\":2},\"tunes\":{}},{\"id\":\"p-limit-1\",\"type\":\"paragraph\",\"data\":{\"text\":\"This comparison focuses on runtime ownership and OpenAI's stated platform direction. It does not benchmark latency, quality, or total cost for a specific workload. Those properties depend on model choice, tool usage, environment, task length, caching, sandbox usage, and application architecture.\"},\"tunes\":{}},{\"id\":\"p-limit-2\",\"type\":\"paragraph\",\"data\":{\"text\":\"The Agents API is also new enough that production experience is still accumulating. A design should therefore be validated with representative workloads rather than chosen solely from product positioning.\"},\"tunes\":{}},{\"id\":\"h-conclusion\",\"type\":\"header\",\"data\":{\"text\":\"Conclusion\",\"level\":2},\"tunes\":{}},{\"id\":\"p-conclusion-1\",\"type\":\"paragraph\",\"data\":{\"text\":\"The 2026 OpenAI agent decision is fundamentally about runtime ownership. Agents API means OpenAI owns more of the harness and durable-session machinery. Responses means your application owns the loop around platform primitives. The Agents SDK remains valid for existing systems but is no longer the default destination for major new agent-runtime features.\"},\"tunes\":{}},{\"id\":\"p-conclusion-2\",\"type\":\"paragraph\",\"data\":{\"text\":\"For a new application, follow the platform direction unless a real requirement pushes you lower in the stack. Start with the Agents API, move to Responses when you need to own the loop, evaluate Codex SDK when you need the harness in your infrastructure, and keep the Agents SDK where existing investments or temporary capability gaps justify it.\"},\"tunes\":{}},{\"id\":\"h-faq\",\"type\":\"header\",\"data\":{\"text\":\"FAQ\",\"level\":2},\"tunes\":{}},{\"id\":\"faq\",\"type\":\"faq\",\"data\":{\"title\":\"OpenAI agent runtime choices in 2026\",\"items\":[{\"id\":\"faq1\",\"question\":\"Should I use the OpenAI Agents API or Agents SDK for a new project?\",\"answer\":\"OpenAI currently recommends the Agents API for new agent applications. The Agents SDK is feature complete and remains supported for existing applications, with maintenance, security, critical bug fixes and compatibility work continuing.\"},{\"id\":\"faq2\",\"question\":\"Is the Agents SDK deprecated?\",\"answer\":\"OpenAI describes it as feature complete, not as unsupported. Major new features are not planned, but maintenance, security fixes, critical bug fixes and compatibility work continue.\"},{\"id\":\"faq3\",\"question\":\"When should I use the Responses API instead of the Agents API?\",\"answer\":\"Use Responses when your application should own the agent loop, state strategy, orchestration and continuation logic while still using OpenAI models and platform tools.\"},{\"id\":\"faq4\",\"question\":\"Does the Agents API require OpenAI-hosted compute?\",\"answer\":\"No. The Agents API can use no execution environment, an OpenAI-hosted environment, or a self-hosted environment connected to the managed harness.\"},{\"id\":\"faq5\",\"question\":\"Where does the Codex SDK fit?\",\"answer\":\"OpenAI positions the Codex SDK for running the Codex harness in infrastructure you operate. It is the relevant option when you want the harness but not the hosted Agents API runtime.\"},{\"id\":\"faq6\",\"question\":\"Should an existing Agents SDK app migrate immediately?\",\"answer\":\"Not automatically. Evaluate whether the current system is blocked by the SDK's feature-complete status, whether required capabilities exist in the Agents API, and whether the migration benefit exceeds the operational and architectural change.\"}]},\"tunes\":{}},{\"id\":\"h-glossary\",\"type\":\"header\",\"data\":{\"text\":\"Glossary\",\"level\":2},\"tunes\":{}},{\"id\":\"glossary\",\"type\":\"glossary\",\"data\":{\"title\":\"Key runtime terms\",\"entries\":[{\"term\":\"Harness\",\"definition\":\"The runtime loop and supporting machinery that coordinates model calls, tools, context, sessions and agent execution.\",\"anchor\":\"harness\"},{\"term\":\"Agents API\",\"definition\":\"OpenAI's managed API for durable cloud agents using a hosted Codex harness.\",\"anchor\":\"agents-api\"},{\"term\":\"Responses API\",\"definition\":\"OpenAI's lower-level API primitive for model responses, hosted tools and stateful interactions around which applications can build their own agent loop.\",\"anchor\":\"responses-api\"},{\"term\":\"Agents SDK\",\"definition\":\"OpenAI's open-source framework for running agent workflows in application code; feature complete as of September 2026.\",\"anchor\":\"agents-sdk\"},{\"term\":\"Codex SDK\",\"definition\":\"The runtime option OpenAI lists for running the Codex harness in infrastructure you operate.\",\"anchor\":\"codex-sdk\"},{\"term\":\"Runtime ownership\",\"definition\":\"The architectural boundary describing which parts of the agent loop, session state, execution environment and lifecycle are operated by the platform versus the application.\",\"anchor\":\"runtime-ownership\"}]},\"tunes\":{}},{\"id\":\"h-sources\",\"type\":\"header\",\"data\":{\"text\":\"Primary sources and further reading\",\"level\":2},\"tunes\":{}},{\"id\":\"src-launch\",\"type\":\"linkTool\",\"data\":{\"link\":\"https:\u002F\u002Fopenai.com\u002Findex\u002Fintroducing-the-agents-api\u002F\",\"meta\":{\"image\":{\"url\":\"\"},\"title\":\"OpenAI — Introducing the Agents API\",\"description\":\"Launch announcement for the Agents API on 10 September 2026, describing the managed Codex harness and public beta.\"}},\"tunes\":{}},{\"id\":\"src-agents-overview\",\"type\":\"linkTool\",\"data\":{\"link\":\"https:\u002F\u002Fdevelopers.openai.com\u002Fapi\u002Fdocs\u002Fguides\u002Fagents\",\"meta\":{\"image\":{\"url\":\"\"},\"title\":\"OpenAI — Agents runtime overview\",\"description\":\"Current comparison of Agents API, Codex SDK and Responses API, including the support status of the Agents SDK.\"}},\"tunes\":{}},{\"id\":\"src-agents-api\",\"type\":\"linkTool\",\"data\":{\"link\":\"https:\u002F\u002Fdevelopers.openai.com\u002Fapi\u002Fdocs\u002Fguides\u002Fagents-api\u002Foverview\",\"meta\":{\"image\":{\"url\":\"\"},\"title\":\"OpenAI — Agents API overview\",\"description\":\"Documentation for durable cloud agents, sessions, orchestration, context compaction, recovery and environment choices.\"}},\"tunes\":{}},{\"id\":\"src-architecture\",\"type\":\"linkTool\",\"data\":{\"link\":\"https:\u002F\u002Fdevelopers.openai.com\u002Fapi\u002Fdocs\u002Fguides\u002Fagents-api\u002Farchitecture\",\"meta\":{\"image\":{\"url\":\"\"},\"title\":\"OpenAI — Agents API architecture\",\"description\":\"Architecture boundary between the hosted harness, application server and no\u002Fopenai-hosted\u002Fself-hosted execution environments.\"}},\"tunes\":{}},{\"id\":\"src-sdk\",\"type\":\"linkTool\",\"data\":{\"link\":\"https:\u002F\u002Fdevelopers.openai.com\u002Fapi\u002Fdocs\u002Fguides\u002Fagents\u002Fsdk\",\"meta\":{\"image\":{\"url\":\"\"},\"title\":\"OpenAI — Agents SDK\",\"description\":\"Current Agents SDK support notice and explanation of the application-owned agent loop.\"}},\"tunes\":{}},{\"id\":\"src-responses\",\"type\":\"linkTool\",\"data\":{\"link\":\"https:\u002F\u002Fdevelopers.openai.com\u002Fapi\u002Fdocs\u002Fguides\u002Fmigrate-to-responses\",\"meta\":{\"image\":{\"url\":\"\"},\"title\":\"OpenAI — Migrate to the Responses API\",\"description\":\"Current Responses API positioning, built-in tools, stateful context and agentic primitives.\"}},\"tunes\":{}},{\"id\":\"toc\",\"type\":\"tableOfContents\",\"data\":{\"title\":\"Contents\",\"minLevel\":2,\"maxLevel\":3},\"tunes\":{}}],\"version\":\"2.31.6\"}",{"time":212,"blocks":213,"version":795},1790352010644,[214,222,228,236,243,250,255,260,265,270,306,311,316,321,326,331,345,350,361,366,371,376,381,386,391,396,401,407,412,417,422,427,432,478,483,512,517,546,551,556,561,566,582,587,592,597,602,607,612,621,626,631,636,641,646,651,656,661,666,671,701,706,731,736,746,755,764,773,782,791],{"id":215,"data":216,"type":220,"tunes":221},"75qcDhG72q",{"title":217,"maxLevel":218,"minLevel":219},"Contents",3,2,"tableOfContents",{},{"id":223,"data":224,"type":226,"tunes":227},"intro",{"text":225},"OpenAI's agent stack changed materially in September 2026. The new Agents API introduced a managed Codex harness for durable cloud agents, while the older Agents SDK moved into a feature-complete maintenance phase. The Responses API remains the lower-level surface for applications that want direct model calls or to own the agent loop themselves. These are not three interchangeable wrappers around the same thing: they place the runtime boundary in different places.","paragraph",{},{"id":229,"data":230,"type":234,"tunes":235},"direct",{"body":231,"title":232,"variant":233},"\u003Cstrong>For a new OpenAI-native agent application in September 2026, start with the Agents API unless you have a concrete reason to own more of the runtime.\u003C\u002Fstrong> Use the Responses API when your application should own the loop, state strategy, and orchestration. Keep the Agents SDK for existing applications or short-term gaps where the Agents API does not yet support a required capability. If you want the Codex harness itself but need to run it in infrastructure you operate, evaluate the Codex SDK rather than forcing the Agents SDK into that role.","Direct answer","info","callout",{},{"id":237,"data":238,"type":234,"tunes":242},"date-warning",{"body":239,"title":240,"variant":241},"This article reflects OpenAI's platform state on \u003Cstrong>25 September 2026\u003C\u002Fstrong>. The Agents API launched in public beta on 10 September 2026. Beta surfaces, feature coverage, pricing, and migration guidance can change; verify current documentation before committing a production architecture.","Time-sensitive architecture decision","warning",{},{"id":244,"data":245,"type":234,"tunes":249},"model-note",{"body":246,"title":247,"variant":248},"The Runtime Ownership Test below is a practical architecture model, not an OpenAI product taxonomy. It asks which parts of the agent runtime your team must control versus which parts you want OpenAI to operate.","The decision model used here","note",{},{"id":251,"data":252,"type":42,"tunes":254},"h-boundary",{"text":253,"level":219},"The architecture changed: choose a runtime boundary, not a library",{},{"id":256,"data":257,"type":226,"tunes":259},"p-boundary-1",{"text":258},"The important decision is no longer simply “Which SDK should I install?” It is who owns the harness, the agent loop, durable session state, context compaction, recovery, execution environment, and application lifecycle.",{},{"id":261,"data":262,"type":226,"tunes":264},"p-boundary-2",{"text":263},"OpenAI's current Agents overview makes this boundary explicit. The Agents API runs a hosted Codex harness and manages orchestration plus durable session state. The Responses API provides model responses and hosted capabilities while your application owns the surrounding agent loop. The Agents SDK runs the loop in your application and is now feature complete rather than the forward path for major new agent features.",{},{"id":266,"data":267,"type":42,"tunes":269},"h-short",{"text":268,"level":219},"The short comparison",{},{"id":271,"data":272,"type":304,"tunes":305},"short-table",{"content":273,"stretched":43,"withHeadings":14},[274,280,286,292,298],[275,276,277,278,279],"Option","Best fit in 2026","Who owns the agent loop?","Session \u002F context responsibility","Strategic status",[281,282,283,284,285],"Agents API","New OpenAI-native durable agents","OpenAI-managed Codex harness","OpenAI manages sessions, orchestration, compaction and recovery","Recommended starting point for new agent apps; public beta",[287,288,289,290,291],"Responses API","Direct model integrations and custom agent runtimes","Your application","You choose response chaining, Conversations, storage and loop logic","Core API primitive; recommended over Chat Completions for new projects",[293,294,295,296,297],"Agents SDK","Existing SDK applications or temporary capability gaps","Your application via the SDK runner","Your application operates deployment, storage and runtime behaviour","Feature complete; maintenance and compatibility continue, major new features not planned",[299,300,301,302,303],"Codex SDK","Codex harness in infrastructure you operate","Codex harness in your environment","You operate harness hosting and lifecycle","Separate option when you want the harness without the hosted Agents API runtime","table",{},{"id":307,"data":308,"type":42,"tunes":310},"h-agents-api",{"text":309,"level":219},"1. Agents API: managed harness, durable cloud agent",{},{"id":312,"data":313,"type":226,"tunes":315},"p-api-1",{"text":314},"The Agents API exposes the Codex harness through an OpenAI-managed service. OpenAI manages sessions, orchestration, context compaction, and recovery. Your application still provides tools and chooses the execution environment.",{},{"id":317,"data":318,"type":226,"tunes":320},"p-api-2",{"text":319},"That last distinction matters. “Managed agent” does not necessarily mean “all compute runs inside OpenAI.” The Agents API architecture supports no environment, an OpenAI-hosted environment, or a self-hosted environment connected to the hosted harness. With a self-hosted environment, your application owns provisioning, reconnection, shutdown, and persistent files while the harness remains managed.",{},{"id":322,"data":323,"type":226,"tunes":325},"p-api-3",{"text":324},"The Agents API is therefore a runtime service, not merely a request format. Sessions can persist, stream progress, receive additional tasks, use tools, work with files, and recover across long-running work.",{},{"id":327,"data":328,"type":42,"tunes":330},"h-api-gain",{"text":329,"level":218},"What you gain with the Agents API",{},{"id":332,"data":333,"type":343,"tunes":344},"api-gains",{"meta":334,"items":335,"style":342},{},[336,337,338,339,340,341],"A managed Codex harness instead of building and operating the main agent loop yourself.","Durable sessions for work that spans turns and long-running tasks.","Managed orchestration, context compaction, and recovery.","OpenAI-hosted or self-hosted execution environments, depending on workload requirements.","Streaming and webhooks for progress and lifecycle events.","A platform direction that OpenAI explicitly recommends for new agent applications.","unordered","list",{},{"id":346,"data":347,"type":42,"tunes":349},"h-api-own",{"text":348,"level":218},"What you still own",{},{"id":351,"data":352,"type":343,"tunes":360},"api-own",{"meta":353,"items":354,"style":342},{},[355,356,357,358,359],"Your product and application server.","Function-tool implementations and business logic.","Authorization and policy decisions around your own systems.","The execution environment lifecycle when you choose self-hosted compute.","Evaluation, acceptance criteria, domain-specific guardrails, and the decision of what the agent is allowed to do.",{},{"id":362,"data":363,"type":42,"tunes":365},"h-responses",{"text":364,"level":219},"2. Responses API: own the loop, use the platform primitives",{},{"id":367,"data":368,"type":226,"tunes":370},"p-resp-1",{"text":369},"The Responses API is the lower-level choice when you want OpenAI model and tool capabilities without delegating the overall agent runtime. OpenAI describes Responses as the recommended API primitive for new projects and as an evolution of Chat Completions with built-in tools, multi-turn state options, multimodal input, and agentic tool use.",{},{"id":372,"data":373,"type":226,"tunes":375},"p-resp-2",{"text":374},"A Responses request can itself invoke tools, but your application remains responsible for the larger workflow when you build an agent around it. That means your code decides how to persist application state, when to continue, how to recover, how to coordinate specialists, how to compact long histories, and how to represent resumable work.",{},{"id":377,"data":378,"type":226,"tunes":380},"p-resp-3",{"text":379},"This is not inherently inferior. It is the right boundary when agent behaviour must be deeply embedded in existing application logic, when you need a custom state model, or when a managed harness would hide control you actually need.",{},{"id":382,"data":383,"type":42,"tunes":385},"h-sdk",{"text":384,"level":219},"3. Agents SDK: supported, but no longer the default forward path",{},{"id":387,"data":388,"type":226,"tunes":390},"p-sdk-1",{"text":389},"The Agents SDK remains an open-source framework for running agent workflows in your application. It provides agent definitions, tools, handoffs, guardrails, tracing, sessions, and the runner loop in TypeScript and Python.",{},{"id":392,"data":393,"type":226,"tunes":395},"p-sdk-2",{"text":394},"But its strategic status changed. OpenAI now labels the Agents SDK feature complete: maintenance, security fixes, critical bug fixes, and compatibility work continue, but major new features are not planned. OpenAI recommends the Agents API for new applications.",{},{"id":397,"data":398,"type":226,"tunes":400},"p-sdk-3",{"text":399},"That does not mean an existing SDK application should be rewritten immediately. It means the architecture should stop assuming that the SDK is where the next major agent-runtime capabilities will land.",{},{"id":402,"data":403,"type":234,"tunes":406},"sdk-warning",{"body":404,"title":405,"variant":241},"OpenAI has not described the Agents SDK as unsupported. Existing applications can continue to use it, and maintenance, security, critical bug fixes, and compatibility work continue. The important change is that major new features are not planned and new applications are directed to the Agents API.","Do not translate “feature complete” into “deprecated”",{},{"id":408,"data":409,"type":42,"tunes":411},"h-codex-sdk",{"text":410,"level":219},"Where the Codex SDK fits",{},{"id":413,"data":414,"type":226,"tunes":416},"p-codex-1",{"text":415},"The current choice is not a simple three-way fork. OpenAI's runtime overview includes the Codex SDK as the option for running the Codex harness in infrastructure you operate. That is architecturally different from both the hosted Agents API and the Agents SDK.",{},{"id":418,"data":419,"type":226,"tunes":421},"p-codex-2",{"text":420},"If your real requirement is “I want the Codex harness, but I need to operate it myself,” the Codex SDK is the surface to evaluate. If your requirement is “I want to own the loop around model calls,” evaluate Responses. If your requirement is “I already have a working Agents SDK application,” the existing SDK can remain valid while you plan against its maintenance status.",{},{"id":423,"data":424,"type":42,"tunes":426},"h-test",{"text":425,"level":219},"The Runtime Ownership Test",{},{"id":428,"data":429,"type":226,"tunes":431},"p-test-intro",{"text":430},"A useful architecture decision starts by deciding what your team must own. Score each requirement as either must control, prefer to control, or prefer managed.",{},{"id":433,"data":434,"type":476,"tunes":477},"ownership-test",{"rows":435,"title":465,"layout":304,"columns":466},[436,441,445,449,453,457,461],{"id":437,"label":438,"values":439},"loop","Agent loop",[440,440,440],"",{"id":442,"label":443,"values":444},"session","Durable sessions",[440,440,440],{"id":446,"label":447,"values":448},"harness","Harness runtime",[440,440,440],{"id":450,"label":451,"values":452},"environment","Execution environment",[440,440,440],{"id":454,"label":455,"values":456},"orchestration","Orchestration semantics",[440,440,440],{"id":458,"label":459,"values":460},"portability","Provider \u002F transport flexibility",[440,440,440],{"id":462,"label":463,"values":464},"ops","Operational burden",[440,440,440],"Runtime Ownership Test",[467,470,473],{"id":468,"label":469},"decision","Decision",{"id":471,"label":472},"managed","If you prefer managed",{"id":474,"label":475},"control","If you require control","comparison",{},{"id":479,"data":480,"type":42,"tunes":482},"h-tree",{"text":481,"level":219},"A decision tree for new systems",{},{"id":484,"data":485,"type":510,"tunes":511},"decision-flow",{"steps":486,"title":508,"orientation":509},[487,490,493,496,499,502,505],{"label":488,"description":489},"1. Is this a new agent application?","If no, do not migrate solely because a newer surface exists. Evaluate the current application's actual constraints first.",{"label":491,"description":492},"2. Do you want a managed long-running agent harness?","If yes, start with the Agents API as OpenAI's recommended path for new agent applications.",{"label":494,"description":495},"3. Do you need the Codex harness but must operate it yourself?","Evaluate the Codex SDK rather than rebuilding harness behaviour on top of the Agents SDK.",{"label":497,"description":498},"4. Do you need to own the agent loop and state model?","Use the Responses API as the lower-level platform primitive and build the loop around it.",{"label":500,"description":501},"5. Are you already on the Agents SDK?","Continue if it meets requirements; major new features are not planned, so treat future platform adoption as an explicit roadmap decision.",{"label":503,"description":504},"6. Is a required capability missing from the Agents API?","OpenAI explicitly allows the Agents SDK as a short-term option for new applications that need unsupported capabilities.",{"label":506,"description":507},"7. Validate with a production-shaped spike","Test tools, environment, approvals, latency, observability, failure recovery, and lifecycle before locking the architecture.","Choose the runtime by the control boundary","auto","processFlow",{},{"id":513,"data":514,"type":42,"tunes":516},"h-not-drive",{"text":515,"level":219},"What should not drive the decision",{},{"id":518,"data":519,"type":304,"tunes":545},"weak-rules",{"content":520,"stretched":43,"withHeadings":14},[521,525,529,533,537,541],[522,523,524],"Weak decision rule","Why it fails","Better question",[526,527,528],"“The newest API must be best.”","Newer can be strategically preferred while still lacking a capability you need.","Which runtime responsibilities should be managed versus application-owned?",[530,531,532],"“We already know the SDK.”","Team familiarity can preserve an architecture whose roadmap has changed.","What is the cost of staying versus moving over the next product cycle?",[534,535,536],"“Managed means no infrastructure.”","Agents API can still use self-hosted environments and your application still owns product logic.","Which infrastructure layer is actually being delegated?",[538,539,540],"“Responses is only for simple calls.”","Responses provides built-in tools and stateful primitives; it can be the foundation of custom agent loops.","Do we need the platform to own the harness, or only model\u002Ftool primitives?",[542,543,544],"“Feature complete means we must migrate now.”","The SDK remains maintained for existing applications.","What concrete future requirement is blocked by staying?",{},{"id":547,"data":548,"type":42,"tunes":550},"h-migration",{"text":549,"level":219},"Migration is an architectural change, not an import rename",{},{"id":552,"data":553,"type":226,"tunes":555},"p-migration-1",{"text":554},"Moving from the Agents SDK to the Agents API changes ownership. In the SDK, the loop runs in your application. In the Agents API, OpenAI runs the harness and session while your application integrates through tasks, events, tools, and environment boundaries.",{},{"id":557,"data":558,"type":226,"tunes":560},"p-migration-2",{"text":559},"A real migration plan therefore needs to map session state, custom orchestration, handoffs, tool execution, approvals, storage, tracing, retries, failure recovery, environment lifecycle, and any provider-specific abstractions. Code volume may fall while operational assumptions change.",{},{"id":562,"data":563,"type":42,"tunes":565},"h-migration-inventory",{"text":564,"level":218},"The migration inventory",{},{"id":567,"data":568,"type":343,"tunes":581},"migration-list",{"meta":569,"items":570,"style":342},{},[571,572,573,574,575,576,577,578,579,580],"Agent definitions and instruction ownership.","Tool definitions and where each tool executes.","Handoffs, manager\u002Fspecialist patterns, and subagent behaviour.","Session identifiers, conversation state, resumability, and history retention.","Human approvals and interruption semantics.","Custom context trimming or compaction logic.","Tracing, evals, observability, and production debugging.","Self-hosted files, containers, private-network access, or other execution dependencies.","Provider abstraction or non-OpenAI model dependencies.","Retry, timeout, idempotency, recovery, and lifecycle assumptions.",{},{"id":583,"data":584,"type":42,"tunes":586},"h-beta",{"text":585,"level":219},"Public beta changes the risk model",{},{"id":588,"data":589,"type":226,"tunes":591},"p-beta-1",{"text":590},"The Agents API is the recommended direction for new agent applications, but it is also in public beta. Those facts are not contradictory. Strategic direction answers “where is the platform going?” Beta status answers “how much interface and operational change should I budget for?”",{},{"id":593,"data":594,"type":226,"tunes":596},"p-beta-2",{"text":595},"For production systems, isolate the integration behind an application boundary. Keep domain state, permissions, audit data, and business rules outside vendor-specific session objects where possible. This makes it easier to absorb API evolution without turning the agent runtime into the source of truth for your entire product.",{},{"id":598,"data":599,"type":42,"tunes":601},"h-default",{"text":600,"level":219},"A practical default architecture",{},{"id":603,"data":604,"type":226,"tunes":606},"p-default-1",{"text":605},"For many new OpenAI-native applications, a reasonable 2026 default is: Agents API for the managed harness and durable session, application-owned domain services and authorization, explicit function tools for business actions, and either OpenAI-hosted or self-hosted execution depending on data and compute requirements.",{},{"id":608,"data":609,"type":226,"tunes":611},"p-default-2",{"text":610},"That keeps the agent runtime powerful without making it the owner of business truth. The application still decides what a user may do, which data is authoritative, which actions require approval, and how results are validated.",{},{"id":613,"data":614,"type":619,"tunes":620},"ref-reliability",{"url":615,"title":616,"excerpt":617,"ctaLabel":618},"https:\u002F\u002Fstajic.de\u002Fblog\u002Fai-agent-reliability-why-the-final-answer-is-not-enough","AI Agent Reliability: Why the Final Answer Is Not Enough","A managed harness reduces operational burden, but reliability still requires traceable execution, explicit acceptance criteria and evaluation beyond the final answer.","Read the reliability article","referralArticle",{},{"id":622,"data":623,"type":42,"tunes":625},"h-change",{"text":624,"level":219},"What would change this answer?",{},{"id":627,"data":628,"type":226,"tunes":630},"p-change-1",{"text":629},"The recommendation changes if the Agents API adds or removes capabilities, exits beta with different contracts, changes environment or pricing boundaries, or introduces migration tooling that reduces ownership differences. It also changes if your application depends on provider portability, custom orchestration semantics, local-only execution, or a capability the hosted harness cannot support.",{},{"id":632,"data":633,"type":226,"tunes":635},"p-change-2",{"text":634},"For an existing Agents SDK application, the answer also changes with migration cost. If the system is stable, well evaluated, and not blocked by the SDK's feature-complete status, immediate migration may create more risk than value. If the product roadmap depends on capabilities landing only in the Agents API, delaying migration can create a different kind of debt.",{},{"id":637,"data":638,"type":42,"tunes":640},"h-limitations",{"text":639,"level":219},"Limitations",{},{"id":642,"data":643,"type":226,"tunes":645},"p-limit-1",{"text":644},"This comparison focuses on runtime ownership and OpenAI's stated platform direction. It does not benchmark latency, quality, or total cost for a specific workload. Those properties depend on model choice, tool usage, environment, task length, caching, sandbox usage, and application architecture.",{},{"id":647,"data":648,"type":226,"tunes":650},"p-limit-2",{"text":649},"The Agents API is also new enough that production experience is still accumulating. A design should therefore be validated with representative workloads rather than chosen solely from product positioning.",{},{"id":652,"data":653,"type":42,"tunes":655},"h-conclusion",{"text":654,"level":219},"Conclusion",{},{"id":657,"data":658,"type":226,"tunes":660},"p-conclusion-1",{"text":659},"The 2026 OpenAI agent decision is fundamentally about runtime ownership. Agents API means OpenAI owns more of the harness and durable-session machinery. Responses means your application owns the loop around platform primitives. The Agents SDK remains valid for existing systems but is no longer the default destination for major new agent-runtime features.",{},{"id":662,"data":663,"type":226,"tunes":665},"p-conclusion-2",{"text":664},"For a new application, follow the platform direction unless a real requirement pushes you lower in the stack. Start with the Agents API, move to Responses when you need to own the loop, evaluate Codex SDK when you need the harness in your infrastructure, and keep the Agents SDK where existing investments or temporary capability gaps justify it.",{},{"id":667,"data":668,"type":42,"tunes":670},"h-faq",{"text":669,"level":219},"FAQ",{},{"id":672,"data":673,"type":672,"tunes":700},"faq",{"items":674,"title":699},[675,679,683,687,691,695],{"id":676,"answer":677,"question":678},"faq1","OpenAI currently recommends the Agents API for new agent applications. The Agents SDK is feature complete and remains supported for existing applications, with maintenance, security, critical bug fixes and compatibility work continuing.","Should I use the OpenAI Agents API or Agents SDK for a new project?",{"id":680,"answer":681,"question":682},"faq2","OpenAI describes it as feature complete, not as unsupported. Major new features are not planned, but maintenance, security fixes, critical bug fixes and compatibility work continue.","Is the Agents SDK deprecated?",{"id":684,"answer":685,"question":686},"faq3","Use Responses when your application should own the agent loop, state strategy, orchestration and continuation logic while still using OpenAI models and platform tools.","When should I use the Responses API instead of the Agents API?",{"id":688,"answer":689,"question":690},"faq4","No. The Agents API can use no execution environment, an OpenAI-hosted environment, or a self-hosted environment connected to the managed harness.","Does the Agents API require OpenAI-hosted compute?",{"id":692,"answer":693,"question":694},"faq5","OpenAI positions the Codex SDK for running the Codex harness in infrastructure you operate. It is the relevant option when you want the harness but not the hosted Agents API runtime.","Where does the Codex SDK fit?",{"id":696,"answer":697,"question":698},"faq6","Not automatically. Evaluate whether the current system is blocked by the SDK's feature-complete status, whether required capabilities exist in the Agents API, and whether the migration benefit exceeds the operational and architectural change.","Should an existing Agents SDK app migrate immediately?","OpenAI agent runtime choices in 2026",{},{"id":702,"data":703,"type":42,"tunes":705},"h-glossary",{"text":704,"level":219},"Glossary",{},{"id":707,"data":708,"type":707,"tunes":730},"glossary",{"title":709,"entries":710},"Key runtime terms",[711,714,717,720,723,726],{"term":712,"anchor":446,"definition":713},"Harness","The runtime loop and supporting machinery that coordinates model calls, tools, context, sessions and agent execution.",{"term":281,"anchor":715,"definition":716},"agents-api","OpenAI's managed API for durable cloud agents using a hosted Codex harness.",{"term":287,"anchor":718,"definition":719},"responses-api","OpenAI's lower-level API primitive for model responses, hosted tools and stateful interactions around which applications can build their own agent loop.",{"term":293,"anchor":721,"definition":722},"agents-sdk","OpenAI's open-source framework for running agent workflows in application code; feature complete as of September 2026.",{"term":299,"anchor":724,"definition":725},"codex-sdk","The runtime option OpenAI lists for running the Codex harness in infrastructure you operate.",{"term":727,"anchor":728,"definition":729},"Runtime ownership","runtime-ownership","The architectural boundary describing which parts of the agent loop, session state, execution environment and lifecycle are operated by the platform versus the application.",{},{"id":732,"data":733,"type":42,"tunes":735},"h-sources",{"text":734,"level":219},"Primary sources and further reading",{},{"id":737,"data":738,"type":744,"tunes":745},"src-launch",{"link":739,"meta":740},"https:\u002F\u002Fopenai.com\u002Findex\u002Fintroducing-the-agents-api\u002F",{"image":741,"title":742,"description":743},{"url":440},"OpenAI — Introducing the Agents API","Launch announcement for the Agents API on 10 September 2026, describing the managed Codex harness and public beta.","linkTool",{},{"id":747,"data":748,"type":744,"tunes":754},"src-agents-overview",{"link":749,"meta":750},"https:\u002F\u002Fdevelopers.openai.com\u002Fapi\u002Fdocs\u002Fguides\u002Fagents",{"image":751,"title":752,"description":753},{"url":440},"OpenAI — Agents runtime overview","Current comparison of Agents API, Codex SDK and Responses API, including the support status of the Agents SDK.",{},{"id":756,"data":757,"type":744,"tunes":763},"src-agents-api",{"link":758,"meta":759},"https:\u002F\u002Fdevelopers.openai.com\u002Fapi\u002Fdocs\u002Fguides\u002Fagents-api\u002Foverview",{"image":760,"title":761,"description":762},{"url":440},"OpenAI — Agents API overview","Documentation for durable cloud agents, sessions, orchestration, context compaction, recovery and environment choices.",{},{"id":765,"data":766,"type":744,"tunes":772},"src-architecture",{"link":767,"meta":768},"https:\u002F\u002Fdevelopers.openai.com\u002Fapi\u002Fdocs\u002Fguides\u002Fagents-api\u002Farchitecture",{"image":769,"title":770,"description":771},{"url":440},"OpenAI — Agents API architecture","Architecture boundary between the hosted harness, application server and no\u002Fopenai-hosted\u002Fself-hosted execution environments.",{},{"id":774,"data":775,"type":744,"tunes":781},"src-sdk",{"link":776,"meta":777},"https:\u002F\u002Fdevelopers.openai.com\u002Fapi\u002Fdocs\u002Fguides\u002Fagents\u002Fsdk",{"image":778,"title":779,"description":780},{"url":440},"OpenAI — Agents SDK","Current Agents SDK support notice and explanation of the application-owned agent loop.",{},{"id":783,"data":784,"type":744,"tunes":790},"src-responses",{"link":785,"meta":786},"https:\u002F\u002Fdevelopers.openai.com\u002Fapi\u002Fdocs\u002Fguides\u002Fmigrate-to-responses",{"image":787,"title":788,"description":789},{"url":440},"OpenAI — Migrate to the Responses API","Current Responses API positioning, built-in tools, stateful context and agentic primitives.",{},{"id":792,"data":793,"type":220,"tunes":794},"toc",{"title":217,"maxLevel":218,"minLevel":219},{},"2.31.6","OpenAI’s agent stack changed in September 2026. This architecture guide separates the Agents API, Agents SDK, Responses API, and Codex SDK by runtime ownership—so teams can choose the right control boundary instead of comparing product names.","\u002Fuploads\u002F2026\u002F09\u002Fopenai-agents-api-vs-agents-sdk-vs-responses-api-what-should-you-build-on-in-2026-1790351846714-zi7lus.webp","openai-agents-api-vs-agents-sdk-vs-responses-api-what-should-you-build-on-in-2026-1790351846714-zi7lus","PUBLISHED","2026-09-25T11:56:00.000Z","2026-09-25T15:56:16.274Z","2026-09-25T19:58:41.459Z",{"en":804,"de":805,"sr":806,"es":807,"fr":808,"it":809,"ru":810,"zh":811},"\u002Fblog\u002Fopenai-agents-api-vs-agents-sdk-vs-responses-api-what-should-you-build-on-in-2026","\u002Fde\u002Fblog\u002Fopenai-agents-api-vs-agents-sdk-vs-responses-api-what-should-you-build-on-in-2026","\u002Fsr\u002Fblog\u002Fopenai-agents-api-vs-agents-sdk-vs-responses-api-what-should-you-build-on-in-2026","\u002Fes\u002Fblog\u002Fopenai-agents-api-vs-agents-sdk-vs-responses-api-what-should-you-build-on-in-2026","\u002Ffr\u002Fblog\u002Fopenai-agents-api-vs-agents-sdk-vs-responses-api-what-should-you-build-on-in-2026","\u002Fit\u002Fblog\u002Fopenai-agents-api-vs-agents-sdk-vs-responses-api-what-should-you-build-on-in-2026","\u002Fru\u002Fblog\u002Fopenai-agents-api-vs-agents-sdk-vs-responses-api-what-should-you-build-on-in-2026","\u002Fzh\u002Fblog\u002Fopenai-agents-api-vs-agents-sdk-vs-responses-api-what-should-you-build-on-in-2026",[813,816,820],{"id":101,"name":814,"slug":815},"Overview","overview-digital-platform",{"id":817,"name":818,"slug":819},48,"Capabilities","capabilities",{"id":821,"name":814,"slug":822},46,"overview",{"id":824,"login":825,"email":826,"displayName":827},"20","rooth8233","aleksandar@stajic.de","Aleksandar Stajić",[829],{"lang":7,"title":208,"content":210,"contentJson":830,"excerpt":796},{"time":212,"blocks":831,"version":795},[832,835,838,841,844,847,850,853,856,859,868,871,874,877,880,883,888,891,896,899,902,905,908,911,914,917,920,923,926,929,932,935,938,960,963,974,977,987,990,993,996,999,1004,1007,1010,1013,1016,1019,1022,1025,1028,1031,1034,1037,1040,1043,1046,1049,1052,1055,1065,1068,1078,1081,1086,1091,1096,1101,1106,1111],{"id":215,"data":833,"type":220,"tunes":834},{"title":217,"maxLevel":218,"minLevel":219},{},{"id":223,"data":836,"type":226,"tunes":837},{"text":225},{},{"id":229,"data":839,"type":234,"tunes":840},{"body":231,"title":232,"variant":233},{},{"id":237,"data":842,"type":234,"tunes":843},{"body":239,"title":240,"variant":241},{},{"id":244,"data":845,"type":234,"tunes":846},{"body":246,"title":247,"variant":248},{},{"id":251,"data":848,"type":42,"tunes":849},{"text":253,"level":219},{},{"id":256,"data":851,"type":226,"tunes":852},{"text":258},{},{"id":261,"data":854,"type":226,"tunes":855},{"text":263},{},{"id":266,"data":857,"type":42,"tunes":858},{"text":268,"level":219},{},{"id":271,"data":860,"type":304,"tunes":867},{"content":861,"stretched":43,"withHeadings":14},[862,863,864,865,866],[275,276,277,278,279],[281,282,283,284,285],[287,288,289,290,291],[293,294,295,296,297],[299,300,301,302,303],{},{"id":307,"data":869,"type":42,"tunes":870},{"text":309,"level":219},{},{"id":312,"data":872,"type":226,"tunes":873},{"text":314},{},{"id":317,"data":875,"type":226,"tunes":876},{"text":319},{},{"id":322,"data":878,"type":226,"tunes":879},{"text":324},{},{"id":327,"data":881,"type":42,"tunes":882},{"text":329,"level":218},{},{"id":332,"data":884,"type":343,"tunes":887},{"meta":885,"items":886,"style":342},{},[336,337,338,339,340,341],{},{"id":346,"data":889,"type":42,"tunes":890},{"text":348,"level":218},{},{"id":351,"data":892,"type":343,"tunes":895},{"meta":893,"items":894,"style":342},{},[355,356,357,358,359],{},{"id":362,"data":897,"type":42,"tunes":898},{"text":364,"level":219},{},{"id":367,"data":900,"type":226,"tunes":901},{"text":369},{},{"id":372,"data":903,"type":226,"tunes":904},{"text":374},{},{"id":377,"data":906,"type":226,"tunes":907},{"text":379},{},{"id":382,"data":909,"type":42,"tunes":910},{"text":384,"level":219},{},{"id":387,"data":912,"type":226,"tunes":913},{"text":389},{},{"id":392,"data":915,"type":226,"tunes":916},{"text":394},{},{"id":397,"data":918,"type":226,"tunes":919},{"text":399},{},{"id":402,"data":921,"type":234,"tunes":922},{"body":404,"title":405,"variant":241},{},{"id":408,"data":924,"type":42,"tunes":925},{"text":410,"level":219},{},{"id":413,"data":927,"type":226,"tunes":928},{"text":415},{},{"id":418,"data":930,"type":226,"tunes":931},{"text":420},{},{"id":423,"data":933,"type":42,"tunes":934},{"text":425,"level":219},{},{"id":428,"data":936,"type":226,"tunes":937},{"text":430},{},{"id":433,"data":939,"type":476,"tunes":959},{"rows":940,"title":465,"layout":304,"columns":955},[941,943,945,947,949,951,953],{"id":437,"label":438,"values":942},[440,440,440],{"id":442,"label":443,"values":944},[440,440,440],{"id":446,"label":447,"values":946},[440,440,440],{"id":450,"label":451,"values":948},[440,440,440],{"id":454,"label":455,"values":950},[440,440,440],{"id":458,"label":459,"values":952},[440,440,440],{"id":462,"label":463,"values":954},[440,440,440],[956,957,958],{"id":468,"label":469},{"id":471,"label":472},{"id":474,"label":475},{},{"id":479,"data":961,"type":42,"tunes":962},{"text":481,"level":219},{},{"id":484,"data":964,"type":510,"tunes":973},{"steps":965,"title":508,"orientation":509},[966,967,968,969,970,971,972],{"label":488,"description":489},{"label":491,"description":492},{"label":494,"description":495},{"label":497,"description":498},{"label":500,"description":501},{"label":503,"description":504},{"label":506,"description":507},{},{"id":513,"data":975,"type":42,"tunes":976},{"text":515,"level":219},{},{"id":518,"data":978,"type":304,"tunes":986},{"content":979,"stretched":43,"withHeadings":14},[980,981,982,983,984,985],[522,523,524],[526,527,528],[530,531,532],[534,535,536],[538,539,540],[542,543,544],{},{"id":547,"data":988,"type":42,"tunes":989},{"text":549,"level":219},{},{"id":552,"data":991,"type":226,"tunes":992},{"text":554},{},{"id":557,"data":994,"type":226,"tunes":995},{"text":559},{},{"id":562,"data":997,"type":42,"tunes":998},{"text":564,"level":218},{},{"id":567,"data":1000,"type":343,"tunes":1003},{"meta":1001,"items":1002,"style":342},{},[571,572,573,574,575,576,577,578,579,580],{},{"id":583,"data":1005,"type":42,"tunes":1006},{"text":585,"level":219},{},{"id":588,"data":1008,"type":226,"tunes":1009},{"text":590},{},{"id":593,"data":1011,"type":226,"tunes":1012},{"text":595},{},{"id":598,"data":1014,"type":42,"tunes":1015},{"text":600,"level":219},{},{"id":603,"data":1017,"type":226,"tunes":1018},{"text":605},{},{"id":608,"data":1020,"type":226,"tunes":1021},{"text":610},{},{"id":613,"data":1023,"type":619,"tunes":1024},{"url":615,"title":616,"excerpt":617,"ctaLabel":618},{},{"id":622,"data":1026,"type":42,"tunes":1027},{"text":624,"level":219},{},{"id":627,"data":1029,"type":226,"tunes":1030},{"text":629},{},{"id":632,"data":1032,"type":226,"tunes":1033},{"text":634},{},{"id":637,"data":1035,"type":42,"tunes":1036},{"text":639,"level":219},{},{"id":642,"data":1038,"type":226,"tunes":1039},{"text":644},{},{"id":647,"data":1041,"type":226,"tunes":1042},{"text":649},{},{"id":652,"data":1044,"type":42,"tunes":1045},{"text":654,"level":219},{},{"id":657,"data":1047,"type":226,"tunes":1048},{"text":659},{},{"id":662,"data":1050,"type":226,"tunes":1051},{"text":664},{},{"id":667,"data":1053,"type":42,"tunes":1054},{"text":669,"level":219},{},{"id":672,"data":1056,"type":672,"tunes":1064},{"items":1057,"title":699},[1058,1059,1060,1061,1062,1063],{"id":676,"answer":677,"question":678},{"id":680,"answer":681,"question":682},{"id":684,"answer":685,"question":686},{"id":688,"answer":689,"question":690},{"id":692,"answer":693,"question":694},{"id":696,"answer":697,"question":698},{},{"id":702,"data":1066,"type":42,"tunes":1067},{"text":704,"level":219},{},{"id":707,"data":1069,"type":707,"tunes":1077},{"title":709,"entries":1070},[1071,1072,1073,1074,1075,1076],{"term":712,"anchor":446,"definition":713},{"term":281,"anchor":715,"definition":716},{"term":287,"anchor":718,"definition":719},{"term":293,"anchor":721,"definition":722},{"term":299,"anchor":724,"definition":725},{"term":727,"anchor":728,"definition":729},{},{"id":732,"data":1079,"type":42,"tunes":1080},{"text":734,"level":219},{},{"id":737,"data":1082,"type":744,"tunes":1085},{"link":739,"meta":1083},{"image":1084,"title":742,"description":743},{"url":440},{},{"id":747,"data":1087,"type":744,"tunes":1090},{"link":749,"meta":1088},{"image":1089,"title":752,"description":753},{"url":440},{},{"id":756,"data":1092,"type":744,"tunes":1095},{"link":758,"meta":1093},{"image":1094,"title":761,"description":762},{"url":440},{},{"id":765,"data":1097,"type":744,"tunes":1100},{"link":767,"meta":1098},{"image":1099,"title":770,"description":771},{"url":440},{},{"id":774,"data":1102,"type":744,"tunes":1105},{"link":776,"meta":1103},{"image":1104,"title":779,"description":780},{"url":440},{},{"id":783,"data":1107,"type":744,"tunes":1110},{"link":785,"meta":1108},{"image":1109,"title":788,"description":789},{"url":440},{},{"id":792,"data":1112,"type":220,"tunes":1113},{"title":217,"maxLevel":218,"minLevel":219},{},"Post erfolgreich abgerufen",{"items":1116,"source":1145,"manualIds":1146,"manualMatchedIds":1147},[1117,1124,1131,1138],{"id":1118,"slug":1119,"title":1120,"excerpt":1121,"featuredImage":1122,"publishedAt":1123},"382","a-practical-monorepo-architecture-next-js-platform-admin-fastify-api-prisma-and-nginx","A Practical Monorepo Architecture with Next.js, Fastify, Prisma, and NGINX","Explore a practical monorepo architecture using Next.js, Fastify, Prisma, and NGINX, highlighting real-world integration and workflow.","\u002Fuploads\u002F2026\u002F01\u002Fa-practical-monorepo-architecture-next-js-platform-admin-fastify-api-prisma-and-nginx-1769885526116-q1100n.webp","2026-01-31T08:18:00.000Z",{"id":1125,"slug":1126,"title":1127,"excerpt":1128,"featuredImage":1129,"publishedAt":1130},"476","mcp-vs-a2a-vs-ucp-vs-ap2-vs-a2ui-the-agent-protocol-stack-explained","MCP vs A2A vs UCP vs AP2 vs A2UI: The Agent Protocol Stack Explained","MCP, A2A, UCP, AP2 and A2UI are often presented as competing agent standards. They mostly solve different interoperability problems. This guide maps each protocol to the boundary it actually standardizes—and shows how they can work together in one production system.","\u002Fuploads\u002F2026\u002F09\u002Fmcp-vs-a2a-vs-ucp-vs-ap2-vs-a2ui-the-agent-protocol-stack-explained-1790352625869-2ezle0.webp","2026-09-25T12:09:00.000Z",{"id":1132,"slug":1133,"title":1134,"excerpt":1135,"featuredImage":1136,"publishedAt":1137},"478","what-is-rag-the-simplest-explanation-of-how-it-works","What Is RAG? The Simplest Explanation of How It Works","RAG sounds complicated, but the idea is simple: before an AI answers, it first looks up useful information from a knowledge source and gives that information to the language model. This guide explains RAG, LLMs, state, memory and tools using one simple mental model.","\u002Fuploads\u002F2026\u002F09\u002Fwhat-is-rag-the-simplest-explanation-of-how-it-works-1790377492124-khjagt.webp","2026-09-25T19:03:00.000Z",{"id":1139,"slug":1140,"title":1141,"excerpt":1142,"featuredImage":1143,"publishedAt":1144},"381","enterprise-grade-multi-tenant-architecture-for-an-international-platform","Enterprise-Grade Multi-Tenant Architecture for an International Platform","Loving Rocks is an enterprise-grade wedding platform designed with a true multi-tenant architecture, isolated databases per tenant, and built-in internationalization for global scalability, security, and long-term operational stability.","\u002Fuploads\u002F2026\u002F01\u002Fenterprise-grade-multi-tenant-architecture-for-an-international-platform-1769789121298-b6v7ak.webp","2026-01-30T12:04:00.000Z","fallback",[],[]]