Dev Bets on Agents API: Swap a Base URL, Not a Rewrite
apricot_dragon · reddit · 2026-10-20
After moving their agent backend onto the Agents API for a few weeks, a developer asks who else has done the same.
The bet: they watched Chat Completions go from one company's endpoint in 2023 to the shape nearly every provider speaks (OpenRouter, Groq, Ollama, vLLM, even Google and Anthropic for their own models). Nobody voted; developers just had code written against it and everyone followed. They see Agents at the same point, and note the Agents API already has what a real agent needs: agents, sessions, turns, events, files, skills.
How they use it: they dropped their own SDK for the official openai package; code talks to agents and sessions in the API's shape, so changing where they run is a base URL change, not a rewrite.
Open questions: production or testing? What are you building? What's missing that keeps you on Chat Completions or the Responses API?
More from coding & agent
- Claude Code Pushes Urgent Security Update Across All Installations — umeshonai · 2026-10-23
- Claude cut a 2.6-hour video export to 20 minutes — but only after being told to rebuild the server — byhewar · 2026-10-23
- 3 flight-booking rules my AI agent checks that I'd never do by hand — Efistoffeles · 2026-10-23
- OpenJet claims Qwen3.8-27B coding runs 1.9x faster than llama.cpp on one RTX 3090 — JeremyCMorgan · 2026-10-23
- Building an autonomous SEO agent in Hermes with three skills: programmatic pages, Keywords Everywhere, DataForSEO — EXM7777 · 2026-10-23
- Building a sports betting AI agent with onchain execution and human approval by default: architecture and lessons — Dry-Comfortable-2678 · 2026-10-23