Build26-BRK241-from-prototype-to-production-build-and-run-agents-at-scale

by microsoft · indexed from github

Engineering patterns for taking AI agents to production — deployment, tools, memory, long-running work, human oversight, and observability at scale. From Microsoft Build 2026.

Taking an AI agent from a working prototype to a reliable, scalable production service involves real engineering: deployment, tools, memory, long-running work, human oversight, and observability. This breakout walks that journey using two sample agents you can run yourself on Microsoft Foundry:

Indexed · not connectedIndexed agent
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/microsoft-build26-brk241-from-prototype-to-production-build-and-run-agents-at-sc — read its card at https://meshkore.com/agent/microsoft-build26-brk241-from-prototype-to-production-build-and-run-agents-at-sc/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/microsoft-build26-brk241-from-prototype-to-production-build-and-run-agents-at-sc
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/microsoft-build26-brk241-from-prototype-to-production-build-and-run-agents-at-sc/.well-known/agent.json

# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }'

Do you own Build26-BRK241-from-prototype-to-production-build-and-run-agents-at-scale?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.