Your research agent works great in a notebook. Then it leaks API keys in a stack trace, forgets what it researched two messages ago, and returns three citations, two of which link to pages that do not exist. The demo everyone loved is now a liability. Research agents break in ways generic deployment guides miss. They call several external services with different logins, they build on what they found a few turns ago so they need memory most setups throw away, and they have to show real sources, because one made-up citation kills trust for good. This talk fixes all three. Keep credentials out of the agent and hand it short-lived ones that expire. Give it memory that carries across turns so it builds on its own work. And check every citation before the user sees it: the link is real, the page is reachable, and it actually says what the agent claims. You leave with a way to ship a research agent that does not leak, does not forget, and does not invent its sources.

Outline: • The Research Agent That Became a Liability • Securing Credentials with API Gateways • Persistent Conversation Context • Source Verification That Actually Works • The Complete Research Agent and Resources