The ScoreDetect certificates nobody wants to work through
ScoreDetect exposes 2 operations and a companion can work all of them: create a timestamped blockchain certificate and create a certificate from file. Anything that changes a record waits for your click.
Open the certificate. Check it against something else. Write the change. Move to the next one. That is the ScoreDetect afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a certificate until you approve it.
What it can do is exactly what ScoreDetect exposes to an account you authorise and nothing beyond it: 2 operations, no reads and 2 writes. In practice that means it can create a timestamped blockchain certificate and create a certificate from file, and work across the certificates and timestamped blockchain certificates.
The ScoreDetect API stops at ScoreDetect. 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 certificates or ask you for them?
In the tab.
ScoreDetect exposes no read operation to a connected account, so a companion opens ScoreDetect in the session you are already signed into and reads the screens you would.
The certificates are what most of this inventory is about, alongside the timestamped blockchain certificates. A companion can hold all 2 of these operations and forty open tabs in the same pass, which is how an afternoon of ScoreDetect admin becomes a queue you review.
What happens before it can create timestamped blockchain certificate?
All 2 write operations wait for you.
A companion can create a timestamped blockchain certificate and create a certificate from file, and each one is staged on an approval card first: you see the certificate, the field and the new value before it lands in ScoreDetect.
Nothing in ScoreDetect is sent, changed or deleted on your behalf without that click, and a rejected card leaves the certificate exactly as it was. The gate is the same one on every surface, described at security.
- Create Timestamped Blockchain Certificate
- Create Certificate from File
Does the certificate sweep have to be asked for every time?
Yes.
Saved as a routine, the ScoreDetect certificates 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 busywork, the ScoreDetect certificates 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