Two agents, one limit, one refused.

Budgets

Cap what each agent key can run

Set a monthly cap per agent key on the Anlyon operations it can perform, action invocations included. A cost cap sends an alert at 80% by default. At the cap those requests stop with a clear error instead of a surprise line on the invoice. It is a cap on Anlyon operations, not on model tokens or on the money an approved action moves.

Start building freeRead the docs
agent.ts
await anlyon.budgets.put(apiKeyId, {  // $25.00 of Anlyon operations a month for the research agent.  monthlyCostCentsCap: 2500,  alertThreshold: 0.8,});// At the cap, each covered operation on this key returns://   429 BUDGET_EXCEEDED

What it does

Per key

A ceiling per key, not per account

The research agent gets $25 of Anlyon operations a month. Production gets $500. When one hits its cap, that key's covered operations stop and the other keys keep running.

At the cap

Blocked means blocked

Cross the cap and the next request stops with a clear error your agent can catch and handle. Never a silent drop, never an overage you discover on the invoice.

The alert

You hear about it at 80%, not 100%

The alert fires on the cost cap while there’s still room to react. By the time the cap actually bites, it shouldn’t be news.

A pattern

An autonomous researcher on a $5 budget

It runs until the work is done or your cap on Anlyon operations is hit. The cap does not count model tokens or the money an action moves.

View the recipe

Free tier, no credit card. One command if you use Claude or Cursor.

Start building freeRead the docs

$ claude mcp add anlyon -- npx -y @anlyonhq/mcp-server