AI Agent Spending Limits

Give the agent a balance it can spend, not a card it can run up. With Locus Pro, an agent pays for each API, data or tool call from prepaid credits, and every limit is checked before the provider runs. A call over any limit is refused with a clear error and costs nothing. Most teams combine three limits: a monthly cap for the whole workspace, a monthly budget for each agent, and a price ceiling on each call.

• •Prepaid balance — The agent can only spend credits that are already there. When the balance cannot cover a call, Locus returns HTTP 402 before the provider runs.
• •Workspace monthly hard limit — A ceiling for the calendar month across every agent and key. It counts completed charges plus calls still in progress, and refuses new calls once reached.
• •Monthly budget per agent or connected app — Set a budget on an agent key, or on an app such as Claude Code or Cursor when you approve its sign-in. One agent cannot use up the budget meant for the others.
• •Per-call and per-loop limits — An agent key can carry a maximum price per call and a maximum spend per loop, which stops a retry loop after a few calls instead of a few hundred.
• •Price ceiling on each call — The agent sends max_credits with a call. If the price would exceed it, the call is refused before dispatch and nothing is charged. This matters for live-priced services.
• •Approval above an amount — Optionally ask a person before any agent call over a set price. The agent gets an approval link to send to an admin and retries once it is approved.

Yes. When Claude Code, Codex, Cursor or another MCP client signs in to Locus Pro, the consent screen lets you set a monthly budget for that app. The coding agent can then search the catalog and call paid tools until it reaches the budget, and calls beyond it are refused with the budget, the amount already committed and the reset date. Searching the catalog, describing a tool and checking the balance are free.

On an Enterprise workspace, each of your customers gets their own balance and policy. Calls name the customer, Locus charges that customer’s balance at the base price plus your markup, and a policy can limit what each customer’s agents spend. Your own workspace limits still apply on top, so a single customer cannot exhaust your pool.

• •The per-loop limit on the agent key caps spend for one task run.
• •The per-call price ceiling stops one expensive call.
• •The monthly budget and the workspace hard limit cap total exposure.
• •Retries that reuse the same idempotency key replay the stored result instead of paying again.
• •An API key cannot raise its own limits; changing them needs a signed-in owner or admin.

Locus Pro limits what agents spend on APIs, data and tools in its catalog. If your agent buys goods from merchants or pays people, you need a card or payment platform with its own controls; compare them in the agentic payment platforms guide.