Reconcile an agent's payments
Reconcile what an agent's wallet paid against what it got for it: every payment with its purpose, receipt and status, the day's spend against the rules, and anything that does not match.
In Lobstack: Skills › Library › Add
What your agent will do.
At the end of a day or a week of paid work, or when a balance looks wrong and somebody wants to know where the money went.
- 01
Read wallet_status: the balances, today's spend, the rules and the recent payments.
- 02
For each payment list the date, the payee or host, the amount, the why, the status and the transaction link. Check any that is not verified with check_transaction.
- 03
Match each paid call to what came back: a payment with no answer, or two payments for the same request, is a finding.
- 04
Total by payee and by purpose, and set the total against the daily allowance. Say how close it ran.
- 05
Lead with what needs a person: mismatches, failures, a payee paid more than expected, a low balance before tomorrow's routine.
Read-only: this pays, retries and refunds nothing. Not accounting or tax advice.
The whole SKILL.md: 30 lines of Markdown.
Add it in the app from Skills › Library, or copy it and paste it into Skills › Add a skill.
---name: payments-reconciliationdescription: "Reconcile what an agent's wallet paid against what it got for it: every payment with its purpose, receipt and status, the day's spend against the rules, and anything that does not match."metadata: title: "Reconcile an agent's payments" category: payments tags: [payments, reporting]--- ## When to use this At the end of a day or a week of paid work, or when a balance looks wrongand somebody wants to know where the money went. ## How 1. Read wallet_status: the balances, today's spend, the rules and the recent payments.2. For each payment list the date, the payee or host, the amount, the why, the status and the transaction link. Check any that is not verified with check_transaction.3. Match each paid call to what came back: a payment with no answer, or two payments for the same request, is a finding.4. Total by payee and by purpose, and set the total against the daily allowance. Say how close it ran.5. Lead with what needs a person: mismatches, failures, a payee paid more than expected, a low balance before tomorrow's routine. Read-only: this pays, retries and refunds nothing. Not accounting or taxadvice.
- Payments
Find a pay-per-call API
Find a pay-per-call API for a job in the x402 Bazaar: what it returns, what it costs per call, which network it settles on, and whether it is worth paying for. Pays nothing.
SKILL.md · App - Payments
Pay for an API call with x402
Call an API that charges per request with x402: set the most it is worth, let the app plan and simulate the payment, pay inside the rules, and report the receipt with the answer.
SKILL.md · App - Payments
Send a USDC payment (Plan, Act, Verify)
Send a USDC payment the safe way: plan it (simulated, with the rules checked), show the plan, act only on that plan, then verify the transfer on chain and report the link.
SKILL.md · App - Payments
Suggest an agent's spending rules
Suggest spending rules for an agent'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.
SKILL.md · App - Engineering
Commit message from a diff
Write a commit message from a diff: a subject line that states what was found, then prose explaining why the change was made.
SKILL.md · App - Engineering
Triage a failing build
Triage a red CI run: find the first real failure, attribute it to a change, and say whether the code is wrong or the runner was.
SKILL.md · App