Per-Tenant Quotas

A practical guide to per-tenant quotas within the agent rate limiting and quotas topic.

What This Lesson Covers

Per-Tenant Quotas is a key topic within Agent Rate Limiting and Quotas. In this lesson you will learn what it is, why it matters, the mechanics behind it, and the production patterns that experienced agent engineers use. By the end you will be able to apply per-tenant quotas in real agent systems with confidence.

This lesson belongs to the Agent Operations category of the AI Agents track. Everything is grounded in patterns shipping in real production agent systems — not toy examples. The agents space moves fast, but the underlying principles are stable.

Why It Matters

Stop runaway agents from blowing your bill. Master token bucket rate limiting, per-tenant quotas, circuit breakers, and the patterns to fail fast under abuse.

The reason per-tenant quotas deserves dedicated attention is that the difference between an agent demo and an agent in production often comes down to the small decisions made here. Two teams using the same model and the same framework can ship wildly different reliability based on how well they execute on this technique. Understanding the underlying mechanics — not just copying a tutorial — is what lets you adapt when the stock approach falls over in your specific environment.

How It Works in Practice

Below is a worked example showing how to apply per-tenant quotas in real agent code. Read through it, then experiment by changing the parameters and observing the effect on your traces and outputs.

import time
from collections import deque

class TokenBucket:
    def __init__(self, capacity: int, refill_per_sec: float):
        self.capacity = capacity
        self.tokens = capacity
        self.refill = refill_per_sec
        self.last = time.time()

    def take(self, n: int = 1) -> bool:
        now = time.time()
        self.tokens = min(self.capacity, self.tokens + (now - self.last) * self.refill)
        self.last = now
        if self.tokens >= n:
            self.tokens -= n
            return True
        return False

bucket = TokenBucket(capacity=100, refill_per_sec=1)
if not bucket.take(10):
    raise RateLimitError("Slow down")

Step-by-Step Walkthrough

1. Set up the environment — Install the relevant SDK or framework and have your model API keys ready. For agents that use tools, also wire up any external services they will call.
2. Define the agent contract clearly — What is the agent supposed to accomplish? What tools does it have? What is it forbidden from doing? Sloppy contracts produce sloppy agents.
3. Pick the right model and parameters — Not every agent step needs a frontier model. Routing cheap tasks to small models is often the biggest single cost lever you have.
4. Instrument from day one — Wire up tracing (LangSmith, Phoenix, OpenTelemetry) before you write the second feature. Debugging an unstrumented agent loop at 2am is misery.
5. Iterate on real failure modes — Build an eval set from your actual production failures, not from synthetic happy-path examples. The hard cases are where the wins live.

When To Use It (and When Not To)

Per-Tenant Quotas is the right tool when:

• You need a repeatable, measurable approach — not a one-off experiment
• The agent volume justifies the engineering effort to set it up properly
• You have clear evals to know whether the technique improved outcomes
• Your latency and cost budget can absorb the overhead it adds

It is the wrong tool when:

• A simpler agent (or no agent at all, just a workflow) already meets your quality bar
• You do not yet have any eval signal — build the eval first
• The added complexity will outlive your willingness to maintain it
• You are still iterating on the core agent contract — stabilize that first

Production Checklist

• Are all agent traces captured (inputs, tool calls, outputs, latency, tokens)?
• Is there an eval set drawn from real production examples that exercises this technique?
• Do you have iteration caps, token budgets, and cost ceilings so a runaway loop cannot blow up your bill?
• Is there a clear human escalation path for tasks the agent cannot or should not handle?
• Have you red-teamed the agent against prompt injection and tool abuse for this technique?
• Does the cost and latency overhead make sense at your real traffic, not just at the demo?

Next Steps

The other lessons in Agent Rate Limiting and Quotas build directly on this one. Once you are comfortable with per-tenant quotas, the natural next step is to combine it with the patterns in the surrounding lessons — that is where compound returns kick in. Agent skills are most useful as a system, not as isolated tricks.