Skip to main content
Bounds decides an agent’s tool call before it runs. Rules judge the proposed call against the path of its task, not in isolation, so a send that follows an untrusted read is refused and the refusal names the step that tainted it. Every verdict is appended to a local, hash-chained, signed ledger. Installed as attesso. Any action, not only payments. Free and unlimited on your own machine; $0.00085 per synced decision when the record has to leave your laptop, $2 of credit to start, no plan, no seats, no minimum.

​
What it decides, in one session

log evaluates the policy and the path, writes the verdict, and exits 1 when it refuses. report answers what a task cost and what it was stopped from doing, per task.

​
Connect an agent instead

The connector is the shortest path: it initializes the ledger, writes the mode file, wires every harness that has an installer, and returns JSON.
observe records every verdict without blocking. npx attesso mode enforce turns enforcement on for the next call. The harness wiring, the per-harness refusal shapes and the manual steps are in Connect an agent.

​
Two tiers, one vocabulary

The split is deliberate: the signing key sits beside the log, so a local record proves integrity, not authority. Human authority, cross-device keys and verification by someone who does not trust you need the hosted plane. Receipts and packets states exactly which artifact proves what.

​
What lands in .attesso/

--dir PATH points any command at a different ledger directory.

​
What Bounds is not

  • Not a sandbox. File tools are scoped by roots and exclusions, and shell can be denied outright, but execute is never command-parsed. Scope file tools spells out the boundary.
  • Not observability or an eval harness. It decides before a call runs; it does not grade output after the fact.
  • Not a payment product. It does not execute or move money. The authorization chain for payments is the core model.

​
Price

  • Free and unlimited locally: rules, ledger, report, hook, receipts, no account.
  • $0.00085 per synced decision, $0.85 per 1,000, about $34 a month for a developer running 40,000 agent calls.
  • $2 of credit to start, about 2,350 decisions, no card. Top up from $10; a monthly cap you set.
  • Volume and platform contracts: contact sales.

​
Where to go next

Connect an agent

One connector, five harnesses, and the observe-to-enforce ladder.

Write path rules

The rule language, step and repeat ceilings, and how to test a rule change.

Read the ledger

Entry shape, report, watch, and steering a running task.

Prove a decision

Receipts, bundles, packets, and the limits of each.