OpenAI's guardrails don't control costs. Here's the gap.
OpenAI shipped guardrails in the Agents SDK last month. They validate behavior. They do not enforce spend. Here is the gap and how to close it.
OpenAI shipped guardrails in the Agents SDK last month.
Input guardrails. Output guardrails. Tool call guardrails. The API is clean. The docs are good. A lot of builders are excited.
I want to be clear: these are real. They solve real problems.
They just don't solve the one that costs you money.
What OpenAI's guardrails actually do
OpenAI's guardrails are validators. They inspect what goes into and out of your agents at runtime.
Input guardrail: run logic before the agent processes a message. Block it, redirect it, log it.
Output guardrail: run logic after the agent produces a response. Flag it, filter it, hold it.
Tool call guardrail: intercept a tool invocation before it fires. Approve or reject based on your rules.
These are behavior controls. They answer the question "did my agent do the right thing?"
That question matters. But it is not the question that generates a $47,000 AWS invoice.
The gap
OpenAI's guardrails have no concept of spend.
There is no budget_usd parameter. No on_exceed hook. No token accumulation across a task. No cost ceiling per agent function.
That is not an oversight. It is out of scope. OpenAI is building a framework for agent orchestration and quality control. Budget enforcement is a different layer.
The gap looks like this:
Your pipeline passes every guardrail check. The output is clean. The tool calls are approved. And your agent has now made 400 API calls because a retry loop hit an edge case at 2 AM and nobody was watching.
Guardrails passed. Budget destroyed.
What the cost enforcement layer looks like
I built agentguard47 to sit below the framework layer. One decorator per agent function:
from agentguard47 import guard @guard(budget_usd=2.00, on_exceed="raise") def run_analyzer(task): result = client.responses.create(...) return result
When the agent hits $2.00 in accumulated spend, it raises. You catch it. You decide what to do next.
No silent loops. No surprises at billing time. Each agent function has its own ceiling.
This works with OpenAI's Agents SDK. It works with LangChain. It works with a raw openai client call. The decorator does not care what is inside the function.
The stack you actually want
Use OpenAI's guardrails for what they do well: behavior validation, content filtering, tool approval logic.
Add agentguard47 for what they do not cover: spend enforcement per agent, hard stop on budget breach, cost accumulation tracking.
These are not competing tools. They are different layers. One asks "did the agent behave correctly?" The other asks "did the agent stay within budget?"
You need both questions answered.
Install
pip install agentguard47
Docs and examples: https://bmdpat.com/tools/agentguard
Want more like this?
AI agent builds, real costs, what works. M-F only when there is something worth sending. No fluff.
Patrick Hughes
Building BMD HODL — a one-person AI-operated holding company. Nashville, Tennessee. Twenty-Two agents.
More writing
- 6 min
How to Close the AI Agent Cost Gap at the Call Site
The cost gap between what an AI agent could cost and what it does cost is 40%. You close it at the call site, not in a dashboard. Here is how.
- 4 min
When JPMorgan's AI bill goes up, who controls it?
JPMorgan turned on AI for 250k people. The quiet line is that the usage racks up fees. Here is how to control the bill before it arrives.
- 4 min
Anthropic's IPO and the 40% Cost-Savings Gap: Why Your Spend Cap Matters More Now
Anthropic filed for IPO at a $47B run-rate while 40% of enterprise customers report under 10% cost savings from Claude. Here is how to close that gap.