Skip to main content
PRYSM’s AgentGuard gives autonomous agents a hard spending ceiling that cannot be exceeded — not “+5% tolerance”, not soft limits agents work around, but a hard cap enforced before any model call is made.

How AgentGuard works

Every agentic run through PRYSM’s /v1/agent/run endpoint:
  1. Sets a hard ceiling (max_cost_usd). The run stops immediately if spend would exceed it.
  2. Auto-downshifts intensity (Laser → Halo → Foton) under budget pressure instead of overspending.
  3. Emits X-Prysm-Budget-Remaining on every response — agents can read this to self-regulate.
  4. Returns a PrysmProof v2 trajectory — a cryptographic receipt of every step, spend, and model used.
For single-request LLM calls (non-agentic), pass X-Max-Cost-USD as a request header to cap individual completions.

LangChain

Per-request cap

Cap in a LangChain agent

Reading X-Prysm-Budget-Remaining


CrewAI

Per-agent cost guard

Total crew budget via PRYSM agentic run


AutoGen

Cost-limited agent

Multi-agent setup with per-role budgets


OpenAI Agents SDK


Safe default BRAIN.md for agents

Set auto_downgrade: true in your plan settings so PRYSM falls to the next cheaper tier rather than failing the request when a model would exceed the cap.

See also