Recued
Menu
← Back to packs

Persistent Volume Content - E2B

by recued-core v1 app_pack 5 views

E2B volume path metadata, directory listing and creation, file download, and path deletion operations. Generated from the immutable official spec/openapi-volumecontent.yml contract at E2B commit 7474d904a2f6056f9528e73baf697368e03bf6ab. This leaf carries 6 of the suite's 72 admitted operations. Pick the volume-scoped E2B content connection whose token returned by create/get volume is stored as Bearer <VOLUME_TOKEN> in Authorization. JSON request documents are sent verbatim, scalar integer selectors use exact decimal strings, unsafe JSON response integers remain exact strings, reads are uncached, private reads are marked sensitive-read, every mutation requires approval, and no sandbox or infrastructure object is misrepresented as a task, note, or project Source.

What this pack installs

  • e2b-volume-content Ingredient

Trust & control

What installing this whole pack would let it do. Recued grants these permissions at install — review them there before approving.

What it's allowed to do

Destructive Web APIs e2b-volume-content external change
Read: volumes.get_volumecontent_volume_id_dir · Asks approvalWrite: volumes.post_volumecontent_volume_id_dir · Always asksRead: volumes.get_volumecontent_volume_id_file · Asks approvalRead: volumes.get_volumecontent_volume_id_path · Asks approvalWrite: volumes.patch_volumecontent_volume_id_path · Always asksDestructive: volumes.delete_volumecontent_volume_id_path · Always asks

Data it touches

SurfacesWeb APIs

About

Tags

pack:e2be2bcloud-sandboxesvolumesstoragefilesapicomposition