docs: add Agent Cost Guardrails to AI & ML tools#5871
Conversation
Adds documentation for agent-cost-guardrails, an open-source library that prevents runaway LLM costs in CrewAI crews via hard budget limits, per-call token caps, and alert callbacks. - New page: docs/en/tools/ai-ml/agentcostguardrails.mdx - Registered in docs/docs.json under "AI & Machine Learning" group
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
📝 WalkthroughWalkthroughAdds a new documentation page for the agent-cost-guardrails library and registers it in the docs index. The page includes installation, quick-start usage, examples (budget alerts, per-call token caps), configuration parameters, cost-report schema, and operational tips. ChangesAgent Cost Guardrails Documentation
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/en/tools/ai-ml/agentcostguardrails.mdx`:
- Line 26: Update the sentence "No API key is required — the library hooks into
the CrewAI runtime locally." to clarify that no additional API key is required
for the guardrails themselves while still requiring standard model/provider
credentials; e.g., replace it with wording like "No additional API key is
required for the guardrails — the library hooks into the CrewAI runtime locally;
you still must provide your usual model/provider credentials (API keys) for any
LLMs or external services." Ensure the changed text appears where the original
sentence is located so readers understand the distinction.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: ec207635-e2c3-48ae-8d8f-09751282f835
📒 Files selected for processing (2)
docs/docs.jsondocs/en/tools/ai-ml/agentcostguardrails.mdx
|
Hi team! Friendly bump on this PR. The CodeRabbit review passed after the wording update. The library has 100+ PyPI downloads and addresses a real gap — CrewAI crews have no built-in budget cap, and cost blowups are the #1 pain point for teams running agents in production. Happy to adjust anything if there are style/format requirements. Thanks for considering! |
|
Hi team — bumping this in case it got buried. The PR is review-clean (CodeRabbit approved, no open requests). Since the last ping, agent-cost-guardrails has picked up measurable adoption — would be great to get it in front of CrewAI users through the docs. Happy to address any feedback or rebase if needed. Thanks for maintaining CrewAI! |
Summary
Adds documentation for agent-cost-guardrails, an open-source library that prevents runaway LLM costs in CrewAI crews.
The problem it solves: A typical research crew (Researcher → Writer → Editor) can spend $15–50 in a single
crew.kickoff()call with no built-in way to stop it. This library provides:Changes
docs/en/tools/ai-ml/agentcostguardrails.mdx— full reference with quick start, three examples (basic, alert callbacks, 3-agent crew), parameter table, and cost report schemadocs/docs.json— added"en/tools/ai-ml/agentcostguardrails"to the "AI & Machine Learning" navigation groupPackage
pip install "agent-cost-guardrails[crewai]"Summary by CodeRabbit