AI agent development is the engineering of LLM-powered systems that can reason about a goal, choose tools, take multi-step actions and self-correct from feedback. Agents go beyond single-prompt completions: they call APIs, query databases, run code, route to other agents and maintain state across a conversation or workflow. Production agents require evaluation sets, guardrails, audit logging, observability and rollback procedures. Pharos delivers customer support agents, document Q&A agents, multi-agent operations systems and domain-specific copilots integrated with client data and tools. Unlike a direct OpenAI or Anthropic SDK call, which is cleaner and roughly one tenth the cost for single-shot tasks such as classification or summarization, an agent earns its complexity only when the workflow needs multi-step reasoning, tool orchestration or error recovery. Unlike a deterministic rules engine, which is 100x cheaper and fully auditable when the decision tree is stable, an agent pays off when inputs are open-ended and the branching is too broad to encode. Pharos picks agents only when neither alternative can deliver the outcome.
Authoritative citations
12 sources
-
NIST
NIST AI Risk Management Framework (AI RMF 1.0) defines the govern-map-measure-manage lifecycle for trustworthy AI including agentic systems
nist.gov
-
OWASP
OWASP Top 10 for Large Language Model Applications (2025) lists prompt injection, insecure output handling and excessive agency as top agent risks
owasp.org
-
a16z
Andreessen Horowitz reports 60% of enterprise AI deployments now include at least one agentic component, up from 9% in early 2024
a16z.com
-
OpenAI
OpenAI function calling and Assistants API documentation describe structured tool use as the recommended pattern for production agents
platform.openai.com
-
Anthropic
Anthropic Claude tool use guide recommends schema-validated structured output and parallel tool calls for reliable agent loops
docs.anthropic.com
-
LangChain
LangChain concepts documentation on agents establishes the eval-harness plus observability plus guardrail pattern used across LangSmith deployments
python.langchain.com
-
arXiv
ReAct paper (Yao et al., 2023) established the reason-act-observe loop as the foundation of modern tool-using agents
arxiv.org
-
arXiv
Reflexion paper (Shinn et al., 2023) demonstrated self-correction loops improving agent task completion by 20-30 points across benchmarks
arxiv.org
-
Gartner
Gartner predicts that by 2028, 33% of enterprise software applications will include agentic AI, up from less than 1% in 2024
gartner.com
2024
-
HHS
HHS guidance on artificial intelligence under HIPAA requires audit logging, access controls and de-identification for any PHI processed by AI agents
hhs.gov
-
Stanford HAI
Stanford AI Index documents that agentic benchmarks (SWE-bench, WebArena, AgentBench) have become primary reliability signals for production LLM systems
hai.stanford.edu
-
Google DeepMind
Google DeepMind research on a responsible path to AGI emphasises reward hacking and specification gaming as core failure modes requiring guardrails in production
deepmind.google
What we do not do
- Single-prompt LLM features where direct OpenAI/Anthropic SDK usage is cleaner than an agent framework
- Agents without an evaluation set tied to business outcomes
- Use cases where deterministic rules engines would be cheaper and fully auditable
- Real-time systems with sub-100ms latency budgets that LLM inference cannot meet
- Projects with no plan for prompt versioning, drift monitoring or rollback