Skip to content

Payments · For your bots

Suggest a bot's spending rules

Suggest spending rules for a bot's wallet from what its job costs: per payment, per day, the amount it may pay without asking, and what scheduled runs may spend. The person sets them.

In Lobstack: Skills › Library › Add

Download Lobstack

When to use it

A bot has just been given a wallet, or its job has changed, and the person wants rules that let it work without asking about every cent — and no more.

What your bot will do

  1. 01

    Work out what the job costs: the paid calls a run makes, their prices, how many runs a day, from recent payments where there are any.

  2. 02

    Suggest each rule with the arithmetic behind it:

    • most per payment: the dearest single call, with a little headroom;
    • per day: a normal day's spend, with room for a busy one;
    • pay without asking: small enough that a mistake is cheap;
    • scheduled runs per day: zero unless a routine really needs to pay.
  3. 03

    Suggest allowed payees when the job only ever pays a few hosts.

  4. 04

    Say what each rule would have refused in the recent payments.

  5. 05

    Hand it over as a suggestion. Only the person changes the rules, in the bot's Wallet settings; the bot has no way to.

Tighter is the default: a rule can be loosened after a refusal, but not after a loss.

The file

spending-rules-review/SKILL.md30 lines
---name: spending-rules-reviewdescription: "Suggest spending rules for a bot's wallet from what its job costs: per payment, per day, the amount it may pay without asking, and what scheduled runs may spend. The person sets them."metadata:  title: "Suggest a bot's spending rules"  category: payments  tags: [payments, policy]--- ## When to use this A bot has just been given a wallet, or its job has changed, and the personwants rules that let it work without asking about every cent -- and no more. ## How 1. Work out what the job costs: the paid calls a run makes, their prices,   how many runs a day, from recent payments where there are any.2. Suggest each rule with the arithmetic behind it:   - most per payment: the dearest single call, with a little headroom;   - per day: a normal day's spend, with room for a busy one;   - pay without asking: small enough that a mistake is cheap;   - scheduled runs per day: zero unless a routine really needs to pay.3. Suggest allowed payees when the job only ever pays a few hosts.4. Say what each rule would have refused in the recent payments.5. Hand it over as a suggestion. Only the person changes the rules, in the   bot's Wallet settings; the bot has no way to. Tighter is the default: a rule can be loosened after a refusal, but notafter a loss.

Get Lobstack.