Audit and framing
Define the decisions the agent may take, the tools it may call and the actions that always require a human.
An agent that works in production is a system with permissions, limits, tools, memory and a supervision path - not a prompt loop.
I design and build tool-using agents, including multi-agent orchestration with sequential fallbacks and full traceability.
A supervisor agent calls retrieval, business APIs and a code sandbox, surrounded by memory, an evaluation set and human approval.
Define the decisions the agent may take, the tools it may call and the actions that always require a human.
Build the agent graph, the tools, the memory and the evaluation set, then compare architectures on real cases.
Add monitoring, fallbacks and alerts, then hand over the operating runbook to your team.
When the task requires choosing tools or adapting a sequence to the content. A deterministic pipeline stays cheaper and more predictable for stable, well-specified processing.
Mainly Pydantic AI for typed agents and tools, alongside LangGraph or Bedrock agents when the surrounding stack calls for it. The choice follows the constraints, not the reverse.
Actions are explicitly allow-listed, arguments are validated, risky steps require confirmation, and every call is traced. Recovery is part of the design.
Yes. Agents can run serverless or on managed services inside your account, with your model providers and your access controls.