Skip to content
Burnwatch logo

Burnwatch

Monitors each autonomous agent's payment stream, learns its normal spend rate and payees, and alerts on drains.

Free plan · From $19/mo

At a glanceswept Oct 17, 2026

32 linking domains

Emerging

For
Engineers running autonomous AI agents that spend money through x402 or plain HTTP 402 payments
Price
Free plan · From $19/mopricing page, read Oct 22, 2026
Runs as
SDK
Used for
  • Alert when an agent's spending rate suddenly spikes
  • Flag payments to recipients an agent has never paid
  • Detect payment bursts that follow a tool call
read off burnwatch.dev on Oct 22, 2026
Worth knowingcomputed from what we read · each with its source
  • Launched on Product Hunt on Jun 24, 2026Product Hunt ↗
Pricingpricing page, read Oct 22, 2026

Free plan · From $19/mo

Alternatives in Financeby use, among tools still maintained

Figure and bar: visits/mo, estimate · year: online since

Compare Burnwatch with

Pick up to two.

All 10 alternatives to Burnwatch →

All Finance tools →

Not it? Say what you need

beta

Three tools from the Atlas for the job you describe, each with what fits and what does not.

From people who use itnot part of the reading

No notes yet. What do you use Burnwatch for?

Sign in to leave a note
Questions this page answers
  • What is Burnwatch?

    Monitors each autonomous agent's payment stream, learns its normal spend rate and payees, and alerts on drains. It is listed in the Atlas under Finance, Developer tools.

  • Who is Burnwatch for?

    Engineers running autonomous AI agents that spend money through x402 or plain HTTP 402 payments

  • How much does Burnwatch cost?

    Burnwatch has a free plan; paid plans start at $19/mo, per its pricing page on 2026-10-22.

  • Is Burnwatch free?

    Yes, Burnwatch has a free plan, per its pricing page on 2026-10-22.

  • Do people use Burnwatch?

    Emerging.

  • What are alternatives to Burnwatch?

    In Finance, by use: RunVouch, Longbridge, RateZip, Poisar, SteelEye, BidSparq.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.

How we read every tool → · By INITE Atlas Desk