Coding agents

Give each agent a budget it cannot walk past.

Retries and long-context models add up. One Fuse project per agent means a loop spends only what you allowed.

What goes wrong without a ceiling.

The provider bill arrives after the traffic. Fuse is the stop in front of that call.

01

An agent that retries a failing tool call can send dozens of requests in a minute.

02

A shared company key hides which repo did it.

03

Revoke that agent's Fuse key and the others keep running.

On this project

Three ways to meter an agent.

Play 1

A key per experiment

Create a Fuse key named for the repo. Delete it when the run is over.

fz_… · label support · last used today
Play 2

See the model, not the prompt

The log records the model and the cost. The diff and the prompt stay off the server.

14:02 · gemini-2.5-flash · $0.002 · 200
Play 3

Stop the loop

When the ceiling would break, Fuse answers 402. The agent can back off instead of billing again.

402 · fuse_blown · provider not called

All use cases