How do I cap what an agent spends on hosting?

Question

Accepted Answer

By choosing a plan where the agent cannot spend at all, or by setting the cap yourself. On the Website plan (€ 10 a month) and the App plan (€ 15) the price is fixed: an agent can deploy, but no action it takes adds a cent to the invoice. On the Platform plan the spending cap per site is the ceiling: default € 50 a month, adjustable up to € 250, and at 100% the containers pause until you raise it.

Where an agent could cost money	What stops it
Deploying too often	50 deploys a day on Website, 20 on App; more is refused
Switching on building blocks	not a right an agent has; building blocks are switched on by you in the portal
Usage on Platform	the cap you set; email at 80%, pause at 100%
Creating extra sites	a new trial site needs an email address and is free for 14 days; keeping one is a payment you make
Doing things you did not intend	rights per key; a missing right returns an error, and every action is in the audit log

A key never carries a payment method. Paying, upgrading and switching on building blocks stay actions of a person in the portal, so the worst an agent can do on a fixed plan is publish a version you did not want. That you fix with a new deploy.

Give the agent a key with only the rights it needs, and add the site's MCP server to your tool:

claude mcp add --transport http dorelli https://mcp.dorelli.cloud/<your-site> --header "Authorization: Bearer <agent key>"

The agent can read its own limits and today's usage with the limits tool, so a well-behaved agent stops before we have to stop it. The audit log in your portal shows every action, including the refused ones, for 30 days on Website and 90 days on App and Platform.

Not for

A budget per key: the cap is per site, and a fixed plan has no meter to cap. Not for agents that must buy things (domains, add-ons, bigger containers) on their own; that needs a person, on purpose.