What an AI agent developer actually builds
Agent design: deciding what the agent may do, expressing that as tools with strict schemas, and choosing between a single agent with tool calling, a planner-worker pattern, or a graph of specialised agents with handoffs. I use LangGraph for orchestration where state and branching matter, the OpenAI and Anthropic Claude APIs directly where they do not, and MCP servers to expose tools that other agents can share.
Retrieval: chunking and embedding your documents, help centre or database into pgvector, hybrid search with reranking, permission-aware retrieval so users only see what they are allowed to, and citations so answers can be checked. Evaluation: a test set built with you in week one, automated regression gates in CI, and tracing so every agent run can be replayed and costed.
- Tool calling and function calling with validated schemas and idempotent actions
- Multi-step and multi-agent workflows with LangGraph, handoffs and human review steps
- RAG pipelines: ingestion, chunking, pgvector, hybrid search, reranking, citations
- Guardrails, rate limits, cost caps and abuse protection
- Model routing and fallback across OpenAI, Anthropic Claude, Groq and open models
- LLM observability: tracing, evals, cost and quality dashboards