Recued
Menu
← Back to packs

Persistent Volumes - E2B

by recued-core v1 app_pack 5 views

E2B persistent-volume discovery, creation, lookup, and deletion operations. Generated from the immutable official spec/openapi.yml contract at E2B commit 7474d904a2f6056f9528e73baf697368e03bf6ab. This leaf carries 4 of the suite's 72 admitted operations. Pick the E2B control-plane connection whose E2B API key is stored in X-API-Key. 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-volumes 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-volumes external change
Read: volumes.get_volumes · Asks approvalWrite: volumes.post_volumes · Always asksRead: volumes.get_volumes_volume_id · Asks approvalDestructive: volumes.delete_volumes_volume_id · Always asks

Data it touches

SurfacesWeb APIs

About

Tags

pack:e2be2bcloud-sandboxesvolumesstorageapicomposition