[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"portal-settings:stajic:sr":3,"public-menus:all":38,"post:openai-agents-api-vs-agents-sdk-vs-responses-api-what-should-you-build-on-in-2026:sr":205,"related:post:openai-agents-api-vs-agents-sdk-vs-responses-api-what-should-you-build-on-in-2026:sr:1":1584},{"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","sr","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":1583},{"id":207,"title":208,"slug":209,"content":210,"contentJson":211,"excerpt":795,"featuredImage":796,"featuredImageAlt":797,"featuredImageCaption":10,"featuredImageTitle":10,"featuredImageCopyright":10,"featuredImageAuthor":10,"featuredImageSourceUrl":10,"featuredImageLicense":10,"featuredImageIsAiGenerated":43,"status":798,"publishedAt":799,"createdAt":800,"updatedAt":801,"seoLocalePaths":802,"categories":811,"author":823,"translations":828},"473","OpenAI Agents API vs Agents SDK vs Responses API: Na čemu bi trebalo da gradite u 2026?","openai-agents-api-vs-agents-sdk-vs-responses-api-what-should-you-build-on-in-2026","\u003Cnav class=\"editorjs-toc\" data-editorjs-toc=\"true\" aria-label=\"Sadržaj\">\u003Cstrong class=\"editorjs-toc__title\">Sadržaj\u003C\u002Fstrong>\u003Col class=\"editorjs-toc__list editorjs-toc__list--depth-0\">\u003Cli class=\"editorjs-toc__item\">\u003Ca href=\"#section-6\" class=\"editorjs-toc__link\">Arhitektura se promenila: izaberite granicu runtime-a, a ne biblioteku\u003C\u002Fa>\u003C\u002Fli>\u003Cli class=\"editorjs-toc__item\">\u003Ca href=\"#section-9\" class=\"editorjs-toc__link\">Kratko poređenje\u003C\u002Fa>\u003C\u002Fli>\u003Cli class=\"editorjs-toc__item\">\u003Ca href=\"#section-11\" class=\"editorjs-toc__link\">1. Agents API: upravljani harness, trajni cloud agent\u003C\u002Fa>\u003Col class=\"editorjs-toc__list editorjs-toc__list--depth-1\">\u003Cli class=\"editorjs-toc__item\">\u003Ca href=\"#section-15\" class=\"editorjs-toc__link\">Šta dobijate uz Agents API\u003C\u002Fa>\u003C\u002Fli>\u003Cli class=\"editorjs-toc__item\">\u003Ca href=\"#section-17\" class=\"editorjs-toc__link\">Šta i dalje ostaje pod vašom kontrolom\u003C\u002Fa>\u003C\u002Fli>\u003C\u002Fol>\u003C\u002Fli>\u003Cli class=\"editorjs-toc__item\">\u003Ca href=\"#section-19\" class=\"editorjs-toc__link\">2. Responses API: upravljajte petljom, koristite primitive platforme\u003C\u002Fa>\u003C\u002Fli>\u003Cli class=\"editorjs-toc__item\">\u003Ca href=\"#section-23\" class=\"editorjs-toc__link\">3. Agents SDK: podržan, ali više nije podrazumevani put za budući razvoj\u003C\u002Fa>\u003C\u002Fli>\u003Cli class=\"editorjs-toc__item\">\u003Ca href=\"#section-28\" class=\"editorjs-toc__link\">Gde se uklapa Codex SDK\u003C\u002Fa>\u003C\u002Fli>\u003Cli class=\"editorjs-toc__item\">\u003Ca href=\"#section-31\" class=\"editorjs-toc__link\">Test vlasništva nad radnim okruženjem\u003C\u002Fa>\u003C\u002Fli>\u003Cli class=\"editorjs-toc__item\">\u003Ca href=\"#section-34\" class=\"editorjs-toc__link\">Stablo odlučivanja za nove sisteme\u003C\u002Fa>\u003C\u002Fli>\u003Cli class=\"editorjs-toc__item\">\u003Ca href=\"#section-36\" class=\"editorjs-toc__link\">Šta ne bi trebalo da vodi donošenje odluke\u003C\u002Fa>\u003C\u002Fli>\u003Cli class=\"editorjs-toc__item\">\u003Ca href=\"#section-38\" class=\"editorjs-toc__link\">Migracija je arhitektonska promena, a ne preimenovanje uvoza\u003C\u002Fa>\u003Col class=\"editorjs-toc__list editorjs-toc__list--depth-1\">\u003Cli class=\"editorjs-toc__item\">\u003Ca href=\"#section-41\" class=\"editorjs-toc__link\">Popis elemenata za migraciju\u003C\u002Fa>\u003C\u002Fli>\u003C\u002Fol>\u003C\u002Fli>\u003Cli class=\"editorjs-toc__item\">\u003Ca href=\"#section-43\" class=\"editorjs-toc__link\">Javna beta menja model rizika\u003C\u002Fa>\u003C\u002Fli>\u003Cli class=\"editorjs-toc__item\">\u003Ca href=\"#section-46\" class=\"editorjs-toc__link\">Praktična podrazumevana arhitektura\u003C\u002Fa>\u003C\u002Fli>\u003Cli class=\"editorjs-toc__item\">\u003Ca href=\"#section-50\" class=\"editorjs-toc__link\">Šta bi promenilo ovaj odgovor?\u003C\u002Fa>\u003C\u002Fli>\u003Cli class=\"editorjs-toc__item\">\u003Ca href=\"#section-53\" class=\"editorjs-toc__link\">Ograničenja\u003C\u002Fa>\u003C\u002Fli>\u003Cli class=\"editorjs-toc__item\">\u003Ca href=\"#section-56\" class=\"editorjs-toc__link\">Zaključak\u003C\u002Fa>\u003C\u002Fli>\u003Cli class=\"editorjs-toc__item\">\u003Ca href=\"#section-59\" class=\"editorjs-toc__link\">Česta pitanja\u003C\u002Fa>\u003C\u002Fli>\u003Cli class=\"editorjs-toc__item\">\u003Ca href=\"#section-61\" class=\"editorjs-toc__link\">Rečnik pojmova\u003C\u002Fa>\u003C\u002Fli>\u003Cli class=\"editorjs-toc__item\">\u003Ca href=\"#section-63\" class=\"editorjs-toc__link\">Primarni izvori i dodatna literatura\u003C\u002Fa>\u003C\u002Fli>\u003C\u002Fol>\u003C\u002Fnav>\n\u003Cp>OpenAI-jev stek za agente značajno se promenio u septembru 2026. Novi Agents API uveo je upravljani Codex harness za trajne cloud agente, dok je stariji Agents SDK prešao u fazu održavanja sa zaokruženim funkcionalnostima. Responses API ostaje interfejs nižeg nivoa za aplikacije koje žele direktne pozive modela ili da same upravljaju petljom agenta. Ovo nisu tri međusobno zamenljiva omotača oko iste stvari: oni postavljaju granicu runtime-a na različita mesta.\u003C\u002Fp>\n\u003Caside class=\"editorjs-callout editorjs-callout--info my-6 rounded-xl border p-5 border-blue-300 bg-blue-50 dark:border-blue-900 dark:bg-blue-950\u002F20\" role=\"note\">\u003Cstrong class=\"block mb-2 text-gray-900 dark:text-gray-100\">Direktan odgovor\u003C\u002Fstrong>\u003Cdiv class=\"text-gray-700 dark:text-gray-200\"><strong>Za novu OpenAI-nativnu agentsku aplikaciju u septembru 2026, počnite sa Agents API-jem, osim ako nemate konkretan razlog da sami kontrolišete veći deo runtime-a.<\u002Fstrong> Koristite Responses API kada vaša aplikacija treba da poseduje petlju, strategiju stanja i orkestraciju. Zadržite Agents SDK za postojeće aplikacije ili kratkoročne nedostatke gde Agents API još uvek ne podržava potrebnu mogućnost. Ako želite sam Codex harness, ali morate da ga pokrećete na infrastrukturi kojom sami upravljate, procenite Codex SDK umesto da forsirate Agents SDK u toj ulozi.\u003C\u002Fdiv>\u003C\u002Faside>\n\u003Caside class=\"editorjs-callout editorjs-callout--warning my-6 rounded-xl border p-5 border-amber-300 bg-amber-50 dark:border-amber-900 dark:bg-amber-950\u002F20\" role=\"note\">\u003Cstrong class=\"block mb-2 text-gray-900 dark:text-gray-100\">Vremenski osetljiva arhitektonska odluka\u003C\u002Fstrong>\u003Cdiv class=\"text-gray-700 dark:text-gray-200\">Ovaj članak odražava stanje platforme OpenAI na dan <strong>25. septembra 2026<\u002Fstrong>. Agents API je lansiran u javnoj beta verziji 10. septembra 2026. Beta interfejsi, pokrivenost funkcijama, cene i uputstva za migraciju mogu se promeniti; proverite aktuelnu dokumentaciju pre nego što donesete konačne odluke o produkcionoj arhitekturi.\u003C\u002Fdiv>\u003C\u002Faside>\n\u003Caside class=\"editorjs-callout editorjs-callout--note my-6 rounded-xl border p-5 border-gray-300 bg-gray-50 dark:border-gray-700 dark:bg-gray-900\u002F40\" role=\"note\">\u003Cstrong class=\"block mb-2 text-gray-900 dark:text-gray-100\">Model odlučivanja koji se ovde koristi\u003C\u002Fstrong>\u003Cdiv class=\"text-gray-700 dark:text-gray-200\">Test vlasništva nad runtime-om u nastavku predstavlja praktičan arhitektonski model, a ne OpenAI taksonomiju proizvoda. On postavlja pitanje koje delove runtime-a agenta vaš tim mora da kontroliše, a kojim delovima želite da upravlja OpenAI.\u003C\u002Fdiv>\u003C\u002Faside>\n\u003Ch2 id=\"section-6\">Arhitektura se promenila: izaberite granicu runtime-a, a ne biblioteku\u003C\u002Fh2>\n\u003Cp>Važna odluka više nije jednostavno „Koji SDK treba da instaliram?” Reč je o tome ko kontroliše harness, petlju agenta, trajno stanje sesije, sažimanje konteksta, oporavak, izvršno okruženje i životni ciklus aplikacije.\u003C\u002Fp>\n\u003Cp>OpenAI-jev trenutni pregled za Agents jasno definiše ovu granicu. Agents API pokreće hostovani Codex harness i upravlja orkestracijom, kao i trajnim stanjem sesije. Responses API pruža odgovore modela i hostovane mogućnosti, dok vaša aplikacija upravlja okolnom petljom agenta. Agents SDK pokreće petlju u vašoj aplikaciji i sada je zaokružen po pitanju funkcionalnosti, te više ne predstavlja pravac za razvoj novih velikih mogućnosti za agente.\u003C\u002Fp>\n\u003Ch2 id=\"section-9\">Kratko poređenje\u003C\u002Fh2>\n\u003Cdiv class=\"overflow-x-auto\">\u003Ctable class=\"w-full border-collapse\">\u003Cthead>\u003Ctr>\u003Cth class=\"border border-gray-300 px-4 py-2 text-left font-semibold\">Opcija\u003C\u002Fth>\u003Cth class=\"border border-gray-300 px-4 py-2 text-left font-semibold\">Najbolji izbor u 2026.\u003C\u002Fth>\u003Cth class=\"border border-gray-300 px-4 py-2 text-left font-semibold\">Ko poseduje petlju agenta?\u003C\u002Fth>\u003Cth class=\"border border-gray-300 px-4 py-2 text-left font-semibold\">Odgovornost za sesiju \u002F kontekst\u003C\u002Fth>\u003Cth class=\"border border-gray-300 px-4 py-2 text-left font-semibold\">Strateški status\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\u003Ctbody>\u003Ctr>\u003Ctd class=\"border border-gray-300 px-4 py-2\">Agents API\u003C\u002Ftd>\u003Ctd class=\"border border-gray-300 px-4 py-2\">Novi OpenAI-nativni trajni agenti\u003C\u002Ftd>\u003Ctd class=\"border border-gray-300 px-4 py-2\">Codex harness kojim upravlja OpenAI\u003C\u002Ftd>\u003Ctd class=\"border border-gray-300 px-4 py-2\">OpenAI upravlja sesijama, orkestracijom, sažimanjem i oporavkom\u003C\u002Ftd>\u003Ctd class=\"border border-gray-300 px-4 py-2\">Preporučena polazna tačka za nove agentske aplikacije; javna beta\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd class=\"border border-gray-300 px-4 py-2\">Responses API\u003C\u002Ftd>\u003Ctd class=\"border border-gray-300 px-4 py-2\">Direktne integracije modela i prilagođeni runtime-ovi za agente\u003C\u002Ftd>\u003Ctd class=\"border border-gray-300 px-4 py-2\">Vaša aplikacija\u003C\u002Ftd>\u003Ctd class=\"border border-gray-300 px-4 py-2\">Sami birate ulančavanje odgovora, Conversations, skladište i logiku petlje\u003C\u002Ftd>\u003Ctd class=\"border border-gray-300 px-4 py-2\">Osnovni API primitiv; preporučuje se umesto Chat Completions za nove projekte\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd class=\"border border-gray-300 px-4 py-2\">Agents SDK\u003C\u002Ftd>\u003Ctd class=\"border border-gray-300 px-4 py-2\">Postojeće SDK aplikacije ili privremeni nedostaci u mogućnostima\u003C\u002Ftd>\u003Ctd class=\"border border-gray-300 px-4 py-2\">Vaša aplikacija putem SDK pokretača\u003C\u002Ftd>\u003Ctd class=\"border border-gray-300 px-4 py-2\">Vaša aplikacija upravlja raspoređivanjem, skladištem i ponašanjem runtime-a\u003C\u002Ftd>\u003Ctd class=\"border border-gray-300 px-4 py-2\">Zaokružen sa funkcijama; održavanje i kompatibilnost se nastavljaju, nove velike funkcije nisu planirane\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd class=\"border border-gray-300 px-4 py-2\">Codex SDK\u003C\u002Ftd>\u003Ctd class=\"border border-gray-300 px-4 py-2\">Codex harness u infrastrukturi kojom sami upravljate\u003C\u002Ftd>\u003Ctd class=\"border border-gray-300 px-4 py-2\">Codex harness u vašem okruženju\u003C\u002Ftd>\u003Ctd class=\"border border-gray-300 px-4 py-2\">Sami upravljate hostovanjem harness-a i životnim ciklusom\u003C\u002Ftd>\u003Ctd class=\"border border-gray-300 px-4 py-2\">Zasebna opcija kada želite harness bez hostovanog Agents API runtime-a\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Ch2 id=\"section-11\">1. Agents API: upravljani harness, trajni cloud agent\u003C\u002Fh2>\n\u003Cp>Agents API izlaže Codex harness kroz servis kojim upravlja OpenAI. OpenAI upravlja sesijama, orkestracijom, sažimanjem konteksta i oporavkom. Vaša aplikacija i dalje obezbeđuje alate i bira izvršno okruženje.\u003C\u002Fp>\n\u003Cp>Ta poslednja razlika je važna. „Upravljani agent” ne znači nužno da se „svo računanje odvija unutar OpenAI-ja”. Arhitektura Agents API-ja podržava rad bez okruženja, okruženje koje hostuje OpenAI, ili okruženje na sopstvenom hostingu povezano sa hostovanim harness-om. Sa okruženjem na sopstvenom hostingu, vaša aplikacija upravlja provizionisanjem, ponovnim povezivanjem, gašenjem i trajnim datotekama, dok harness ostaje pod upravljanjem OpenAI-ja.\u003C\u002Fp>\n\u003Cp>Agents API je stoga runtime servis, a ne samo format zahteva. Sesije mogu biti trajne, strimovati napredak, primati dodatne zadatke, koristiti alate, raditi sa datotekama i oporavljati se tokom dugotrajnog rada.\u003C\u002Fp>\n\u003Ch3 id=\"section-15\">Šta dobijate uz Agents API\u003C\u002Fh3>\n\u003Cul>\u003Cli>Upravljani Codex harness umesto da sami gradite i upravljate glavnom petljom agenta.\u003C\u002Fli>\u003Cli>Trajne sesije za rad koji obuhvata više koraka i dugotrajne zadatke.\u003C\u002Fli>\u003Cli>Upravljanu orkestraciju, sažimanje konteksta i oporavak.\u003C\u002Fli>\u003Cli>Izvršna okruženja koja hostuje OpenAI ili okruženja na sopstvenom hostingu, u zavisnosti od zahteva radnog opterećenja.\u003C\u002Fli>\u003Cli>Strimovanje i veb-hukove za praćenje napretka i događaja životnog ciklusa.\u003C\u002Fli>\u003Cli>Strateški pravac platforme koji OpenAI izričito preporučuje za nove agentske aplikacije.\u003C\u002Fli>\u003C\u002Ful>\n\u003Ch3 id=\"section-17\">Šta i dalje ostaje pod vašom kontrolom\u003C\u002Fh3>\n\u003Cul>\u003Cli>Vaš proizvod i aplikativni server.\u003C\u002Fli>\u003Cli>Implementacije funkcija-alata i poslovna logika.\u003C\u002Fli>\u003Cli>Odluke o autorizaciji i polisama koje se odnose na vaše sopstvene sisteme.\u003C\u002Fli>\u003Cli>Životni ciklus izvršnog okruženja kada se odlučite za računarske resurse na sopstvenom hostingu.\u003C\u002Fli>\u003Cli>Evaluacija, kriterijumi prihvatanja, specifični zaštitni mehanizmi za domen i odluka o tome šta je agentu dozvoljeno da radi.\u003C\u002Fli>\u003C\u002Ful>\n\u003Ch2 id=\"section-19\">2. Responses API: upravljajte petljom, koristite primitive platforme\u003C\u002Fh2>\n\u003Cp>Responses API je izbor nižeg nivoa kada želite mogućnosti OpenAI modela i alata bez delegiranja celokupnog radnog okruženja (runtime) agenta. OpenAI opisuje Responses kao preporučeni API primitiv za nove projekte i kao evoluciju Chat Completions-a sa ugrađenim alatima, opcijama stanja kroz više krugova razgovora, multimodalnim unosom i agentskim korišćenjem alata.\u003C\u002Fp>\n\u003Cp>Sam Responses zahtev može pozivati alate, ali vaša aplikacija ostaje odgovorna za širi radni tok kada gradite agenta oko njega. To znači da vaš kod odlučuje o tome kako perzistirati stanje aplikacije, kada nastaviti, kako se oporaviti od grešaka, kako koordinisati specijaliste, kako sažeti dugu istoriju i kako predstaviti rad koji se može nastaviti.\u003C\u002Fp>\n\u003Cp>Ovo nije suštinski lošije rešenje. To je prava granica kada ponašanje agenta mora biti duboko integrisano u postojeću logiku aplikacije, kada vam je potreban prilagođeni model stanja ili kada bi upravljani okvir (managed harness) sakrio kontrolu koja vam je zapravo potrebna.\u003C\u002Fp>\n\u003Ch2 id=\"section-23\">3. Agents SDK: podržan, ali više nije podrazumevani put za budući razvoj\u003C\u002Fh2>\n\u003Cp>Agents SDK ostaje radni okvir otvorenog koda za pokretanje radnih tokova agenata u vašoj aplikaciji. Pruža definicije agenata, alate, primopredaje (handoffs), zaštitne ograde (guardrails), praćenje (tracing), sesije i petlju izvršavanja u TypeScript-u i Python-u.\u003C\u002Fp>\n\u003Cp>Ali njegov strateški status se promenio. OpenAI sada označava Agents SDK kao funkcionalno završen (feature complete): održavanje, bezbednosne ispravke, kritične ispravke grešaka i rad na kompatibilnosti se nastavljaju, ali nove veće funkcionalnosti nisu planirane. OpenAI preporučuje Agents API za nove aplikacije.\u003C\u002Fp>\n\u003Cp>To ne znači da postojeću SDK aplikaciju treba odmah ponovo napisati. To znači da arhitektura treba da prestane da pretpostavlja da je SDK mesto na koje će stići sledeće velike mogućnosti radnog okruženja za agente.\u003C\u002Fp>\n\u003Caside class=\"editorjs-callout editorjs-callout--warning my-6 rounded-xl border p-5 border-amber-300 bg-amber-50 dark:border-amber-900 dark:bg-amber-950\u002F20\" role=\"note\">\u003Cstrong class=\"block mb-2 text-gray-900 dark:text-gray-100\">Nemojte prevoditi „feature complete” kao „zastarelo” (deprecated)\u003C\u002Fstrong>\u003Cdiv class=\"text-gray-700 dark:text-gray-200\">OpenAI nije opisao Agents SDK kao nepodržan. Postojeće aplikacije mogu nastaviti da ga koriste, a održavanje, bezbednost, kritične ispravke grešaka i rad na kompatibilnosti se nastavljaju. Važna promena je to što nove veće funkcionalnosti nisu planirane i nove aplikacije se usmeravaju na Agents API.\u003C\u002Fdiv>\u003C\u002Faside>\n\u003Ch2 id=\"section-28\">Gde se uklapa Codex SDK\u003C\u002Fh2>\n\u003Cp>Trenutni izbor nije jednostavno trostruko grananje. OpenAI-jev pregled radnih okruženja uključuje Codex SDK kao opciju za pokretanje Codex okvira u infrastrukturi kojom sami upravljate. To se arhitektonski razlikuje i od hostovanog Agents API-ja i od Agents SDK-a.\u003C\u002Fp>\n\u003Cp>Ako je vaš stvarni zahtev „Želim Codex okvir, ali moram sam njime da upravljam”, Codex SDK je rešenje koje treba proceniti. Ako je vaš zahtev „Želim da upravljam petljom oko poziva modela”, procenite Responses. Ako je vaš zahtev „Već imam funkcionalnu Agents SDK aplikaciju”, postojeći SDK može ostati validan dok pravite planove u skladu sa njegovim statusom održavanja.\u003C\u002Fp>\n\u003Ch2 id=\"section-31\">Test vlasništva nad radnim okruženjem\u003C\u002Fh2>\n\u003Cp>Korisna arhitektonska odluka počinje definisanjem onoga što vaš tim mora da poseduje. Ocenite svaki zahtev kao: mora kontrolisati, poželjno kontrolisati ili poželjno upravljano.\u003C\u002Fp>\n\u003Csection class=\"editorjs-comparison my-6\">\u003Ch3 class=\"mb-3 text-lg font-semibold\">Test vlasništva nad radnim okruženjem\u003C\u002Fh3>\u003Cdiv class=\"overflow-x-auto\">\u003Ctable class=\"w-full border-collapse\">\u003Cthead>\u003Ctr>\u003Cth class=\"border border-gray-300 bg-gray-50 px-4 py-3 text-left dark:border-gray-700 dark:bg-gray-900\">\u003C\u002Fth>\u003Cth class=\"border border-gray-300 bg-gray-50 px-4 py-3 text-left font-semibold dark:border-gray-700 dark:bg-gray-900\">Odluka\u003C\u002Fth>\u003Cth class=\"border border-gray-300 bg-gray-50 px-4 py-3 text-left font-semibold dark:border-gray-700 dark:bg-gray-900\">Ako preferirate upravljano\u003C\u002Fth>\u003Cth class=\"border border-gray-300 bg-gray-50 px-4 py-3 text-left font-semibold dark:border-gray-700 dark:bg-gray-900\">Ako zahtevate kontrolu\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\u003Ctbody>\u003Ctr>\u003Cth class=\"border border-gray-300 px-4 py-3 text-left font-semibold dark:border-gray-700\">Petlja agenta\u003C\u002Fth>\u003Ctd class=\"border border-gray-300 px-4 py-3 dark:border-gray-700\">\u003C\u002Ftd>\u003Ctd class=\"border border-gray-300 px-4 py-3 dark:border-gray-700\">\u003C\u002Ftd>\u003Ctd class=\"border border-gray-300 px-4 py-3 dark:border-gray-700\">\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Cth class=\"border border-gray-300 px-4 py-3 text-left font-semibold dark:border-gray-700\">Trajne sesije\u003C\u002Fth>\u003Ctd class=\"border border-gray-300 px-4 py-3 dark:border-gray-700\">\u003C\u002Ftd>\u003Ctd class=\"border border-gray-300 px-4 py-3 dark:border-gray-700\">\u003C\u002Ftd>\u003Ctd class=\"border border-gray-300 px-4 py-3 dark:border-gray-700\">\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Cth class=\"border border-gray-300 px-4 py-3 text-left font-semibold dark:border-gray-700\">Harness radno okruženje\u003C\u002Fth>\u003Ctd class=\"border border-gray-300 px-4 py-3 dark:border-gray-700\">\u003C\u002Ftd>\u003Ctd class=\"border border-gray-300 px-4 py-3 dark:border-gray-700\">\u003C\u002Ftd>\u003Ctd class=\"border border-gray-300 px-4 py-3 dark:border-gray-700\">\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Cth class=\"border border-gray-300 px-4 py-3 text-left font-semibold dark:border-gray-700\">Okruženje za izvršavanje\u003C\u002Fth>\u003Ctd class=\"border border-gray-300 px-4 py-3 dark:border-gray-700\">\u003C\u002Ftd>\u003Ctd class=\"border border-gray-300 px-4 py-3 dark:border-gray-700\">\u003C\u002Ftd>\u003Ctd class=\"border border-gray-300 px-4 py-3 dark:border-gray-700\">\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Cth class=\"border border-gray-300 px-4 py-3 text-left font-semibold dark:border-gray-700\">Semantika orkestracije\u003C\u002Fth>\u003Ctd class=\"border border-gray-300 px-4 py-3 dark:border-gray-700\">\u003C\u002Ftd>\u003Ctd class=\"border border-gray-300 px-4 py-3 dark:border-gray-700\">\u003C\u002Ftd>\u003Ctd class=\"border border-gray-300 px-4 py-3 dark:border-gray-700\">\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Cth class=\"border border-gray-300 px-4 py-3 text-left font-semibold dark:border-gray-700\">Fleksibilnost provajdera \u002F transporta\u003C\u002Fth>\u003Ctd class=\"border border-gray-300 px-4 py-3 dark:border-gray-700\">\u003C\u002Ftd>\u003Ctd class=\"border border-gray-300 px-4 py-3 dark:border-gray-700\">\u003C\u002Ftd>\u003Ctd class=\"border border-gray-300 px-4 py-3 dark:border-gray-700\">\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Cth class=\"border border-gray-300 px-4 py-3 text-left font-semibold dark:border-gray-700\">Operativno opterećenje\u003C\u002Fth>\u003Ctd class=\"border border-gray-300 px-4 py-3 dark:border-gray-700\">\u003C\u002Ftd>\u003Ctd class=\"border border-gray-300 px-4 py-3 dark:border-gray-700\">\u003C\u002Ftd>\u003Ctd class=\"border border-gray-300 px-4 py-3 dark:border-gray-700\">\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\u003C\u002Fsection>\n\u003Ch2 id=\"section-34\">Stablo odlučivanja za nove sisteme\u003C\u002Fh2>\n\u003Csection class=\"editorjs-process my-6\">\u003Ch3 class=\"mb-3 text-lg font-semibold\">Izaberite radno okruženje prema granici kontrole\u003C\u002Fh3>\u003Cdiv class=\"grid grid-cols-1 md:grid-cols-2 xl:grid-cols-3 gap-4\">\u003Cdiv class=\"editorjs-process__step min-w-0  rounded-xl border border-gray-200 dark:border-gray-700 p-4\">\u003Cdiv class=\"text-xs font-semibold text-gray-500 dark:text-gray-400\">1\u003C\u002Fdiv>\u003Cdiv class=\"mt-1 font-semibold text-gray-900 dark:text-gray-100\">1. Da li je ovo nova aplikacija sa agentima?\u003C\u002Fdiv>\u003Cdiv class=\"mt-1 text-sm text-gray-600 dark:text-gray-300\">Ako nije, nemojte migrirati samo zato što postoji novije rešenje. Najpre procenite stvarna ograničenja trenutne aplikacije.\u003C\u002Fdiv>\u003C\u002Fdiv>\u003Cdiv class=\"editorjs-process__step min-w-0  rounded-xl border border-gray-200 dark:border-gray-700 p-4\">\u003Cdiv class=\"text-xs font-semibold text-gray-500 dark:text-gray-400\">2\u003C\u002Fdiv>\u003Cdiv class=\"mt-1 font-semibold text-gray-900 dark:text-gray-100\">2. Da li želite upravljani okvir za dugotrajne agente?\u003C\u002Fdiv>\u003Cdiv class=\"mt-1 text-sm text-gray-600 dark:text-gray-300\">Ako želite, počnite sa Agents API-jem kao preporučenim pravcem kompanije OpenAI za nove aplikacije sa agentima.\u003C\u002Fdiv>\u003C\u002Fdiv>\u003Cdiv class=\"editorjs-process__step min-w-0  rounded-xl border border-gray-200 dark:border-gray-700 p-4\">\u003Cdiv class=\"text-xs font-semibold text-gray-500 dark:text-gray-400\">3\u003C\u002Fdiv>\u003Cdiv class=\"mt-1 font-semibold text-gray-900 dark:text-gray-100\">3. Da li vam je potreban Codex okvir, ali morate sami njime da upravljate?\u003C\u002Fdiv>\u003Cdiv class=\"mt-1 text-sm text-gray-600 dark:text-gray-300\">Procenite Codex SDK umesto ponovne izgradnje ponašanja okvira na bazi Agents SDK-a.\u003C\u002Fdiv>\u003C\u002Fdiv>\u003Cdiv class=\"editorjs-process__step min-w-0  rounded-xl border border-gray-200 dark:border-gray-700 p-4\">\u003Cdiv class=\"text-xs font-semibold text-gray-500 dark:text-gray-400\">4\u003C\u002Fdiv>\u003Cdiv class=\"mt-1 font-semibold text-gray-900 dark:text-gray-100\">4. Da li je potrebno da posedujete sopstvenu petlju agenta i model stanja?\u003C\u002Fdiv>\u003Cdiv class=\"mt-1 text-sm text-gray-600 dark:text-gray-300\">Koristite Responses API kao platformski primitiv nižeg nivoa i izgradite petlju oko njega.\u003C\u002Fdiv>\u003C\u002Fdiv>\u003Cdiv class=\"editorjs-process__step min-w-0  rounded-xl border border-gray-200 dark:border-gray-700 p-4\">\u003Cdiv class=\"text-xs font-semibold text-gray-500 dark:text-gray-400\">5\u003C\u002Fdiv>\u003Cdiv class=\"mt-1 font-semibold text-gray-900 dark:text-gray-100\">5. Da li već koristite Agents SDK?\u003C\u002Fdiv>\u003Cdiv class=\"mt-1 text-sm text-gray-600 dark:text-gray-300\">Nastavite ukoliko ispunjava zahteve; nove veće funkcionalnosti nisu planirane, pa buduće usvajanje platforme tretirajte kao eksplicitnu odluku u mapi razvoja.\u003C\u002Fdiv>\u003C\u002Fdiv>\u003Cdiv class=\"editorjs-process__step min-w-0  rounded-xl border border-gray-200 dark:border-gray-700 p-4\">\u003Cdiv class=\"text-xs font-semibold text-gray-500 dark:text-gray-400\">6\u003C\u002Fdiv>\u003Cdiv class=\"mt-1 font-semibold text-gray-900 dark:text-gray-100\">6. Da li u Agents API-ju nedostaje potrebna mogućnost?\u003C\u002Fdiv>\u003Cdiv class=\"mt-1 text-sm text-gray-600 dark:text-gray-300\">OpenAI izričito dozvoljava Agents SDK kao kratkoročnu opciju za nove aplikacije kojima su potrebne nepodržane mogućnosti.\u003C\u002Fdiv>\u003C\u002Fdiv>\u003Cdiv class=\"editorjs-process__step min-w-0  rounded-xl border border-gray-200 dark:border-gray-700 p-4\">\u003Cdiv class=\"text-xs font-semibold text-gray-500 dark:text-gray-400\">7\u003C\u002Fdiv>\u003Cdiv class=\"mt-1 font-semibold text-gray-900 dark:text-gray-100\">7. Validacija kroz probni prototip u produkcijskim uslovima\u003C\u002Fdiv>\u003Cdiv class=\"mt-1 text-sm text-gray-600 dark:text-gray-300\">Testirajte alate, okruženje, odobrenja, kašnjenje, opservabilnost, oporavak od grešaka i životni ciklus pre konačnog zaključavanja arhitekture.\u003C\u002Fdiv>\u003C\u002Fdiv>\u003C\u002Fdiv>\u003C\u002Fsection>\n\u003Ch2 id=\"section-36\">Šta ne bi trebalo da vodi donošenje odluke\u003C\u002Fh2>\n\u003Cdiv class=\"overflow-x-auto\">\u003Ctable class=\"w-full border-collapse\">\u003Cthead>\u003Ctr>\u003Cth class=\"border border-gray-300 px-4 py-2 text-left font-semibold\">Slabo pravilo odlučivanja\u003C\u002Fth>\u003Cth class=\"border border-gray-300 px-4 py-2 text-left font-semibold\">Zašto ne uspeva\u003C\u002Fth>\u003Cth class=\"border border-gray-300 px-4 py-2 text-left font-semibold\">Bolje pitanje\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\u003Ctbody>\u003Ctr>\u003Ctd class=\"border border-gray-300 px-4 py-2\">„Najnoviji API mora biti najbolji.”\u003C\u002Ftd>\u003Ctd class=\"border border-gray-300 px-4 py-2\">Novije rešenje može biti strateški poželjnije, a da mu i dalje nedostaje funkcionalnost koja vam je potrebna.\u003C\u002Ftd>\u003Ctd class=\"border border-gray-300 px-4 py-2\">Koje odgovornosti izvršnog okruženja treba da budu upravljane, a koje u vlasništvu aplikacije?\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd class=\"border border-gray-300 px-4 py-2\">„Već poznajemo SDK.”\u003C\u002Ftd>\u003Ctd class=\"border border-gray-300 px-4 py-2\">Poznavanje alata u timu može sačuvati arhitekturu čiji se plan razvoja promenio.\u003C\u002Ftd>\u003Ctd class=\"border border-gray-300 px-4 py-2\">Koliki je trošak ostanka u poređenju sa prelaskom tokom sledećeg ciklusa proizvoda?\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd class=\"border border-gray-300 px-4 py-2\">„Upravljano znači bez infrastrukture.”\u003C\u002Ftd>\u003Ctd class=\"border border-gray-300 px-4 py-2\">Agents API i dalje može koristiti samostalno hostovana okruženja, a vaša aplikacija i dalje zadržava logiku proizvoda.\u003C\u002Ftd>\u003Ctd class=\"border border-gray-300 px-4 py-2\">Koji infrastrukturni sloj se zapravo delegira?\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd class=\"border border-gray-300 px-4 py-2\">„Responses služi samo za jednostavne pozive.”\u003C\u002Ftd>\u003Ctd class=\"border border-gray-300 px-4 py-2\">Responses pruža ugrađene alate i primitive stanja; može biti osnova za prilagođene petlje agenata.\u003C\u002Ftd>\u003Ctd class=\"border border-gray-300 px-4 py-2\">Da li nam je potrebno da platforma upravlja okvirom, ili samo primitivima modela\u002Falata?\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd class=\"border border-gray-300 px-4 py-2\">„Završetak razvoja novih funkcija znači da moramo odmah da migriramo.”\u003C\u002Ftd>\u003Ctd class=\"border border-gray-300 px-4 py-2\">SDK ostaje održavan za postojeće aplikacije.\u003C\u002Ftd>\u003Ctd class=\"border border-gray-300 px-4 py-2\">Koji konkretan budući zahtev je blokiran ostankom?\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Ch2 id=\"section-38\">Migracija je arhitektonska promena, a ne preimenovanje uvoza\u003C\u002Fh2>\n\u003Cp>Prelazak sa Agents SDK na Agents API menja vlasništvo. U SDK-u, petlja se izvršava u vašoj aplikaciji. U Agents API-ju, OpenAI upravlja okvirom i sesijom, dok se vaša aplikacija integriše putem zadataka, događaja, alata i granica okruženja.\u003C\u002Fp>\n\u003Cp>Pravi plan migracije stoga mora da mapira stanje sesije, prilagođenu orkestraciju, prenošenje zadataka, izvršavanje alata, odobrenja, skladištenje, praćenje, ponovne pokušaje, oporavak od grešaka, životni ciklus okruženja i sve apstrakcije specifične za provajdera. Obim koda može se smanjiti dok se operativne pretpostavke menjaju.\u003C\u002Fp>\n\u003Ch3 id=\"section-41\">Popis elemenata za migraciju\u003C\u002Fh3>\n\u003Cul>\u003Cli>Definicije agenata i vlasništvo nad instrukcijama.\u003C\u002Fli>\u003Cli>Definicije alata i lokacija gde se svaki alat izvršava.\u003C\u002Fli>\u003Cli>Prenošenje zadataka, obrasci menadžera\u002Fspecijaliste i ponašanje podagenata.\u003C\u002Fli>\u003Cli>Identifikatori sesije, stanje razgovora, mogućnost nastavka i zadržavanje istorije.\u003C\u002Fli>\u003Cli>Ljudska odobrenja i semantika prekida.\u003C\u002Fli>\u003Cli>Prilagođena logika za skraćivanje ili zbijanje konteksta.\u003C\u002Fli>\u003Cli>Praćenje, evaluacije, opservabilnost i otklanjanje grešaka u produkciji.\u003C\u002Fli>\u003Cli>Samostalno hostovane datoteke, kontejneri, pristup privatnoj mreži ili druge zavisnosti izvršavanja.\u003C\u002Fli>\u003Cli>Apstrakcija provajdera ili zavisnosti od modela koji nisu OpenAI.\u003C\u002Fli>\u003Cli>Pretpostavke o ponovnim pokušajima, vremenskom isteku, idempotentnosti, oporavku i životnom ciklusu.\u003C\u002Fli>\u003C\u002Ful>\n\u003Ch2 id=\"section-43\">Javna beta menja model rizika\u003C\u002Fh2>\n\u003Cp>Agents API je preporučeni smer za nove agentske aplikacije, ali je takođe u javnoj beta verziji. Te činjenice nisu u suprotnosti. Strateški smer odgovara na pitanje „kuda platforma ide?”, dok beta status odgovara na pitanje „koliko promena interfejsa i operativnih promena treba planirati u budžetu?”\u003C\u002Fp>\n\u003Cp>Za produkcione sisteme, izolujte integraciju iza granice aplikacije. Držite stanje domena, dozvole, revizorske podatke i poslovna pravila van objekata sesije specifičnih za dobavljača gde god je to moguće. Ovo olakšava prilagođavanje evoluciji API-ja bez pretvaranja izvršnog okruženja agenta u izvor istine za ceo vaš proizvod.\u003C\u002Fp>\n\u003Ch2 id=\"section-46\">Praktična podrazumevana arhitektura\u003C\u002Fh2>\n\u003Cp>Za mnoge nove izvorne OpenAI aplikacije, razuman podrazumevani izbor za 2026. godinu jeste: Agents API za upravljani okvir i trajnu sesiju, domenski servisi i autorizacija u vlasništvu aplikacije, eksplicitni alati funkcija za poslovne akcije, i izvršavanje hostovano od strane OpenAI-ja ili samostalno, u zavisnosti od zahteva za podacima i računarskim resursima.\u003C\u002Fp>\n\u003Cp>To održava izvršno okruženje agenta moćnim, a da ono ne postane vlasnik poslovne istine. Aplikacija i dalje odlučuje šta korisnik sme da uradi, koji su podaci merodavni, koje akcije zahtevaju odobrenje i kako se rezultati validiraju.\u003C\u002Fp>\n\u003Caside class=\"editorjs-referral my-6\">\u003Ca href=\"https:\u002F\u002Fstajic.de\u002Fsr\u002Fblog\u002Fai-agent-reliability-why-the-final-answer-is-not-enough\" class=\"flex flex-col sm:flex-row gap-4 rounded-xl border border-gray-200 dark:border-gray-700 p-4 transition hover:border-primary-500\">\u003Cdiv class=\"min-w-0 flex-1\">\u003Cstrong class=\"block text-lg text-gray-900 dark:text-gray-100\">Pouzdanost AI agenata: Zašto konačni odgovor nije dovoljan\u003C\u002Fstrong>\u003Cp class=\"mt-2 text-sm text-gray-600 dark:text-gray-300\">Upravljani okvir smanjuje operativno opterećenje, ali pouzdanost i dalje zahteva sledljivo izvršavanje, eksplicitne kriterijume prihvatljivosti i evaluaciju koja prevazilazi konačni odgovor.\u003C\u002Fp>\u003Cspan class=\"mt-3 inline-flex text-sm font-medium text-primary-600 dark:text-primary-400\">Pročitajte članak o pouzdanosti →\u003C\u002Fspan>\u003C\u002Fdiv>\u003C\u002Fa>\u003C\u002Faside>\n\u003Ch2 id=\"section-50\">Šta bi promenilo ovaj odgovor?\u003C\u002Fh2>\n\u003Cp>Preporuka se menja ako Agents API doda ili ukloni mogućnosti, izađe iz beta verzije sa drugačijim ugovorima, promeni granice okruženja ili cene, ili uvede alate za migraciju koji smanjuju razlike u vlasništvu. Takođe se menja ako vaša aplikacija zavisi od prenosivosti među provajderima, prilagođene semantike orkestracije, isključivo lokalnog izvršavanja ili mogućnosti koju hostovani okvir ne može da podrži.\u003C\u002Fp>\n\u003Cp>Za postojeću aplikaciju zasnovanu na Agents SDK-u, odgovor se takođe menja sa troškovima migracije. Ako je sistem stabilan, dobro evaluiran i nije blokiran statusom SDK-a koji označava završetak razvoja novih funkcija, trenutna migracija može stvoriti više rizika nego vrednosti. Ako plan razvoja proizvoda zavisi od mogućnosti koje dolaze isključivo u Agents API, odlaganje migracije može stvoriti drugačiju vrstu tehničkog duga.\u003C\u002Fp>\n\u003Ch2 id=\"section-53\">Ograničenja\u003C\u002Fh2>\n\u003Cp>Ovo poređenje se fokusira na vlasništvo nad izvršnim okruženjem i navedeni pravac platforme kompanije OpenAI. Ono ne meri kašnjenje, kvalitet ili ukupne troškove za specifično radno opterećenje. Ta svojstva zavise od izbora modela, korišćenja alata, okruženja, dužine zadatka, keširanja, upotrebe sandbox okruženja i arhitekture aplikacije.\u003C\u002Fp>\n\u003Cp>Agents API je takođe dovoljno nov da se produkciono iskustvo još uvek prikuplja. Zbog toga bi dizajn trebalo validirati reprezentativnim radnim opterećenjima, a ne birati ga isključivo na osnovu pozicioniranja proizvoda.\u003C\u002Fp>\n\u003Ch2 id=\"section-56\">Zaključak\u003C\u002Fh2>\n\u003Cp>Odluka o OpenAI agentima za 2026. godinu u osnovi se svodi na vlasništvo nad runtime-om. Agents API znači da OpenAI poseduje veći deo harness-a i mehanizama za trajne sesije. Responses znači da vaša aplikacija poseduje petlju oko primitivnih elemenata platforme. Agents SDK ostaje validan za postojeće sisteme, ali više nije podrazumevano odredište za važne nove funkcije agent runtime-a.\u003C\u002Fp>\n\u003Cp>Za novu aplikaciju, pratite smer platforme osim ako vas stvarni zahtev ne natera da se spustite niže u steku. Počnite sa Agents API-jem, pređite na Responses kada vam je potrebno da sami kontrolišete petlju, razmotrite Codex SDK kada vam je potreban harness u sopstvenoj infrastrukturi, i zadržite Agents SDK tamo gde to opravdavaju postojeća ulaganja ili privremeni nedostaci u mogućnostima.\u003C\u002Fp>\n\u003Ch2 id=\"section-59\">Česta pitanja\u003C\u002Fh2>\n\u003Csection class=\"editorjs-faq my-6 rounded-xl border border-gray-200 p-5 dark:border-gray-700\">\u003Ch3 class=\"mb-3 text-lg font-semibold\">Izbori za OpenAI agent runtime u 2026. godini\u003C\u002Fh3>\u003Cdiv id=\"faq1\" class=\"border-t border-gray-200 py-4 first:border-t-0 dark:border-gray-700\">\u003Ch4 class=\"font-semibold text-gray-900 dark:text-gray-100\">Da li bi trebalo da koristim OpenAI Agents API ili Agents SDK za novi projekat?\u003C\u002Fh4>\u003Cdiv class=\"mt-2 text-gray-600 dark:text-gray-300\">OpenAI trenutno preporučuje Agents API za nove aplikacije sa agentima. Agents SDK je funkcionalno završen i ostaje podržan za postojeće aplikacije, uz nastavak održavanja, bezbednosnih ispravki, kritičnih popravki grešaka i rada na kompatibilnosti.\u003C\u002Fdiv>\u003C\u002Fdiv>\u003Cdiv id=\"faq2\" class=\"border-t border-gray-200 py-4 first:border-t-0 dark:border-gray-700\">\u003Ch4 class=\"font-semibold text-gray-900 dark:text-gray-100\">Da li je Agents SDK zastareo?\u003C\u002Fh4>\u003Cdiv class=\"mt-2 text-gray-600 dark:text-gray-300\">OpenAI ga opisuje kao funkcionalno završenog, a ne kao nepodržanog. Velike nove funkcionalnosti nisu planirane, ali se održavanje, bezbednosne ispravke, kritične ispravke grešaka i rad na kompatibilnosti nastavljaju.\u003C\u002Fdiv>\u003C\u002Fdiv>\u003Cdiv id=\"faq3\" class=\"border-t border-gray-200 py-4 first:border-t-0 dark:border-gray-700\">\u003Ch4 class=\"font-semibold text-gray-900 dark:text-gray-100\">Kada bi trebalo da koristim Responses API umesto Agents API-ja?\u003C\u002Fh4>\u003Cdiv class=\"mt-2 text-gray-600 dark:text-gray-300\">Koristite Responses kada vaša aplikacija treba da upravlja petljom agenta, strategijom stanja, orkestracijom i logikom nastavka, dok i dalje koristi OpenAI modele i alate platforme.\u003C\u002Fdiv>\u003C\u002Fdiv>\u003Cdiv id=\"faq4\" class=\"border-t border-gray-200 py-4 first:border-t-0 dark:border-gray-700\">\u003Ch4 class=\"font-semibold text-gray-900 dark:text-gray-100\">Da li Agents API zahteva računarske resurse koje hostuje OpenAI?\u003C\u002Fh4>\u003Cdiv class=\"mt-2 text-gray-600 dark:text-gray-300\">Ne. Agents API može funkcionisati bez izvršnog okruženja, u okruženju koje hostuje OpenAI, ili u samostalno hostovanom okruženju povezanom sa upravljanim harness-om.\u003C\u002Fdiv>\u003C\u002Fdiv>\u003Cdiv id=\"faq5\" class=\"border-t border-gray-200 py-4 first:border-t-0 dark:border-gray-700\">\u003Ch4 class=\"font-semibold text-gray-900 dark:text-gray-100\">Gde se uklapa Codex SDK?\u003C\u002Fh4>\u003Cdiv class=\"mt-2 text-gray-600 dark:text-gray-300\">OpenAI pozicionira Codex SDK za pokretanje Codex harness-a na infrastrukturi kojom sami upravljate. To je relevantna opcija kada želite harness, ali ne i hostovani Agents API runtime.\u003C\u002Fdiv>\u003C\u002Fdiv>\u003Cdiv id=\"faq6\" class=\"border-t border-gray-200 py-4 first:border-t-0 dark:border-gray-700\">\u003Ch4 class=\"font-semibold text-gray-900 dark:text-gray-100\">Da li bi postojeća Agents SDK aplikacija trebalo odmah da migrira?\u003C\u002Fh4>\u003Cdiv class=\"mt-2 text-gray-600 dark:text-gray-300\">Ne automatski. Procenite da li je trenutni sistem blokiran statusom SDK-a kao funkcionalno završenog, da li potrebne mogućnosti postoje u Agents API-ju i da li korist od migracije nadmašuje operativne i arhitektonske promene.\u003C\u002Fdiv>\u003C\u002Fdiv>\u003C\u002Fsection>\n\u003Ch2 id=\"section-61\">Rečnik pojmova\u003C\u002Fh2>\n\u003Csection class=\"editorjs-glossary my-6 rounded-xl border border-gray-200 dark:border-gray-700 p-5\">\u003Ch3 class=\"mb-3 text-lg font-semibold\">Ključni runtime pojmovi\u003C\u002Fh3>\u003Cdl>\u003Cdiv id=\"harness\" class=\"border-t border-gray-200 dark:border-gray-700 py-3 first:border-t-0\">\u003Cdt class=\"font-semibold text-gray-900 dark:text-gray-100\">Harness\u003C\u002Fdt>\u003Cdd class=\"mt-1 text-gray-600 dark:text-gray-300\">Runtime petlja i prateći mehanizmi koji koordiniraju pozive modela, alate, kontekst, sesije i izvršavanje agenta.\u003C\u002Fdd>\u003C\u002Fdiv>\u003Cdiv id=\"agents-api\" class=\"border-t border-gray-200 dark:border-gray-700 py-3 first:border-t-0\">\u003Cdt class=\"font-semibold text-gray-900 dark:text-gray-100\">Agents API\u003C\u002Fdt>\u003Cdd class=\"mt-1 text-gray-600 dark:text-gray-300\">OpenAI-jev upravljani API za trajne agente u oblaku koji koriste hostovani Codex harness.\u003C\u002Fdd>\u003C\u002Fdiv>\u003Cdiv id=\"responses-api\" class=\"border-t border-gray-200 dark:border-gray-700 py-3 first:border-t-0\">\u003Cdt class=\"font-semibold text-gray-900 dark:text-gray-100\">Responses API\u003C\u002Fdt>\u003Cdd class=\"mt-1 text-gray-600 dark:text-gray-300\">OpenAI-jev API primitiv nižeg nivoa za odgovore modela, hostovane alate i interakcije sa stanjem, oko kojih aplikacije mogu izgraditi sopstvenu petlju agenta.\u003C\u002Fdd>\u003C\u002Fdiv>\u003Cdiv id=\"agents-sdk\" class=\"border-t border-gray-200 dark:border-gray-700 py-3 first:border-t-0\">\u003Cdt class=\"font-semibold text-gray-900 dark:text-gray-100\">Agents SDK\u003C\u002Fdt>\u003Cdd class=\"mt-1 text-gray-600 dark:text-gray-300\">OpenAI-jev open-source radni okvir za pokretanje tokova rada agenata u kodu aplikacije; funkcionalno završen od septembra 2026.\u003C\u002Fdd>\u003C\u002Fdiv>\u003Cdiv id=\"codex-sdk\" class=\"border-t border-gray-200 dark:border-gray-700 py-3 first:border-t-0\">\u003Cdt class=\"font-semibold text-gray-900 dark:text-gray-100\">Codex SDK\u003C\u002Fdt>\u003Cdd class=\"mt-1 text-gray-600 dark:text-gray-300\">Runtime opcija koju OpenAI navodi za pokretanje Codex harness-a na infrastrukturi kojom sami upravljate.\u003C\u002Fdd>\u003C\u002Fdiv>\u003Cdiv id=\"runtime-ownership\" class=\"border-t border-gray-200 dark:border-gray-700 py-3 first:border-t-0\">\u003Cdt class=\"font-semibold text-gray-900 dark:text-gray-100\">Runtime ownership\u003C\u002Fdt>\u003Cdd class=\"mt-1 text-gray-600 dark:text-gray-300\">Arhitektonska granica koja opisuje kojim delovima petlje agenta, stanja sesije, izvršnog okruženja i životnog ciklusa upravlja platforma, a kojim aplikacija.\u003C\u002Fdd>\u003C\u002Fdiv>\u003C\u002Fdl>\u003C\u002Fsection>\n\u003Ch2 id=\"section-63\">Primarni izvori i dodatna literatura\u003C\u002Fh2>\n\u003Ca href=\"https:\u002F\u002Fopenai.com\u002Findex\u002Fintroducing-the-agents-api\u002F\" target=\"_blank\" rel=\"noopener noreferrer\" class=\"editorjs-link-tool block border border-gray-200 dark:border-gray-700 rounded-lg p-4 transition text-gray-900 dark:text-gray-100 hover:border-primary-500 hover:bg-primary-50 dark:hover:bg-gray-900 hover:text-gray-900 dark:hover:text-gray-100\">\u003Cstrong class=\"block font-semibold\">OpenAI — Predstavljanje Agents API-ja\u003C\u002Fstrong>\u003Cp class=\"text-sm text-gray-600 dark:text-gray-400\">Najava lansiranja Agents API-ja od 10. septembra 2026. godine, koja opisuje upravljani Codex harness i javnu beta verziju.\u003C\u002Fp>\u003C\u002Fa>\n\u003Ca href=\"https:\u002F\u002Fdevelopers.openai.com\u002Fapi\u002Fdocs\u002Fguides\u002Fagents\" target=\"_blank\" rel=\"noopener noreferrer\" class=\"editorjs-link-tool block border border-gray-200 dark:border-gray-700 rounded-lg p-4 transition text-gray-900 dark:text-gray-100 hover:border-primary-500 hover:bg-primary-50 dark:hover:bg-gray-900 hover:text-gray-900 dark:hover:text-gray-100\">\u003Cstrong class=\"block font-semibold\">OpenAI — Pregled agent runtime-a\u003C\u002Fstrong>\u003Cp class=\"text-sm text-gray-600 dark:text-gray-400\">Trenutno poređenje Agents API-ja, Codex SDK-a i Responses API-ja, uključujući status podrške za Agents SDK.\u003C\u002Fp>\u003C\u002Fa>\n\u003Ca href=\"https:\u002F\u002Fdevelopers.openai.com\u002Fapi\u002Fdocs\u002Fguides\u002Fagents-api\u002Foverview\" target=\"_blank\" rel=\"noopener noreferrer\" class=\"editorjs-link-tool block border border-gray-200 dark:border-gray-700 rounded-lg p-4 transition text-gray-900 dark:text-gray-100 hover:border-primary-500 hover:bg-primary-50 dark:hover:bg-gray-900 hover:text-gray-900 dark:hover:text-gray-100\">\u003Cstrong class=\"block font-semibold\">OpenAI — Pregled Agents API-ja\u003C\u002Fstrong>\u003Cp class=\"text-sm text-gray-600 dark:text-gray-400\">Dokumentacija za trajne agente u oblaku, sesije, orkestraciju, sažimanje konteksta, oporavak i izbor okruženja.\u003C\u002Fp>\u003C\u002Fa>\n\u003Ca href=\"https:\u002F\u002Fdevelopers.openai.com\u002Fapi\u002Fdocs\u002Fguides\u002Fagents-api\u002Farchitecture\" target=\"_blank\" rel=\"noopener noreferrer\" class=\"editorjs-link-tool block border border-gray-200 dark:border-gray-700 rounded-lg p-4 transition text-gray-900 dark:text-gray-100 hover:border-primary-500 hover:bg-primary-50 dark:hover:bg-gray-900 hover:text-gray-900 dark:hover:text-gray-100\">\u003Cstrong class=\"block font-semibold\">OpenAI — Arhitektura Agents API-ja\u003C\u002Fstrong>\u003Cp class=\"text-sm text-gray-600 dark:text-gray-400\">Arhitektonska granica između hostovanog harness-a, aplikativnog servera i izvršnih okruženja bez okruženja, hostovanih od strane OpenAI-ja ili samostalno hostovanih.\u003C\u002Fp>\u003C\u002Fa>\n\u003Ca href=\"https:\u002F\u002Fdevelopers.openai.com\u002Fapi\u002Fdocs\u002Fguides\u002Fagents\u002Fsdk\" target=\"_blank\" rel=\"noopener noreferrer\" class=\"editorjs-link-tool block border border-gray-200 dark:border-gray-700 rounded-lg p-4 transition text-gray-900 dark:text-gray-100 hover:border-primary-500 hover:bg-primary-50 dark:hover:bg-gray-900 hover:text-gray-900 dark:hover:text-gray-100\">\u003Cstrong class=\"block font-semibold\">OpenAI — Agents SDK\u003C\u002Fstrong>\u003Cp class=\"text-sm text-gray-600 dark:text-gray-400\">Trenutno obaveštenje o podršci za Agents SDK i objašnjenje petlje agenta u vlasništvu aplikacije.\u003C\u002Fp>\u003C\u002Fa>\n\u003Ca href=\"https:\u002F\u002Fdevelopers.openai.com\u002Fapi\u002Fdocs\u002Fguides\u002Fmigrate-to-responses\" target=\"_blank\" rel=\"noopener noreferrer\" class=\"editorjs-link-tool block border border-gray-200 dark:border-gray-700 rounded-lg p-4 transition text-gray-900 dark:text-gray-100 hover:border-primary-500 hover:bg-primary-50 dark:hover:bg-gray-900 hover:text-gray-900 dark:hover:text-gray-100\">\u003Cstrong class=\"block font-semibold\">OpenAI — Migracija na Responses API\u003C\u002Fstrong>\u003Cp class=\"text-sm text-gray-600 dark:text-gray-400\">Trenutno pozicioniranje Responses API-ja, ugrađeni alati, kontekst sa stanjem i agentski primitivi.\u003C\u002Fp>\u003C\u002Fa>\n\u003Cnav class=\"editorjs-toc\" data-editorjs-toc=\"true\" aria-label=\"Sadržaj\">\u003Cstrong class=\"editorjs-toc__title\">Sadržaj\u003C\u002Fstrong>\u003Col class=\"editorjs-toc__list editorjs-toc__list--depth-0\">\u003Cli class=\"editorjs-toc__item\">\u003Ca href=\"#section-6\" class=\"editorjs-toc__link\">Arhitektura se promenila: izaberite granicu runtime-a, a ne biblioteku\u003C\u002Fa>\u003C\u002Fli>\u003Cli class=\"editorjs-toc__item\">\u003Ca href=\"#section-9\" class=\"editorjs-toc__link\">Kratko poređenje\u003C\u002Fa>\u003C\u002Fli>\u003Cli class=\"editorjs-toc__item\">\u003Ca href=\"#section-11\" class=\"editorjs-toc__link\">1. Agents API: upravljani harness, trajni cloud agent\u003C\u002Fa>\u003Col class=\"editorjs-toc__list editorjs-toc__list--depth-1\">\u003Cli class=\"editorjs-toc__item\">\u003Ca href=\"#section-15\" class=\"editorjs-toc__link\">Šta dobijate uz Agents API\u003C\u002Fa>\u003C\u002Fli>\u003Cli class=\"editorjs-toc__item\">\u003Ca href=\"#section-17\" class=\"editorjs-toc__link\">Šta i dalje ostaje pod vašom kontrolom\u003C\u002Fa>\u003C\u002Fli>\u003C\u002Fol>\u003C\u002Fli>\u003Cli class=\"editorjs-toc__item\">\u003Ca href=\"#section-19\" class=\"editorjs-toc__link\">2. Responses API: upravljajte petljom, koristite primitive platforme\u003C\u002Fa>\u003C\u002Fli>\u003Cli class=\"editorjs-toc__item\">\u003Ca href=\"#section-23\" class=\"editorjs-toc__link\">3. Agents SDK: podržan, ali više nije podrazumevani put za budući razvoj\u003C\u002Fa>\u003C\u002Fli>\u003Cli class=\"editorjs-toc__item\">\u003Ca href=\"#section-28\" class=\"editorjs-toc__link\">Gde se uklapa Codex SDK\u003C\u002Fa>\u003C\u002Fli>\u003Cli class=\"editorjs-toc__item\">\u003Ca href=\"#section-31\" class=\"editorjs-toc__link\">Test vlasništva nad radnim okruženjem\u003C\u002Fa>\u003C\u002Fli>\u003Cli class=\"editorjs-toc__item\">\u003Ca href=\"#section-34\" class=\"editorjs-toc__link\">Stablo odlučivanja za nove sisteme\u003C\u002Fa>\u003C\u002Fli>\u003Cli class=\"editorjs-toc__item\">\u003Ca href=\"#section-36\" class=\"editorjs-toc__link\">Šta ne bi trebalo da vodi donošenje odluke\u003C\u002Fa>\u003C\u002Fli>\u003Cli class=\"editorjs-toc__item\">\u003Ca href=\"#section-38\" class=\"editorjs-toc__link\">Migracija je arhitektonska promena, a ne preimenovanje uvoza\u003C\u002Fa>\u003Col class=\"editorjs-toc__list editorjs-toc__list--depth-1\">\u003Cli class=\"editorjs-toc__item\">\u003Ca href=\"#section-41\" class=\"editorjs-toc__link\">Popis elemenata za migraciju\u003C\u002Fa>\u003C\u002Fli>\u003C\u002Fol>\u003C\u002Fli>\u003Cli class=\"editorjs-toc__item\">\u003Ca href=\"#section-43\" class=\"editorjs-toc__link\">Javna beta menja model rizika\u003C\u002Fa>\u003C\u002Fli>\u003Cli class=\"editorjs-toc__item\">\u003Ca href=\"#section-46\" class=\"editorjs-toc__link\">Praktična podrazumevana arhitektura\u003C\u002Fa>\u003C\u002Fli>\u003Cli class=\"editorjs-toc__item\">\u003Ca href=\"#section-50\" class=\"editorjs-toc__link\">Šta bi promenilo ovaj odgovor?\u003C\u002Fa>\u003C\u002Fli>\u003Cli class=\"editorjs-toc__item\">\u003Ca href=\"#section-53\" class=\"editorjs-toc__link\">Ograničenja\u003C\u002Fa>\u003C\u002Fli>\u003Cli class=\"editorjs-toc__item\">\u003Ca href=\"#section-56\" class=\"editorjs-toc__link\">Zaključak\u003C\u002Fa>\u003C\u002Fli>\u003Cli class=\"editorjs-toc__item\">\u003Ca href=\"#section-59\" class=\"editorjs-toc__link\">Česta pitanja\u003C\u002Fa>\u003C\u002Fli>\u003Cli class=\"editorjs-toc__item\">\u003Ca href=\"#section-61\" class=\"editorjs-toc__link\">Rečnik pojmova\u003C\u002Fa>\u003C\u002Fli>\u003Cli class=\"editorjs-toc__item\">\u003Ca href=\"#section-63\" class=\"editorjs-toc__link\">Primarni izvori i dodatna literatura\u003C\u002Fa>\u003C\u002Fli>\u003C\u002Fol>\u003C\u002Fnav>",{"time":212,"blocks":213,"version":794},1790366048324,[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,477,482,511,516,545,550,555,560,565,581,586,591,596,601,606,611,620,625,630,635,640,645,650,655,660,665,670,700,705,730,735,745,754,763,772,781,790],{"id":215,"data":216,"type":220,"tunes":221},"75qcDhG72q",{"title":217,"maxLevel":218,"minLevel":219},"Sadržaj",3,2,"tableOfContents",{},{"id":223,"data":224,"type":226,"tunes":227},"intro",{"text":225},"OpenAI-jev stek za agente značajno se promenio u septembru 2026. Novi Agents API uveo je upravljani Codex harness za trajne cloud agente, dok je stariji Agents SDK prešao u fazu održavanja sa zaokruženim funkcionalnostima. Responses API ostaje interfejs nižeg nivoa za aplikacije koje žele direktne pozive modela ili da same upravljaju petljom agenta. Ovo nisu tri međusobno zamenljiva omotača oko iste stvari: oni postavljaju granicu runtime-a na različita mesta.","paragraph",{},{"id":229,"data":230,"type":234,"tunes":235},"direct",{"body":231,"title":232,"variant":233},"\u003Cstrong>Za novu OpenAI-nativnu agentsku aplikaciju u septembru 2026, počnite sa Agents API-jem, osim ako nemate konkretan razlog da sami kontrolišete veći deo runtime-a.\u003C\u002Fstrong> Koristite Responses API kada vaša aplikacija treba da poseduje petlju, strategiju stanja i orkestraciju. Zadržite Agents SDK za postojeće aplikacije ili kratkoročne nedostatke gde Agents API još uvek ne podržava potrebnu mogućnost. Ako želite sam Codex harness, ali morate da ga pokrećete na infrastrukturi kojom sami upravljate, procenite Codex SDK umesto da forsirate Agents SDK u toj ulozi.","Direktan odgovor","info","callout",{},{"id":237,"data":238,"type":234,"tunes":242},"date-warning",{"body":239,"title":240,"variant":241},"Ovaj članak odražava stanje platforme OpenAI na dan \u003Cstrong>25. septembra 2026\u003C\u002Fstrong>. Agents API je lansiran u javnoj beta verziji 10. septembra 2026. Beta interfejsi, pokrivenost funkcijama, cene i uputstva za migraciju mogu se promeniti; proverite aktuelnu dokumentaciju pre nego što donesete konačne odluke o produkcionoj arhitekturi.","Vremenski osetljiva arhitektonska odluka","warning",{},{"id":244,"data":245,"type":234,"tunes":249},"model-note",{"body":246,"title":247,"variant":248},"Test vlasništva nad runtime-om u nastavku predstavlja praktičan arhitektonski model, a ne OpenAI taksonomiju proizvoda. On postavlja pitanje koje delove runtime-a agenta vaš tim mora da kontroliše, a kojim delovima želite da upravlja OpenAI.","Model odlučivanja koji se ovde koristi","note",{},{"id":251,"data":252,"type":42,"tunes":254},"h-boundary",{"text":253,"level":219},"Arhitektura se promenila: izaberite granicu runtime-a, a ne biblioteku",{},{"id":256,"data":257,"type":226,"tunes":259},"p-boundary-1",{"text":258},"Važna odluka više nije jednostavno „Koji SDK treba da instaliram?” Reč je o tome ko kontroliše harness, petlju agenta, trajno stanje sesije, sažimanje konteksta, oporavak, izvršno okruženje i životni ciklus aplikacije.",{},{"id":261,"data":262,"type":226,"tunes":264},"p-boundary-2",{"text":263},"OpenAI-jev trenutni pregled za Agents jasno definiše ovu granicu. Agents API pokreće hostovani Codex harness i upravlja orkestracijom, kao i trajnim stanjem sesije. Responses API pruža odgovore modela i hostovane mogućnosti, dok vaša aplikacija upravlja okolnom petljom agenta. Agents SDK pokreće petlju u vašoj aplikaciji i sada je zaokružen po pitanju funkcionalnosti, te više ne predstavlja pravac za razvoj novih velikih mogućnosti za agente.",{},{"id":266,"data":267,"type":42,"tunes":269},"h-short",{"text":268,"level":219},"Kratko poređenje",{},{"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],"Opcija","Najbolji izbor u 2026.","Ko poseduje petlju agenta?","Odgovornost za sesiju \u002F kontekst","Strateški status",[281,282,283,284,285],"Agents API","Novi OpenAI-nativni trajni agenti","Codex harness kojim upravlja OpenAI","OpenAI upravlja sesijama, orkestracijom, sažimanjem i oporavkom","Preporučena polazna tačka za nove agentske aplikacije; javna beta",[287,288,289,290,291],"Responses API","Direktne integracije modela i prilagođeni runtime-ovi za agente","Vaša aplikacija","Sami birate ulančavanje odgovora, Conversations, skladište i logiku petlje","Osnovni API primitiv; preporučuje se umesto Chat Completions za nove projekte",[293,294,295,296,297],"Agents SDK","Postojeće SDK aplikacije ili privremeni nedostaci u mogućnostima","Vaša aplikacija putem SDK pokretača","Vaša aplikacija upravlja raspoređivanjem, skladištem i ponašanjem runtime-a","Zaokružen sa funkcijama; održavanje i kompatibilnost se nastavljaju, nove velike funkcije nisu planirane",[299,300,301,302,303],"Codex SDK","Codex harness u infrastrukturi kojom sami upravljate","Codex harness u vašem okruženju","Sami upravljate hostovanjem harness-a i životnim ciklusom","Zasebna opcija kada želite harness bez hostovanog Agents API runtime-a","table",{},{"id":307,"data":308,"type":42,"tunes":310},"h-agents-api",{"text":309,"level":219},"1. Agents API: upravljani harness, trajni cloud agent",{},{"id":312,"data":313,"type":226,"tunes":315},"p-api-1",{"text":314},"Agents API izlaže Codex harness kroz servis kojim upravlja OpenAI. OpenAI upravlja sesijama, orkestracijom, sažimanjem konteksta i oporavkom. Vaša aplikacija i dalje obezbeđuje alate i bira izvršno okruženje.",{},{"id":317,"data":318,"type":226,"tunes":320},"p-api-2",{"text":319},"Ta poslednja razlika je važna. „Upravljani agent” ne znači nužno da se „svo računanje odvija unutar OpenAI-ja”. Arhitektura Agents API-ja podržava rad bez okruženja, okruženje koje hostuje OpenAI, ili okruženje na sopstvenom hostingu povezano sa hostovanim harness-om. Sa okruženjem na sopstvenom hostingu, vaša aplikacija upravlja provizionisanjem, ponovnim povezivanjem, gašenjem i trajnim datotekama, dok harness ostaje pod upravljanjem OpenAI-ja.",{},{"id":322,"data":323,"type":226,"tunes":325},"p-api-3",{"text":324},"Agents API je stoga runtime servis, a ne samo format zahteva. Sesije mogu biti trajne, strimovati napredak, primati dodatne zadatke, koristiti alate, raditi sa datotekama i oporavljati se tokom dugotrajnog rada.",{},{"id":327,"data":328,"type":42,"tunes":330},"h-api-gain",{"text":329,"level":218},"Šta dobijate uz Agents API",{},{"id":332,"data":333,"type":343,"tunes":344},"api-gains",{"meta":334,"items":335,"style":342},{},[336,337,338,339,340,341],"Upravljani Codex harness umesto da sami gradite i upravljate glavnom petljom agenta.","Trajne sesije za rad koji obuhvata više koraka i dugotrajne zadatke.","Upravljanu orkestraciju, sažimanje konteksta i oporavak.","Izvršna okruženja koja hostuje OpenAI ili okruženja na sopstvenom hostingu, u zavisnosti od zahteva radnog opterećenja.","Strimovanje i veb-hukove za praćenje napretka i događaja životnog ciklusa.","Strateški pravac platforme koji OpenAI izričito preporučuje za nove agentske aplikacije.","unordered","list",{},{"id":346,"data":347,"type":42,"tunes":349},"h-api-own",{"text":348,"level":218},"Šta i dalje ostaje pod vašom kontrolom",{},{"id":351,"data":352,"type":343,"tunes":360},"api-own",{"meta":353,"items":354,"style":342},{},[355,356,357,358,359],"Vaš proizvod i aplikativni server.","Implementacije funkcija-alata i poslovna logika.","Odluke o autorizaciji i polisama koje se odnose na vaše sopstvene sisteme.","Životni ciklus izvršnog okruženja kada se odlučite za računarske resurse na sopstvenom hostingu.","Evaluacija, kriterijumi prihvatanja, specifični zaštitni mehanizmi za domen i odluka o tome šta je agentu dozvoljeno da radi.",{},{"id":362,"data":363,"type":42,"tunes":365},"h-responses",{"text":364,"level":219},"2. Responses API: upravljajte petljom, koristite primitive platforme",{},{"id":367,"data":368,"type":226,"tunes":370},"p-resp-1",{"text":369},"Responses API je izbor nižeg nivoa kada želite mogućnosti OpenAI modela i alata bez delegiranja celokupnog radnog okruženja (runtime) agenta. OpenAI opisuje Responses kao preporučeni API primitiv za nove projekte i kao evoluciju Chat Completions-a sa ugrađenim alatima, opcijama stanja kroz više krugova razgovora, multimodalnim unosom i agentskim korišćenjem alata.",{},{"id":372,"data":373,"type":226,"tunes":375},"p-resp-2",{"text":374},"Sam Responses zahtev može pozivati alate, ali vaša aplikacija ostaje odgovorna za širi radni tok kada gradite agenta oko njega. To znači da vaš kod odlučuje o tome kako perzistirati stanje aplikacije, kada nastaviti, kako se oporaviti od grešaka, kako koordinisati specijaliste, kako sažeti dugu istoriju i kako predstaviti rad koji se može nastaviti.",{},{"id":377,"data":378,"type":226,"tunes":380},"p-resp-3",{"text":379},"Ovo nije suštinski lošije rešenje. To je prava granica kada ponašanje agenta mora biti duboko integrisano u postojeću logiku aplikacije, kada vam je potreban prilagođeni model stanja ili kada bi upravljani okvir (managed harness) sakrio kontrolu koja vam je zapravo potrebna.",{},{"id":382,"data":383,"type":42,"tunes":385},"h-sdk",{"text":384,"level":219},"3. Agents SDK: podržan, ali više nije podrazumevani put za budući razvoj",{},{"id":387,"data":388,"type":226,"tunes":390},"p-sdk-1",{"text":389},"Agents SDK ostaje radni okvir otvorenog koda za pokretanje radnih tokova agenata u vašoj aplikaciji. Pruža definicije agenata, alate, primopredaje (handoffs), zaštitne ograde (guardrails), praćenje (tracing), sesije i petlju izvršavanja u TypeScript-u i Python-u.",{},{"id":392,"data":393,"type":226,"tunes":395},"p-sdk-2",{"text":394},"Ali njegov strateški status se promenio. OpenAI sada označava Agents SDK kao funkcionalno završen (feature complete): održavanje, bezbednosne ispravke, kritične ispravke grešaka i rad na kompatibilnosti se nastavljaju, ali nove veće funkcionalnosti nisu planirane. OpenAI preporučuje Agents API za nove aplikacije.",{},{"id":397,"data":398,"type":226,"tunes":400},"p-sdk-3",{"text":399},"To ne znači da postojeću SDK aplikaciju treba odmah ponovo napisati. To znači da arhitektura treba da prestane da pretpostavlja da je SDK mesto na koje će stići sledeće velike mogućnosti radnog okruženja za agente.",{},{"id":402,"data":403,"type":234,"tunes":406},"sdk-warning",{"body":404,"title":405,"variant":241},"OpenAI nije opisao Agents SDK kao nepodržan. Postojeće aplikacije mogu nastaviti da ga koriste, a održavanje, bezbednost, kritične ispravke grešaka i rad na kompatibilnosti se nastavljaju. Važna promena je to što nove veće funkcionalnosti nisu planirane i nove aplikacije se usmeravaju na Agents API.","Nemojte prevoditi „feature complete” kao „zastarelo” (deprecated)",{},{"id":408,"data":409,"type":42,"tunes":411},"h-codex-sdk",{"text":410,"level":219},"Gde se uklapa Codex SDK",{},{"id":413,"data":414,"type":226,"tunes":416},"p-codex-1",{"text":415},"Trenutni izbor nije jednostavno trostruko grananje. OpenAI-jev pregled radnih okruženja uključuje Codex SDK kao opciju za pokretanje Codex okvira u infrastrukturi kojom sami upravljate. To se arhitektonski razlikuje i od hostovanog Agents API-ja i od Agents SDK-a.",{},{"id":418,"data":419,"type":226,"tunes":421},"p-codex-2",{"text":420},"Ako je vaš stvarni zahtev „Želim Codex okvir, ali moram sam njime da upravljam”, Codex SDK je rešenje koje treba proceniti. Ako je vaš zahtev „Želim da upravljam petljom oko poziva modela”, procenite Responses. Ako je vaš zahtev „Već imam funkcionalnu Agents SDK aplikaciju”, postojeći SDK može ostati validan dok pravite planove u skladu sa njegovim statusom održavanja.",{},{"id":423,"data":424,"type":42,"tunes":426},"h-test",{"text":425,"level":219},"Test vlasništva nad radnim okruženjem",{},{"id":428,"data":429,"type":226,"tunes":431},"p-test-intro",{"text":430},"Korisna arhitektonska odluka počinje definisanjem onoga što vaš tim mora da poseduje. Ocenite svaki zahtev kao: mora kontrolisati, poželjno kontrolisati ili poželjno upravljano.",{},{"id":433,"data":434,"type":475,"tunes":476},"ownership-test",{"rows":435,"title":425,"layout":304,"columns":465},[436,441,445,449,453,457,461],{"id":437,"label":438,"values":439},"loop","Petlja agenta",[440,440,440],"",{"id":442,"label":443,"values":444},"session","Trajne sesije",[440,440,440],{"id":446,"label":447,"values":448},"harness","Harness radno okruženje",[440,440,440],{"id":450,"label":451,"values":452},"environment","Okruženje za izvršavanje",[440,440,440],{"id":454,"label":455,"values":456},"orchestration","Semantika orkestracije",[440,440,440],{"id":458,"label":459,"values":460},"portability","Fleksibilnost provajdera \u002F transporta",[440,440,440],{"id":462,"label":463,"values":464},"ops","Operativno opterećenje",[440,440,440],[466,469,472],{"id":467,"label":468},"decision","Odluka",{"id":470,"label":471},"managed","Ako preferirate upravljano",{"id":473,"label":474},"control","Ako zahtevate kontrolu","comparison",{},{"id":478,"data":479,"type":42,"tunes":481},"h-tree",{"text":480,"level":219},"Stablo odlučivanja za nove sisteme",{},{"id":483,"data":484,"type":509,"tunes":510},"decision-flow",{"steps":485,"title":507,"orientation":508},[486,489,492,495,498,501,504],{"label":487,"description":488},"1. Da li je ovo nova aplikacija sa agentima?","Ako nije, nemojte migrirati samo zato što postoji novije rešenje. Najpre procenite stvarna ograničenja trenutne aplikacije.",{"label":490,"description":491},"2. Da li želite upravljani okvir za dugotrajne agente?","Ako želite, počnite sa Agents API-jem kao preporučenim pravcem kompanije OpenAI za nove aplikacije sa agentima.",{"label":493,"description":494},"3. Da li vam je potreban Codex okvir, ali morate sami njime da upravljate?","Procenite Codex SDK umesto ponovne izgradnje ponašanja okvira na bazi Agents SDK-a.",{"label":496,"description":497},"4. Da li je potrebno da posedujete sopstvenu petlju agenta i model stanja?","Koristite Responses API kao platformski primitiv nižeg nivoa i izgradite petlju oko njega.",{"label":499,"description":500},"5. Da li već koristite Agents SDK?","Nastavite ukoliko ispunjava zahteve; nove veće funkcionalnosti nisu planirane, pa buduće usvajanje platforme tretirajte kao eksplicitnu odluku u mapi razvoja.",{"label":502,"description":503},"6. Da li u Agents API-ju nedostaje potrebna mogućnost?","OpenAI izričito dozvoljava Agents SDK kao kratkoročnu opciju za nove aplikacije kojima su potrebne nepodržane mogućnosti.",{"label":505,"description":506},"7. Validacija kroz probni prototip u produkcijskim uslovima","Testirajte alate, okruženje, odobrenja, kašnjenje, opservabilnost, oporavak od grešaka i životni ciklus pre konačnog zaključavanja arhitekture.","Izaberite radno okruženje prema granici kontrole","auto","processFlow",{},{"id":512,"data":513,"type":42,"tunes":515},"h-not-drive",{"text":514,"level":219},"Šta ne bi trebalo da vodi donošenje odluke",{},{"id":517,"data":518,"type":304,"tunes":544},"weak-rules",{"content":519,"stretched":43,"withHeadings":14},[520,524,528,532,536,540],[521,522,523],"Slabo pravilo odlučivanja","Zašto ne uspeva","Bolje pitanje",[525,526,527],"„Najnoviji API mora biti najbolji.”","Novije rešenje može biti strateški poželjnije, a da mu i dalje nedostaje funkcionalnost koja vam je potrebna.","Koje odgovornosti izvršnog okruženja treba da budu upravljane, a koje u vlasništvu aplikacije?",[529,530,531],"„Već poznajemo SDK.”","Poznavanje alata u timu može sačuvati arhitekturu čiji se plan razvoja promenio.","Koliki je trošak ostanka u poređenju sa prelaskom tokom sledećeg ciklusa proizvoda?",[533,534,535],"„Upravljano znači bez infrastrukture.”","Agents API i dalje može koristiti samostalno hostovana okruženja, a vaša aplikacija i dalje zadržava logiku proizvoda.","Koji infrastrukturni sloj se zapravo delegira?",[537,538,539],"„Responses služi samo za jednostavne pozive.”","Responses pruža ugrađene alate i primitive stanja; može biti osnova za prilagođene petlje agenata.","Da li nam je potrebno da platforma upravlja okvirom, ili samo primitivima modela\u002Falata?",[541,542,543],"„Završetak razvoja novih funkcija znači da moramo odmah da migriramo.”","SDK ostaje održavan za postojeće aplikacije.","Koji konkretan budući zahtev je blokiran ostankom?",{},{"id":546,"data":547,"type":42,"tunes":549},"h-migration",{"text":548,"level":219},"Migracija je arhitektonska promena, a ne preimenovanje uvoza",{},{"id":551,"data":552,"type":226,"tunes":554},"p-migration-1",{"text":553},"Prelazak sa Agents SDK na Agents API menja vlasništvo. U SDK-u, petlja se izvršava u vašoj aplikaciji. U Agents API-ju, OpenAI upravlja okvirom i sesijom, dok se vaša aplikacija integriše putem zadataka, događaja, alata i granica okruženja.",{},{"id":556,"data":557,"type":226,"tunes":559},"p-migration-2",{"text":558},"Pravi plan migracije stoga mora da mapira stanje sesije, prilagođenu orkestraciju, prenošenje zadataka, izvršavanje alata, odobrenja, skladištenje, praćenje, ponovne pokušaje, oporavak od grešaka, životni ciklus okruženja i sve apstrakcije specifične za provajdera. Obim koda može se smanjiti dok se operativne pretpostavke menjaju.",{},{"id":561,"data":562,"type":42,"tunes":564},"h-migration-inventory",{"text":563,"level":218},"Popis elemenata za migraciju",{},{"id":566,"data":567,"type":343,"tunes":580},"migration-list",{"meta":568,"items":569,"style":342},{},[570,571,572,573,574,575,576,577,578,579],"Definicije agenata i vlasništvo nad instrukcijama.","Definicije alata i lokacija gde se svaki alat izvršava.","Prenošenje zadataka, obrasci menadžera\u002Fspecijaliste i ponašanje podagenata.","Identifikatori sesije, stanje razgovora, mogućnost nastavka i zadržavanje istorije.","Ljudska odobrenja i semantika prekida.","Prilagođena logika za skraćivanje ili zbijanje konteksta.","Praćenje, evaluacije, opservabilnost i otklanjanje grešaka u produkciji.","Samostalno hostovane datoteke, kontejneri, pristup privatnoj mreži ili druge zavisnosti izvršavanja.","Apstrakcija provajdera ili zavisnosti od modela koji nisu OpenAI.","Pretpostavke o ponovnim pokušajima, vremenskom isteku, idempotentnosti, oporavku i životnom ciklusu.",{},{"id":582,"data":583,"type":42,"tunes":585},"h-beta",{"text":584,"level":219},"Javna beta menja model rizika",{},{"id":587,"data":588,"type":226,"tunes":590},"p-beta-1",{"text":589},"Agents API je preporučeni smer za nove agentske aplikacije, ali je takođe u javnoj beta verziji. Te činjenice nisu u suprotnosti. Strateški smer odgovara na pitanje „kuda platforma ide?”, dok beta status odgovara na pitanje „koliko promena interfejsa i operativnih promena treba planirati u budžetu?”",{},{"id":592,"data":593,"type":226,"tunes":595},"p-beta-2",{"text":594},"Za produkcione sisteme, izolujte integraciju iza granice aplikacije. Držite stanje domena, dozvole, revizorske podatke i poslovna pravila van objekata sesije specifičnih za dobavljača gde god je to moguće. Ovo olakšava prilagođavanje evoluciji API-ja bez pretvaranja izvršnog okruženja agenta u izvor istine za ceo vaš proizvod.",{},{"id":597,"data":598,"type":42,"tunes":600},"h-default",{"text":599,"level":219},"Praktična podrazumevana arhitektura",{},{"id":602,"data":603,"type":226,"tunes":605},"p-default-1",{"text":604},"Za mnoge nove izvorne OpenAI aplikacije, razuman podrazumevani izbor za 2026. godinu jeste: Agents API za upravljani okvir i trajnu sesiju, domenski servisi i autorizacija u vlasništvu aplikacije, eksplicitni alati funkcija za poslovne akcije, i izvršavanje hostovano od strane OpenAI-ja ili samostalno, u zavisnosti od zahteva za podacima i računarskim resursima.",{},{"id":607,"data":608,"type":226,"tunes":610},"p-default-2",{"text":609},"To održava izvršno okruženje agenta moćnim, a da ono ne postane vlasnik poslovne istine. Aplikacija i dalje odlučuje šta korisnik sme da uradi, koji su podaci merodavni, koje akcije zahtevaju odobrenje i kako se rezultati validiraju.",{},{"id":612,"data":613,"type":618,"tunes":619},"ref-reliability",{"url":614,"title":615,"excerpt":616,"ctaLabel":617},"https:\u002F\u002Fstajic.de\u002Fsr\u002Fblog\u002Fai-agent-reliability-why-the-final-answer-is-not-enough","Pouzdanost AI agenata: Zašto konačni odgovor nije dovoljan","Upravljani okvir smanjuje operativno opterećenje, ali pouzdanost i dalje zahteva sledljivo izvršavanje, eksplicitne kriterijume prihvatljivosti i evaluaciju koja prevazilazi konačni odgovor.","Pročitajte članak o pouzdanosti","referralArticle",{},{"id":621,"data":622,"type":42,"tunes":624},"h-change",{"text":623,"level":219},"Šta bi promenilo ovaj odgovor?",{},{"id":626,"data":627,"type":226,"tunes":629},"p-change-1",{"text":628},"Preporuka se menja ako Agents API doda ili ukloni mogućnosti, izađe iz beta verzije sa drugačijim ugovorima, promeni granice okruženja ili cene, ili uvede alate za migraciju koji smanjuju razlike u vlasništvu. Takođe se menja ako vaša aplikacija zavisi od prenosivosti među provajderima, prilagođene semantike orkestracije, isključivo lokalnog izvršavanja ili mogućnosti koju hostovani okvir ne može da podrži.",{},{"id":631,"data":632,"type":226,"tunes":634},"p-change-2",{"text":633},"Za postojeću aplikaciju zasnovanu na Agents SDK-u, odgovor se takođe menja sa troškovima migracije. Ako je sistem stabilan, dobro evaluiran i nije blokiran statusom SDK-a koji označava završetak razvoja novih funkcija, trenutna migracija može stvoriti više rizika nego vrednosti. Ako plan razvoja proizvoda zavisi od mogućnosti koje dolaze isključivo u Agents API, odlaganje migracije može stvoriti drugačiju vrstu tehničkog duga.",{},{"id":636,"data":637,"type":42,"tunes":639},"h-limitations",{"text":638,"level":219},"Ograničenja",{},{"id":641,"data":642,"type":226,"tunes":644},"p-limit-1",{"text":643},"Ovo poređenje se fokusira na vlasništvo nad izvršnim okruženjem i navedeni pravac platforme kompanije OpenAI. Ono ne meri kašnjenje, kvalitet ili ukupne troškove za specifično radno opterećenje. Ta svojstva zavise od izbora modela, korišćenja alata, okruženja, dužine zadatka, keširanja, upotrebe sandbox okruženja i arhitekture aplikacije.",{},{"id":646,"data":647,"type":226,"tunes":649},"p-limit-2",{"text":648},"Agents API je takođe dovoljno nov da se produkciono iskustvo još uvek prikuplja. Zbog toga bi dizajn trebalo validirati reprezentativnim radnim opterećenjima, a ne birati ga isključivo na osnovu pozicioniranja proizvoda.",{},{"id":651,"data":652,"type":42,"tunes":654},"h-conclusion",{"text":653,"level":219},"Zaključak",{},{"id":656,"data":657,"type":226,"tunes":659},"p-conclusion-1",{"text":658},"Odluka o OpenAI agentima za 2026. godinu u osnovi se svodi na vlasništvo nad runtime-om. Agents API znači da OpenAI poseduje veći deo harness-a i mehanizama za trajne sesije. Responses znači da vaša aplikacija poseduje petlju oko primitivnih elemenata platforme. Agents SDK ostaje validan za postojeće sisteme, ali više nije podrazumevano odredište za važne nove funkcije agent runtime-a.",{},{"id":661,"data":662,"type":226,"tunes":664},"p-conclusion-2",{"text":663},"Za novu aplikaciju, pratite smer platforme osim ako vas stvarni zahtev ne natera da se spustite niže u steku. Počnite sa Agents API-jem, pređite na Responses kada vam je potrebno da sami kontrolišete petlju, razmotrite Codex SDK kada vam je potreban harness u sopstvenoj infrastrukturi, i zadržite Agents SDK tamo gde to opravdavaju postojeća ulaganja ili privremeni nedostaci u mogućnostima.",{},{"id":666,"data":667,"type":42,"tunes":669},"h-faq",{"text":668,"level":219},"Česta pitanja",{},{"id":671,"data":672,"type":671,"tunes":699},"faq",{"items":673,"title":698},[674,678,682,686,690,694],{"id":675,"answer":676,"question":677},"faq1","OpenAI trenutno preporučuje Agents API za nove aplikacije sa agentima. Agents SDK je funkcionalno završen i ostaje podržan za postojeće aplikacije, uz nastavak održavanja, bezbednosnih ispravki, kritičnih popravki grešaka i rada na kompatibilnosti.","Da li bi trebalo da koristim OpenAI Agents API ili Agents SDK za novi projekat?",{"id":679,"answer":680,"question":681},"faq2","OpenAI ga opisuje kao funkcionalno završenog, a ne kao nepodržanog. Velike nove funkcionalnosti nisu planirane, ali se održavanje, bezbednosne ispravke, kritične ispravke grešaka i rad na kompatibilnosti nastavljaju.","Da li je Agents SDK zastareo?",{"id":683,"answer":684,"question":685},"faq3","Koristite Responses kada vaša aplikacija treba da upravlja petljom agenta, strategijom stanja, orkestracijom i logikom nastavka, dok i dalje koristi OpenAI modele i alate platforme.","Kada bi trebalo da koristim Responses API umesto Agents API-ja?",{"id":687,"answer":688,"question":689},"faq4","Ne. Agents API može funkcionisati bez izvršnog okruženja, u okruženju koje hostuje OpenAI, ili u samostalno hostovanom okruženju povezanom sa upravljanim harness-om.","Da li Agents API zahteva računarske resurse koje hostuje OpenAI?",{"id":691,"answer":692,"question":693},"faq5","OpenAI pozicionira Codex SDK za pokretanje Codex harness-a na infrastrukturi kojom sami upravljate. To je relevantna opcija kada želite harness, ali ne i hostovani Agents API runtime.","Gde se uklapa Codex SDK?",{"id":695,"answer":696,"question":697},"faq6","Ne automatski. Procenite da li je trenutni sistem blokiran statusom SDK-a kao funkcionalno završenog, da li potrebne mogućnosti postoje u Agents API-ju i da li korist od migracije nadmašuje operativne i arhitektonske promene.","Da li bi postojeća Agents SDK aplikacija trebalo odmah da migrira?","Izbori za OpenAI agent runtime u 2026. godini",{},{"id":701,"data":702,"type":42,"tunes":704},"h-glossary",{"text":703,"level":219},"Rečnik pojmova",{},{"id":706,"data":707,"type":706,"tunes":729},"glossary",{"title":708,"entries":709},"Ključni runtime pojmovi",[710,713,716,719,722,725],{"term":711,"anchor":446,"definition":712},"Harness","Runtime petlja i prateći mehanizmi koji koordiniraju pozive modela, alate, kontekst, sesije i izvršavanje agenta.",{"term":281,"anchor":714,"definition":715},"agents-api","OpenAI-jev upravljani API za trajne agente u oblaku koji koriste hostovani Codex harness.",{"term":287,"anchor":717,"definition":718},"responses-api","OpenAI-jev API primitiv nižeg nivoa za odgovore modela, hostovane alate i interakcije sa stanjem, oko kojih aplikacije mogu izgraditi sopstvenu petlju agenta.",{"term":293,"anchor":720,"definition":721},"agents-sdk","OpenAI-jev open-source radni okvir za pokretanje tokova rada agenata u kodu aplikacije; funkcionalno završen od septembra 2026.",{"term":299,"anchor":723,"definition":724},"codex-sdk","Runtime opcija koju OpenAI navodi za pokretanje Codex harness-a na infrastrukturi kojom sami upravljate.",{"term":726,"anchor":727,"definition":728},"Runtime ownership","runtime-ownership","Arhitektonska granica koja opisuje kojim delovima petlje agenta, stanja sesije, izvršnog okruženja i životnog ciklusa upravlja platforma, a kojim aplikacija.",{},{"id":731,"data":732,"type":42,"tunes":734},"h-sources",{"text":733,"level":219},"Primarni izvori i dodatna literatura",{},{"id":736,"data":737,"type":743,"tunes":744},"src-launch",{"link":738,"meta":739},"https:\u002F\u002Fopenai.com\u002Findex\u002Fintroducing-the-agents-api\u002F",{"image":740,"title":741,"description":742},{"url":440},"OpenAI — Predstavljanje Agents API-ja","Najava lansiranja Agents API-ja od 10. septembra 2026. godine, koja opisuje upravljani Codex harness i javnu beta verziju.","linkTool",{},{"id":746,"data":747,"type":743,"tunes":753},"src-agents-overview",{"link":748,"meta":749},"https:\u002F\u002Fdevelopers.openai.com\u002Fapi\u002Fdocs\u002Fguides\u002Fagents",{"image":750,"title":751,"description":752},{"url":440},"OpenAI — Pregled agent runtime-a","Trenutno poređenje Agents API-ja, Codex SDK-a i Responses API-ja, uključujući status podrške za Agents SDK.",{},{"id":755,"data":756,"type":743,"tunes":762},"src-agents-api",{"link":757,"meta":758},"https:\u002F\u002Fdevelopers.openai.com\u002Fapi\u002Fdocs\u002Fguides\u002Fagents-api\u002Foverview",{"image":759,"title":760,"description":761},{"url":440},"OpenAI — Pregled Agents API-ja","Dokumentacija za trajne agente u oblaku, sesije, orkestraciju, sažimanje konteksta, oporavak i izbor okruženja.",{},{"id":764,"data":765,"type":743,"tunes":771},"src-architecture",{"link":766,"meta":767},"https:\u002F\u002Fdevelopers.openai.com\u002Fapi\u002Fdocs\u002Fguides\u002Fagents-api\u002Farchitecture",{"image":768,"title":769,"description":770},{"url":440},"OpenAI — Arhitektura Agents API-ja","Arhitektonska granica između hostovanog harness-a, aplikativnog servera i izvršnih okruženja bez okruženja, hostovanih od strane OpenAI-ja ili samostalno hostovanih.",{},{"id":773,"data":774,"type":743,"tunes":780},"src-sdk",{"link":775,"meta":776},"https:\u002F\u002Fdevelopers.openai.com\u002Fapi\u002Fdocs\u002Fguides\u002Fagents\u002Fsdk",{"image":777,"title":778,"description":779},{"url":440},"OpenAI — Agents SDK","Trenutno obaveštenje o podršci za Agents SDK i objašnjenje petlje agenta u vlasništvu aplikacije.",{},{"id":782,"data":783,"type":743,"tunes":789},"src-responses",{"link":784,"meta":785},"https:\u002F\u002Fdevelopers.openai.com\u002Fapi\u002Fdocs\u002Fguides\u002Fmigrate-to-responses",{"image":786,"title":787,"description":788},{"url":440},"OpenAI — Migracija na Responses API","Trenutno pozicioniranje Responses API-ja, ugrađeni alati, kontekst sa stanjem i agentski primitivi.",{},{"id":791,"data":792,"type":220,"tunes":793},"toc",{"title":217,"maxLevel":218,"minLevel":219},{},"2.31","OpenAI-jev stek agenata promenio se u septembru 2026. Ovaj arhitekturni vodič razdvaja Agents API, Agents SDK, Responses API i Codex SDK prema vlasništvu nad izvršnim okruženjem—kako bi timovi mogli da izaberu pravu granicu kontrole umesto da porede nazive proizvoda.","\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":803,"de":804,"sr":805,"es":806,"fr":807,"it":808,"ru":809,"zh":810},"\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",[812,815,819],{"id":101,"name":813,"slug":814},"Overview","overview-digital-platform",{"id":816,"name":817,"slug":818},48,"Sposobnosti","capabilities",{"id":820,"name":821,"slug":822},46,"Pregled","overview",{"id":824,"login":825,"email":826,"displayName":827},"20","rooth8233","aleksandar@stajic.de","Aleksandar Stajić",[829,1298],{"lang":830,"title":831,"content":832,"contentJson":833,"excerpt":1297},"en","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":834,"blocks":835,"version":1296},1790352010644,[836,840,844,849,854,859,863,867,871,875,905,909,913,917,921,925,936,940,950,954,958,962,966,970,974,978,982,987,991,995,999,1003,1007,1040,1044,1070,1074,1102,1106,1110,1114,1118,1133,1137,1141,1145,1149,1153,1157,1164,1168,1172,1176,1180,1184,1188,1192,1196,1200,1204,1227,1231,1248,1252,1259,1266,1273,1280,1286,1293],{"id":215,"data":837,"type":220,"tunes":839},{"title":838,"maxLevel":218,"minLevel":219},"Contents",{},{"id":223,"data":841,"type":226,"tunes":843},{"text":842},"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.",{},{"id":229,"data":845,"type":234,"tunes":848},{"body":846,"title":847,"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",{},{"id":237,"data":850,"type":234,"tunes":853},{"body":851,"title":852,"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",{},{"id":244,"data":855,"type":234,"tunes":858},{"body":856,"title":857,"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",{},{"id":251,"data":860,"type":42,"tunes":862},{"text":861,"level":219},"The architecture changed: choose a runtime boundary, not a library",{},{"id":256,"data":864,"type":226,"tunes":866},{"text":865},"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":868,"type":226,"tunes":870},{"text":869},"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":872,"type":42,"tunes":874},{"text":873,"level":219},"The short comparison",{},{"id":271,"data":876,"type":304,"tunes":904},{"content":877,"stretched":43,"withHeadings":14},[878,884,889,894,899],[879,880,881,882,883],"Option","Best fit in 2026","Who owns the agent loop?","Session \u002F context responsibility","Strategic status",[281,885,886,887,888],"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,890,891,892,893],"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,895,896,897,898],"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,900,901,902,903],"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",{},{"id":307,"data":906,"type":42,"tunes":908},{"text":907,"level":219},"1. Agents API: managed harness, durable cloud agent",{},{"id":312,"data":910,"type":226,"tunes":912},{"text":911},"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":914,"type":226,"tunes":916},{"text":915},"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":918,"type":226,"tunes":920},{"text":919},"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":922,"type":42,"tunes":924},{"text":923,"level":218},"What you gain with the Agents API",{},{"id":332,"data":926,"type":343,"tunes":935},{"meta":927,"items":928,"style":342},{},[929,930,931,932,933,934],"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.",{},{"id":346,"data":937,"type":42,"tunes":939},{"text":938,"level":218},"What you still own",{},{"id":351,"data":941,"type":343,"tunes":949},{"meta":942,"items":943,"style":342},{},[944,945,946,947,948],"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":951,"type":42,"tunes":953},{"text":952,"level":219},"2. Responses API: own the loop, use the platform primitives",{},{"id":367,"data":955,"type":226,"tunes":957},{"text":956},"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":959,"type":226,"tunes":961},{"text":960},"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":963,"type":226,"tunes":965},{"text":964},"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":967,"type":42,"tunes":969},{"text":968,"level":219},"3. Agents SDK: supported, but no longer the default forward path",{},{"id":387,"data":971,"type":226,"tunes":973},{"text":972},"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":975,"type":226,"tunes":977},{"text":976},"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":979,"type":226,"tunes":981},{"text":980},"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":983,"type":234,"tunes":986},{"body":984,"title":985,"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":988,"type":42,"tunes":990},{"text":989,"level":219},"Where the Codex SDK fits",{},{"id":413,"data":992,"type":226,"tunes":994},{"text":993},"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":996,"type":226,"tunes":998},{"text":997},"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":1000,"type":42,"tunes":1002},{"text":1001,"level":219},"The Runtime Ownership Test",{},{"id":428,"data":1004,"type":226,"tunes":1006},{"text":1005},"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":1008,"type":475,"tunes":1039},{"rows":1009,"title":1031,"layout":304,"columns":1032},[1010,1013,1016,1019,1022,1025,1028],{"id":437,"label":1011,"values":1012},"Agent loop",[440,440,440],{"id":442,"label":1014,"values":1015},"Durable sessions",[440,440,440],{"id":446,"label":1017,"values":1018},"Harness runtime",[440,440,440],{"id":450,"label":1020,"values":1021},"Execution environment",[440,440,440],{"id":454,"label":1023,"values":1024},"Orchestration semantics",[440,440,440],{"id":458,"label":1026,"values":1027},"Provider \u002F transport flexibility",[440,440,440],{"id":462,"label":1029,"values":1030},"Operational burden",[440,440,440],"Runtime Ownership Test",[1033,1035,1037],{"id":467,"label":1034},"Decision",{"id":470,"label":1036},"If you prefer managed",{"id":473,"label":1038},"If you require control",{},{"id":478,"data":1041,"type":42,"tunes":1043},{"text":1042,"level":219},"A decision tree for new systems",{},{"id":483,"data":1045,"type":509,"tunes":1069},{"steps":1046,"title":1068,"orientation":508},[1047,1050,1053,1056,1059,1062,1065],{"label":1048,"description":1049},"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":1051,"description":1052},"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":1054,"description":1055},"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":1057,"description":1058},"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":1060,"description":1061},"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":1063,"description":1064},"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":1066,"description":1067},"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",{},{"id":512,"data":1071,"type":42,"tunes":1073},{"text":1072,"level":219},"What should not drive the decision",{},{"id":517,"data":1075,"type":304,"tunes":1101},{"content":1076,"stretched":43,"withHeadings":14},[1077,1081,1085,1089,1093,1097],[1078,1079,1080],"Weak decision rule","Why it fails","Better question",[1082,1083,1084],"“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?",[1086,1087,1088],"“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?",[1090,1091,1092],"“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?",[1094,1095,1096],"“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?",[1098,1099,1100],"“Feature complete means we must migrate now.”","The SDK remains maintained for existing applications.","What concrete future requirement is blocked by staying?",{},{"id":546,"data":1103,"type":42,"tunes":1105},{"text":1104,"level":219},"Migration is an architectural change, not an import rename",{},{"id":551,"data":1107,"type":226,"tunes":1109},{"text":1108},"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":556,"data":1111,"type":226,"tunes":1113},{"text":1112},"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":561,"data":1115,"type":42,"tunes":1117},{"text":1116,"level":218},"The migration inventory",{},{"id":566,"data":1119,"type":343,"tunes":1132},{"meta":1120,"items":1121,"style":342},{},[1122,1123,1124,1125,1126,1127,1128,1129,1130,1131],"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":582,"data":1134,"type":42,"tunes":1136},{"text":1135,"level":219},"Public beta changes the risk model",{},{"id":587,"data":1138,"type":226,"tunes":1140},{"text":1139},"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":592,"data":1142,"type":226,"tunes":1144},{"text":1143},"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":597,"data":1146,"type":42,"tunes":1148},{"text":1147,"level":219},"A practical default architecture",{},{"id":602,"data":1150,"type":226,"tunes":1152},{"text":1151},"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":607,"data":1154,"type":226,"tunes":1156},{"text":1155},"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":612,"data":1158,"type":618,"tunes":1163},{"url":1159,"title":1160,"excerpt":1161,"ctaLabel":1162},"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",{},{"id":621,"data":1165,"type":42,"tunes":1167},{"text":1166,"level":219},"What would change this answer?",{},{"id":626,"data":1169,"type":226,"tunes":1171},{"text":1170},"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":631,"data":1173,"type":226,"tunes":1175},{"text":1174},"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":636,"data":1177,"type":42,"tunes":1179},{"text":1178,"level":219},"Limitations",{},{"id":641,"data":1181,"type":226,"tunes":1183},{"text":1182},"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":646,"data":1185,"type":226,"tunes":1187},{"text":1186},"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":651,"data":1189,"type":42,"tunes":1191},{"text":1190,"level":219},"Conclusion",{},{"id":656,"data":1193,"type":226,"tunes":1195},{"text":1194},"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":661,"data":1197,"type":226,"tunes":1199},{"text":1198},"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":666,"data":1201,"type":42,"tunes":1203},{"text":1202,"level":219},"FAQ",{},{"id":671,"data":1205,"type":671,"tunes":1226},{"items":1206,"title":1225},[1207,1210,1213,1216,1219,1222],{"id":675,"answer":1208,"question":1209},"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":679,"answer":1211,"question":1212},"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":683,"answer":1214,"question":1215},"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":687,"answer":1217,"question":1218},"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":691,"answer":1220,"question":1221},"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":695,"answer":1223,"question":1224},"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":701,"data":1228,"type":42,"tunes":1230},{"text":1229,"level":219},"Glossary",{},{"id":706,"data":1232,"type":706,"tunes":1247},{"title":1233,"entries":1234},"Key runtime terms",[1235,1237,1239,1241,1243,1245],{"term":711,"anchor":446,"definition":1236},"The runtime loop and supporting machinery that coordinates model calls, tools, context, sessions and agent execution.",{"term":281,"anchor":714,"definition":1238},"OpenAI's managed API for durable cloud agents using a hosted Codex harness.",{"term":287,"anchor":717,"definition":1240},"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":720,"definition":1242},"OpenAI's open-source framework for running agent workflows in application code; feature complete as of September 2026.",{"term":299,"anchor":723,"definition":1244},"The runtime option OpenAI lists for running the Codex harness in infrastructure you operate.",{"term":726,"anchor":727,"definition":1246},"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":731,"data":1249,"type":42,"tunes":1251},{"text":1250,"level":219},"Primary sources and further reading",{},{"id":736,"data":1253,"type":743,"tunes":1258},{"link":738,"meta":1254},{"image":1255,"title":1256,"description":1257},{"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.",{},{"id":746,"data":1260,"type":743,"tunes":1265},{"link":748,"meta":1261},{"image":1262,"title":1263,"description":1264},{"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":755,"data":1267,"type":743,"tunes":1272},{"link":757,"meta":1268},{"image":1269,"title":1270,"description":1271},{"url":440},"OpenAI — Agents API overview","Documentation for durable cloud agents, sessions, orchestration, context compaction, recovery and environment choices.",{},{"id":764,"data":1274,"type":743,"tunes":1279},{"link":766,"meta":1275},{"image":1276,"title":1277,"description":1278},{"url":440},"OpenAI — Agents API architecture","Architecture boundary between the hosted harness, application server and no\u002Fopenai-hosted\u002Fself-hosted execution environments.",{},{"id":773,"data":1281,"type":743,"tunes":1285},{"link":775,"meta":1282},{"image":1283,"title":778,"description":1284},{"url":440},"Current Agents SDK support notice and explanation of the application-owned agent loop.",{},{"id":782,"data":1287,"type":743,"tunes":1292},{"link":784,"meta":1288},{"image":1289,"title":1290,"description":1291},{"url":440},"OpenAI — Migrate to the Responses API","Current Responses API positioning, built-in tools, stateful context and agentic primitives.",{},{"id":791,"data":1294,"type":220,"tunes":1295},{"title":838,"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.",{"lang":7,"title":208,"content":210,"contentJson":1299,"excerpt":795},{"time":212,"blocks":1300,"version":794},[1301,1304,1307,1310,1313,1316,1319,1322,1325,1328,1337,1340,1343,1346,1349,1352,1357,1360,1365,1368,1371,1374,1377,1380,1383,1386,1389,1392,1395,1398,1401,1404,1407,1429,1432,1443,1446,1456,1459,1462,1465,1468,1473,1476,1479,1482,1485,1488,1491,1494,1497,1500,1503,1506,1509,1512,1515,1518,1521,1524,1534,1537,1547,1550,1555,1560,1565,1570,1575,1580],{"id":215,"data":1302,"type":220,"tunes":1303},{"title":217,"maxLevel":218,"minLevel":219},{},{"id":223,"data":1305,"type":226,"tunes":1306},{"text":225},{},{"id":229,"data":1308,"type":234,"tunes":1309},{"body":231,"title":232,"variant":233},{},{"id":237,"data":1311,"type":234,"tunes":1312},{"body":239,"title":240,"variant":241},{},{"id":244,"data":1314,"type":234,"tunes":1315},{"body":246,"title":247,"variant":248},{},{"id":251,"data":1317,"type":42,"tunes":1318},{"text":253,"level":219},{},{"id":256,"data":1320,"type":226,"tunes":1321},{"text":258},{},{"id":261,"data":1323,"type":226,"tunes":1324},{"text":263},{},{"id":266,"data":1326,"type":42,"tunes":1327},{"text":268,"level":219},{},{"id":271,"data":1329,"type":304,"tunes":1336},{"content":1330,"stretched":43,"withHeadings":14},[1331,1332,1333,1334,1335],[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":1338,"type":42,"tunes":1339},{"text":309,"level":219},{},{"id":312,"data":1341,"type":226,"tunes":1342},{"text":314},{},{"id":317,"data":1344,"type":226,"tunes":1345},{"text":319},{},{"id":322,"data":1347,"type":226,"tunes":1348},{"text":324},{},{"id":327,"data":1350,"type":42,"tunes":1351},{"text":329,"level":218},{},{"id":332,"data":1353,"type":343,"tunes":1356},{"meta":1354,"items":1355,"style":342},{},[336,337,338,339,340,341],{},{"id":346,"data":1358,"type":42,"tunes":1359},{"text":348,"level":218},{},{"id":351,"data":1361,"type":343,"tunes":1364},{"meta":1362,"items":1363,"style":342},{},[355,356,357,358,359],{},{"id":362,"data":1366,"type":42,"tunes":1367},{"text":364,"level":219},{},{"id":367,"data":1369,"type":226,"tunes":1370},{"text":369},{},{"id":372,"data":1372,"type":226,"tunes":1373},{"text":374},{},{"id":377,"data":1375,"type":226,"tunes":1376},{"text":379},{},{"id":382,"data":1378,"type":42,"tunes":1379},{"text":384,"level":219},{},{"id":387,"data":1381,"type":226,"tunes":1382},{"text":389},{},{"id":392,"data":1384,"type":226,"tunes":1385},{"text":394},{},{"id":397,"data":1387,"type":226,"tunes":1388},{"text":399},{},{"id":402,"data":1390,"type":234,"tunes":1391},{"body":404,"title":405,"variant":241},{},{"id":408,"data":1393,"type":42,"tunes":1394},{"text":410,"level":219},{},{"id":413,"data":1396,"type":226,"tunes":1397},{"text":415},{},{"id":418,"data":1399,"type":226,"tunes":1400},{"text":420},{},{"id":423,"data":1402,"type":42,"tunes":1403},{"text":425,"level":219},{},{"id":428,"data":1405,"type":226,"tunes":1406},{"text":430},{},{"id":433,"data":1408,"type":475,"tunes":1428},{"rows":1409,"title":425,"layout":304,"columns":1424},[1410,1412,1414,1416,1418,1420,1422],{"id":437,"label":438,"values":1411},[440,440,440],{"id":442,"label":443,"values":1413},[440,440,440],{"id":446,"label":447,"values":1415},[440,440,440],{"id":450,"label":451,"values":1417},[440,440,440],{"id":454,"label":455,"values":1419},[440,440,440],{"id":458,"label":459,"values":1421},[440,440,440],{"id":462,"label":463,"values":1423},[440,440,440],[1425,1426,1427],{"id":467,"label":468},{"id":470,"label":471},{"id":473,"label":474},{},{"id":478,"data":1430,"type":42,"tunes":1431},{"text":480,"level":219},{},{"id":483,"data":1433,"type":509,"tunes":1442},{"steps":1434,"title":507,"orientation":508},[1435,1436,1437,1438,1439,1440,1441],{"label":487,"description":488},{"label":490,"description":491},{"label":493,"description":494},{"label":496,"description":497},{"label":499,"description":500},{"label":502,"description":503},{"label":505,"description":506},{},{"id":512,"data":1444,"type":42,"tunes":1445},{"text":514,"level":219},{},{"id":517,"data":1447,"type":304,"tunes":1455},{"content":1448,"stretched":43,"withHeadings":14},[1449,1450,1451,1452,1453,1454],[521,522,523],[525,526,527],[529,530,531],[533,534,535],[537,538,539],[541,542,543],{},{"id":546,"data":1457,"type":42,"tunes":1458},{"text":548,"level":219},{},{"id":551,"data":1460,"type":226,"tunes":1461},{"text":553},{},{"id":556,"data":1463,"type":226,"tunes":1464},{"text":558},{},{"id":561,"data":1466,"type":42,"tunes":1467},{"text":563,"level":218},{},{"id":566,"data":1469,"type":343,"tunes":1472},{"meta":1470,"items":1471,"style":342},{},[570,571,572,573,574,575,576,577,578,579],{},{"id":582,"data":1474,"type":42,"tunes":1475},{"text":584,"level":219},{},{"id":587,"data":1477,"type":226,"tunes":1478},{"text":589},{},{"id":592,"data":1480,"type":226,"tunes":1481},{"text":594},{},{"id":597,"data":1483,"type":42,"tunes":1484},{"text":599,"level":219},{},{"id":602,"data":1486,"type":226,"tunes":1487},{"text":604},{},{"id":607,"data":1489,"type":226,"tunes":1490},{"text":609},{},{"id":612,"data":1492,"type":618,"tunes":1493},{"url":614,"title":615,"excerpt":616,"ctaLabel":617},{},{"id":621,"data":1495,"type":42,"tunes":1496},{"text":623,"level":219},{},{"id":626,"data":1498,"type":226,"tunes":1499},{"text":628},{},{"id":631,"data":1501,"type":226,"tunes":1502},{"text":633},{},{"id":636,"data":1504,"type":42,"tunes":1505},{"text":638,"level":219},{},{"id":641,"data":1507,"type":226,"tunes":1508},{"text":643},{},{"id":646,"data":1510,"type":226,"tunes":1511},{"text":648},{},{"id":651,"data":1513,"type":42,"tunes":1514},{"text":653,"level":219},{},{"id":656,"data":1516,"type":226,"tunes":1517},{"text":658},{},{"id":661,"data":1519,"type":226,"tunes":1520},{"text":663},{},{"id":666,"data":1522,"type":42,"tunes":1523},{"text":668,"level":219},{},{"id":671,"data":1525,"type":671,"tunes":1533},{"items":1526,"title":698},[1527,1528,1529,1530,1531,1532],{"id":675,"answer":676,"question":677},{"id":679,"answer":680,"question":681},{"id":683,"answer":684,"question":685},{"id":687,"answer":688,"question":689},{"id":691,"answer":692,"question":693},{"id":695,"answer":696,"question":697},{},{"id":701,"data":1535,"type":42,"tunes":1536},{"text":703,"level":219},{},{"id":706,"data":1538,"type":706,"tunes":1546},{"title":708,"entries":1539},[1540,1541,1542,1543,1544,1545],{"term":711,"anchor":446,"definition":712},{"term":281,"anchor":714,"definition":715},{"term":287,"anchor":717,"definition":718},{"term":293,"anchor":720,"definition":721},{"term":299,"anchor":723,"definition":724},{"term":726,"anchor":727,"definition":728},{},{"id":731,"data":1548,"type":42,"tunes":1549},{"text":733,"level":219},{},{"id":736,"data":1551,"type":743,"tunes":1554},{"link":738,"meta":1552},{"image":1553,"title":741,"description":742},{"url":440},{},{"id":746,"data":1556,"type":743,"tunes":1559},{"link":748,"meta":1557},{"image":1558,"title":751,"description":752},{"url":440},{},{"id":755,"data":1561,"type":743,"tunes":1564},{"link":757,"meta":1562},{"image":1563,"title":760,"description":761},{"url":440},{},{"id":764,"data":1566,"type":743,"tunes":1569},{"link":766,"meta":1567},{"image":1568,"title":769,"description":770},{"url":440},{},{"id":773,"data":1571,"type":743,"tunes":1574},{"link":775,"meta":1572},{"image":1573,"title":778,"description":779},{"url":440},{},{"id":782,"data":1576,"type":743,"tunes":1579},{"link":784,"meta":1577},{"image":1578,"title":787,"description":788},{"url":440},{},{"id":791,"data":1581,"type":220,"tunes":1582},{"title":217,"maxLevel":218,"minLevel":219},{},"Post erfolgreich abgerufen",{"items":1585,"source":1614,"manualIds":1615,"manualMatchedIds":1616},[1586,1593,1600,1607],{"id":1587,"slug":1588,"title":1589,"excerpt":1590,"featuredImage":1591,"publishedAt":1592},"476","mcp-vs-a2a-vs-ucp-vs-ap2-vs-a2ui-the-agent-protocol-stack-explained","MCP vs A2A vs UCP vs AP2 vs A2UI: Objašnjen stek agentskih protokola","MCP, A2A, UCP, AP2 i A2UI se često predstavljaju kao konkurentski standardi za agente. Oni uglavnom rešavaju različite probleme interoperabilnosti. Ovaj vodič mapira svaki protokol na granicu koju zapravo standardizuje—i pokazuje kako oni mogu da rade zajedno u jednom produkcionom sistemu.","\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":1594,"slug":1595,"title":1596,"excerpt":1597,"featuredImage":1598,"publishedAt":1599},"478","what-is-rag-the-simplest-explanation-of-how-it-works","Šta je RAG? Najjednostavnije objašnjenje kako funkcioniše","RAG zvuči komplikovano, ali ideja je jednostavna: pre nego što AI odgovori, prvo potraži korisne informacije iz izvora znanja i daje te informacije jezičkom modelu. Ovaj vodič objašnjava RAG, LLM-ove, stanje, memoriju i alate koristeći jedan jednostavan mentalni model.","\u002Fuploads\u002F2026\u002F09\u002Fwhat-is-rag-the-simplest-explanation-of-how-it-works-1790377492124-khjagt.webp","2026-09-25T19:03:00.000Z",{"id":1601,"slug":1602,"title":1603,"excerpt":1604,"featuredImage":1605,"publishedAt":1606},"382","a-practical-monorepo-architecture-next-js-platform-admin-fastify-api-prisma-and-nginx","Praktična monorepo arhitektura sa Next.js, Fastify, Prisma i NGINX","Istražite praktičnu monorepo arhitekturu koristeći Next.js, Fastify, Prisma i NGINX, ističući integraciju i tok rada iz stvarnog sveta.","\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":1608,"slug":1609,"title":1610,"excerpt":1611,"featuredImage":1612,"publishedAt":1613},"381","enterprise-grade-multi-tenant-architecture-for-an-international-platform","Višezakupna arhitektura korporativnog nivoa za međunarodnu platformu","Loving Rocks je platforma za venčanja poslovne klase, dizajnirana sa istinskom više-zakupnom arhitekturom, izolovanim bazama podataka po zakupcu i ugrađenom internacionalizacijom za globalnu skalabilnost, bezbednost i dugoročnu operativnu stabilnost.","\u002Fuploads\u002F2026\u002F01\u002Fenterprise-grade-multi-tenant-architecture-for-an-international-platform-1769789121298-b6v7ak.webp","2026-01-30T12:04:00.000Z","fallback",[],[]]