This is not a personal-brand pitch or a holding-company tour. AgentGuard Pro is the paid product. Start with the free Python SDK when you need local guardrails. Start the Pro trial when your agents need hosted run history, read keys, alerts, and a dashboard for the evidence. AgentGuard is the flagship: budget, loop, timeout, and rate limits before your agent keeps spending.
$ pip install agentguard47Observed package downloads, updated hourly. SDK lifetime counts use Pepy; SDK recent-month counts use Pypistats; MCP recent-month counts use npm. Downloads are a usage signal, not an adoption proof. Tracked copy is shown when a metric upstream is unavailable.
Projection: 6 AgentGuard Pro subscribers at $39/mo is $234/mo, above the $200/mo baseline.
decision
The research answer is not three things to buy. A builder creates trust. A company handles the receipt. A product gets installed, trialed, and paid for. This page goes all in on the product and keeps every commercial path pointed at AgentGuard Pro.
Use the public build story as proof of taste, urgency, and product judgment. It is not the thing for sale.
Keep the legal entity on receipts, terms, refunds, and support. Do not make visitors buy the holding-company idea.
pip install agentguard47 proves the value locally. $39/mo adds hosted history, read keys, alerts, and a dashboard. $79/mo is the team upgrade.
Baseline projection: 6 AgentGuard Pro subscribers at $39/mo is $234/mo, above the $200/mo baseline.
Monthly download data is unavailable right now, so the page falls back to fixed baseline math instead of inventing a conversion number.
Most agent tools tell you what happened after the run. AgentGuard adds budget, loop, timeout, and rate limits before unattended work keeps going.
Start with the Python SDK. Add MCP when you want Claude Code, Cursor, Codex, or another MCP client to inspect traces, alerts, usage, costs, and budget health. Use the hosted dashboard when local files are not enough.
Observed package downloads, updated hourly. SDK lifetime counts use Pepy; SDK recent-month counts use Pypistats; MCP recent-month counts use npm. Downloads are a usage signal, not an adoption proof. Tracked copy is shown when a metric upstream is unavailable.
from agentguard import BudgetGuard, JsonlFileSink, LoopGuard, Tracer
budget = BudgetGuard(max_cost_usd=5.00, max_calls=50)
loop = LoopGuard(max_repeats=3)
tracer = Tracer(
sink=JsonlFileSink(".agentguard/traces.jsonl"),
service="support-agent",
guards=[loop],
)
with tracer.trace("agent.run") as span:
budget.consume(calls=1, cost_usd=0.02)
loop.check("search", {"query": "refund policy"})
span.event("tool.call", data={"tool": "search"})
# Call your agent or tool here.Free. Local-first. Raises inside the running process when budget, loop, timeout, and rate limits are crossed.
Read-only access for Claude Code, Cursor, Codex, or another MCP client to inspect traces, alerts, usage, costs, and budget health.
Use the hosted app for read keys, up to 500K retained events on Pro, alerts, and shared visibility. Keep the first integration local if that is all you need.
Create read key ->Stop a run before an experiment turns into a surprise bill.
Stop repeated tool calls before retries become an operator problem.
Put a hard wall-clock ceiling around unattended agent work.
Keep background jobs from hammering tools while nobody is watching.
Write JSONL traces and incident reports for traces, alerts, usage, costs, and budget health without forcing a dashboard first.
{
"mcpServers": {
"agentguard": {
"command": "npx",
"args": [
"-y",
"@agentguard47/mcp-server"
],
"env": {
"AGENTGUARD_API_KEY": "ag_your_read_key_here"
}
}
}
}buy path
$39/mo after the 14-day trial. Keep the free SDK local when that is enough. Use Pro when you need retained runs, read keys, alerts, and a dashboard around the proof.