Resolve one agent's effective cost cap
Resolve the effective per-conversation cost cap (cents) for one agent. The first configured level wins — per-agent config, organization defaults, then the platform default — with a platform-wide hard ceiling applied as a final clamp. cap_cents: 0 acts as a kill-switch; cap_cents: null means unbounded, and source says which precedence level decided. The agent-runtime reads this before every chat turn so it can halt at the ceiling; client-turn budget enforcement, not delivery-level.
Authorizations
Dashboard JWT token from Clerk
Headers
Sandbox opt-in for Clerk-session-authenticated requests. Set to true to route the call through the test-mode pipeline: no real provider delivery, no credits deducted, response meta.test_mode: true. Ignored for live API keys (dv_live_sk_*) — server-to-server clients must use a test-prefixed key (dv_test_sk_*) to exercise sandbox. Test-prefixed keys unconditionally enable sandbox regardless of this header.
true, false Path Parameters
The agent id.
1