Rohit Bhardwaj is Director of AI & Data Architecture at Salesforce, an O’Reilly instructor, and founder of AI Architect Circle. With 30 years of experience in software and enterprise architecture, he helps engineers, architects, and technology leaders make architecture decisions they can explain and defend.
His work brings together enterprise AI, agentic systems, data architecture, and distributed systems. He focuses on the decisions that determine whether a system remains reliable, secure, accountable, and economically sustainable when it encounters real-world demands.
Rohit’s talks and workshops explore practical questions: What happens when an AI agent acts on conflicting information? Can a failed payment be retried safely? Who can stop an autonomous action, and what evidence explains the decision afterward? His teaching connects these questions to architecture, customer trust, and business outcomes.
He is the author of System Design with AI Interview Guide: Designing Scalable, Agentic, and Defensible Systems, published by Apress. He also developed ARCHVIEW™, ROCS Loops™, and LLM-SHIELD™ to help teams structure architectural thinking and address the challenges of building trustworthy AI systems.
Through AI Architect Circle, Rohit extends this learning through live discussions, book walkthroughs, videos, and interactive architecture challenges. These challenges explore incidents such as payment timeouts and conflicting bookings, helping participants practice the judgment behind their design decisions.
Join Rohit live on Saturdays at 9:00 a.m. Eastern
System Design with AI — Live with the Author is a free live podcast and Q&A series featuring practical system-design scenarios, AI architecture discussions, and questions from the community.
See the next session and register
Try an interactive architecture challenge
Put your design decisions under pressure and explore the consequences.
Explore the challenges
Explore AI Architect Circle
Find architecture lessons, videos, resources, and ways to continue learning.
Visit AIArchitectCircle.com
Read the book: Amazon · O’Reilly
Watch and connect: YouTube · Instagram: @aiarchitectcircle · LinkedIn · X / Twitter: @rbhardwaj1
PIs built for humans often fail when consumed by AI agents.
They rely on documentation instead of contracts, return unpredictable structures, and break silently when upgraded. Large Language Models (LLMs) and autonomous agents need something different: machine-discoverable, deterministic, idempotent, and lifecycle-managed APIs.
This session introduces a five-phase API readiness framework—from discovery to deprecation—so you can systematically evolve your APIs for safe, predictable AI consumption.
You’ll learn how to assess current APIs, prioritize the ones that matter, and apply modern readiness practices: function/tool calling, schema validation, idempotency, version sunset headers, and agent-aware monitoring.
Problems Solved
What “AI-Readiness” Means
Common Failure Modes Today
Agenda
Introduction: The Shift from Human → Machine Consumption
Why LLMs and agents fundamentally change API design expectations.
Examples of human-centric patterns that break agent workflows.
Pattern 1: Assessment & Readiness Scorecard
How to audit existing APIs for AI-readiness.
Scoring dimensions: discoverability, determinism, idempotency, guardrails, lifecycle maturity.
Sample scorecard matrix and benchmark scoring.
Pattern 2: Prioritization Strategy
How to choose where to start:
Key Framework References
Takeaways
AI agents are becoming a new class of API consumers. Unlike human users, agents can create bursty traffic, retry aggressively, call multiple tools in parallel, and accidentally amplify downstream failures. A single user request can become a large chain of API calls, model calls, vector searches, database lookups, and workflow events.
This talk explains how to design APIs for this new reality.
We will cover agent-aware rate limiting, budget-aware throttling, backpressure, load shedding, idempotency, deduplication, deterministic caching, async workflows, event-driven APIs, tail-latency SLOs, and cost observability.
Participants will learn how to tag and trace agent traffic, control runaway tool calls, prevent retry amplification, design graceful degradation, and build runbooks for cache storms, retry storms, dependency brownouts, and cost spikes.
The core message:
APIs exposed to AI agents must be contract-safe, retry-safe, cost-aware, observable, and degradation-ready.
Classic API scaling assumed relatively predictable traffic.
AI-driven API traffic is different because:
Agenda