Create integration in Rockset, on your say-so
A companion works the 3 operations your Rockset account exposes. It can create an integration and create an API key, and every one of those waits on an approval card showing the api key before it changes.
Open the api key. Check it against something else. Write the change. Move to the next one. That is the Rockset afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a api key until you approve it.
What it can do is exactly what Rockset exposes to an account you authorise and nothing beyond it: 3 operations, no reads and 3 writes. In practice that means it can create an integration, create an API key and add documents, and work across the api keys, documents and integrations.
The Rockset API stops at Rockset. 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.
Which Rockset api keys does a companion see?
In the tab.
Rockset exposes no read operation to a connected account, so a companion opens Rockset in the session you are already signed into and reads the screens you would.
The api keys are what most of this inventory is about, alongside the documents. A companion can hold all 3 of these operations and forty open tabs in the same pass, which is how an afternoon of Rockset admin becomes a queue you review.
Can it change a api key without asking?
All 3 write operations wait for you.
A companion can create an integration, create an API key and add documents, and each one is staged on an approval card first: you see the api key, the field and the new value before it lands in Rockset.
Nothing in Rockset is sent, changed or deleted on your behalf without that click, and a rejected card leaves the api key exactly as it was. The gate is the same one on every surface, described at security.
- Create Integration
- Create API Key
- Add Documents
Can the api keys pass run every Monday?
Yes.
Saved as a routine, the Rockset api keys 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 infrastructure checks, the Rockset api keys 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