Adding Responses API to an Agent Framework
How we added OpenAI Responses API support to an agent framework: auto-detection, input conversion, tool schema flattening, and response normalization without touching the Chat Completions path.
Tag archive
How we added OpenAI Responses API support to an agent framework: auto-detection, input conversion, tool schema flattening, and response normalization without touching the Chat Completions path.

A technical comparison of FutureX, Microsoft Agent Framework, and AutoGen across multi-agent orchestration models, deployment maturity, and production readiness in 2026.
The Framework Decision That Defines Your Project You want to build an AI agent. But which...
Beyond Basic LangChain You've built a simple agent. Now scale it. Production LangChain...
I Built a Brain for AI Agents — 8 Cognitive Layers, 23,000+ Lines, Zero Bullshit ...

The question that breaks every AI demo Picture the scene. You've just founded a...
Across the previous five posts, we've been doing one thing: pulling Agents back from "magical model capabilities" to "explainable runtime systems."
Something is rapidly happening in the .NET agentic AI ecosystem. Frameworks are emerging, patterns...

In my previous article, I built a multi-agent pipeline that reads a Markdown backlog and provisions...

I have some background with other agent frameworks like CrewAI and LangGraph, so when Microsoft...

How a consent dialog on a local news site led me to build an open-source AI-powered privacy analysis tool using the Microsoft Agent Framework, vision models, and a lot of stubbornness.

This article is part of Festive Tech Calendar 2025 initiative. You'll find other helpful articles...