Read every entity, draft every field, approve in one pass
Your Fibery, worked while you do something else: 4 reads to go through it, 3 writes to change it, and a card in front of every one of those changes.
Open the entity. Check it against something else. Write the change. Move to the next one. That is the Fibery afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a entity until you approve it.
What it can do is exactly what Fibery exposes to an account you authorise and nothing beyond it: 7 operations, 4 reads and 3 writes. In practice that means it can create multiple entities, create an entity and create an or update entity, and work across the entities, fields and multiple entities.
The Fibery API stops at Fibery. 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 entities or ask you for them?
4 of the 7 operations are reads.
Your account, not a guess at it: a companion can list types, list fields for entity type and list entities, and the full list below is the whole list, with nothing inferred from Fibery's documentation.
The entities are what most of this inventory is about, alongside the fields. A companion can hold all 7 of these operations and forty open tabs in the same pass, which is how an afternoon of Fibery admin becomes a queue you review.
- List Types
- List Fields for Entity Type
- List Entities
- Get or Create Entity
Can it change a entity without asking?
All 3 write operations wait for you.
A companion can create multiple entities, create an entity and create an or update entity, and each one is staged on an approval card first: you see the entity, the field and the new value before it lands in Fibery.
Nothing in Fibery is sent, changed or deleted on your behalf without that click, and a rejected card leaves the entity exactly as it was. The gate is the same one on every surface, described at security.
- Create Multiple Entities
- Create Entity
- Create or Update Entity
Does the entity sweep have to be asked for every time?
Yes.
Saved as a routine, the Fibery entities 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 product and engineering playbook catalogues the other recurring shapes of the engineering admin, the Fibery entities 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