Someone still has to create payment. It does not have to be you
Your MOCO, worked while you do something else: 1 read to go through it, 1 write to change it, and a card in front of every one of those changes.
Open the payment. Check it against something else. Write the change. Move to the next one. That is the MOCO afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a payment until you approve it.
What it can do is exactly what MOCO exposes to an account you authorise and nothing beyond it: 2 operations, 1 read and 1 write. In practice that means it can create a payment, and work across the payments and tasks.
The MOCO API stops at MOCO. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.
Does it read the payments or ask you for them?
1 of the 2 operations is a read.
Your account, not a guess at it: a companion can get a task, and the full list below is the whole list, with nothing inferred from MOCO's documentation.
The payments are what most of this inventory is about, alongside the tasks. A companion can hold all 2 of these operations and forty open tabs in the same pass, which is how an afternoon of MOCO admin becomes a queue you review.
- Get Task
What happens before it can create payment?
The one write operation there is waits for you.
A companion can create a payment, and each one is staged on an approval card first: you see the payment, the field and the new value before it lands in MOCO.
Nothing in MOCO is sent, changed or deleted on your behalf without that click, and a rejected card leaves the payment exactly as it was. The gate is the same one on every surface, described at security.
- Create Payment
Does the payment sweep have to be asked for every time?
Yes.
Saved as a routine, the MOCO payments pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.
The operations playbook catalogues the other recurring shapes of the planning, the MOCO payments sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents