Agentset StrawberryIngest jobs, namespaces and search namespaces, worked for you
Hand a companion the outcome. It reads the Agentset ingest jobs, does the 3-operation version of the job, and stops for your click on anything that changes a record.
Open the ingest job. Check it against something else. Write the change. Move to the next one. That is the Agentset afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a ingest job until you approve it.
What it can do is exactly what Agentset exposes to an account you authorise and nothing beyond it: 3 operations, 1 read and 2 writes. In practice that means it can create a namespace and create an ingest job, and work across the ingest jobs, namespaces and search namespaces.
The Agentset API stops at Agentset. 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.
Where do the ingest jobs come from?
1 of the 3 operations is a read.
Your account, not a guess at it: a companion can agentset search namespace, and the full list below is the whole list, with nothing inferred from Agentset's documentation.
The ingest jobs are what most of this inventory is about, alongside the namespaces. A companion can hold all 3 of these operations and forty open tabs in the same pass, which is how an afternoon of Agentset admin becomes a queue you review.
- Agentset Search Namespace
What happens before it can create namespace?
All 2 write operations wait for you.
A companion can create a namespace and create an ingest job, and each one is staged on an approval card first: you see the ingest job, the field and the new value before it lands in Agentset.
Nothing in Agentset is sent, changed or deleted on your behalf without that click, and a rejected card leaves the ingest job exactly as it was. The gate is the same one on every surface, described at security.
- Create Namespace
- Create Ingest Job
What does the recurring ingest jobs pass look like?
Yes.
Saved as a routine, the Agentset ingest jobs 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 Agentset ingest jobs 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