the state of .net sdks for ai apis: official, autogenerated, or missing
i build .net clients for ai apis, so i keep a running map of which providers actually support .net developers and which leave them hand-rolling http. the short version: "no .net sdk" is no longer the main problem. the main problem now is autogenerated .net sdks that technically exist but nobody enjoys using. here's the field, in three buckets. bucket 1: official, hand-maintained (the good ones) these vendors treat .net as a first-class citizen. if you're on one of these, you're fine.…
building enterprise multi-agent workflows in .net with mistral
most people know Mistral for its chat models. the part i find more interesting for enterprise work is the Agents API: persistent agents with instructions and tools, stateful conversations you can resume, built-in connectors (web search, code interpreter, document library), and handoffs so one agent can delegate to another. the .net story stops short of this. the community sdks (tghamm's is genuinely good) cover chat completions, embeddings and function calling. they don't cover the agentic…
giving a .net app a voice: building on the elevenlabs agents platform
ElevenLabs is best known for text to speech, but the thing i find most interesting is ElevenAgents: you configure an agent with a prompt, a voice and some tools, and it handles the whole voice loop. speech to text, the llm, turn-taking, interruptions, text to speech. you just open a websocket and talk. they ship sdks for python, typescript, kotlin and swift. nothing for .net. so if you want to build a voice agent from c#, you're hand-rolling the websocket protocol. i didn't want to do that…