Taking back control

You never need permission — or a working AI — to stop things. From softest to hardest:

1. Reduce or remove a budget

   Turn a 500 USDG cap into 50. Lowering takes effect the moment you save it — Waypoint stops at the new number immediately, and you can trim the on-chain approval to match whenever you like. Raising takes one approval signed from your wallet, because the cap is an on-chain allowance and only you can widen it. Setting it to zero is the same act as Cut off funds below, and has the same reach.

2. Rotate the credential

   The AI’s key stops working mid-sentence. Your budgets stay exactly as they are; reconnect a new key when you’re ready. Rotating asks you to confirm, then to sign with your wallet — the same signature is required to read an existing key back, so an API token on its own can never hand out a working credential.

3. Revoke the session

   The credential dies and every budget is disabled at once, on Waypoint’s side. The session key stays installed on-chain until you revoke each budget (an uninstall you sign) or cut off funds below.

4. Cut off funds

   One transaction from your wallet sets the spending approval to zero, straight at the token itself:

   Copy

   approve(executor, 0)

   This one doesn’t even involve Waypoint: it works even if our servers are down.

   It stops every budget in that token, not one of them. All of your budgets on a chain share one executor, and therefore one approval per token — so setting your USDG approval to zero stops every USDG budget you hold, at once. Budgets denominated in any other token are untouched, because one approval reaches one token. Waypoint’s own per-budget caps are what keep them apart in normal use; this control is deliberately blunter than that, because it has to work when nothing else does.