STORAGE · Adapter
storage-vercel-blob
via Vercel Blob
Vercel-managed object storage. Public + private support.
@openagentry/adapter-storage-vercel-blob npm → — · Install
Use it
# Install
$ npm install @openagentry/adapter-storage-vercel-blob
# Or in a workspace registered with the CLI
$ npx agentry init @openagentry/adapter-storage-vercel-blob— · Default export
Pattern: lazy
The default export is always a frozen STORAGEAdapter
with static category + id. Methods read env on
first call and cache the underlying instance. Missing config produces an
AgentryError at the use-site, not at import.
import default_ from '@openagentry/adapter-storage-vercel-blob';
// → storageAdapter — category: 'storage', id: 'storage-vercel-blob'— · Environment
Configuration
| Variable | Notes |
|---|---|
| BLOB_READ_WRITE_TOKEN | Required. |
— · Reported capabilities
What the manifest says
agentry capabilities --json reports these flags from
the package's openagentry.capabilities manifest block.
- transport
- https
- publicAccess
- true
- privateAccess
- true
— · Failure modes
Error codes
6 stable codes this adapter throws. Each has a one-line resolution.
-
E_VERCEL_BLOB_INVALID_KEYObject key violates Blob naming rules. -
E_VERCEL_BLOB_NOT_FOUNDObject not found in Blob. -
E_VERCEL_BLOB_PERMISSIONBLOB_READ_WRITE_TOKEN lacks permission. -
E_VERCEL_BLOB_NETWORKNetwork failure reaching Vercel Blob. -
E_VERCEL_BLOB_UPSTREAMVercel Blob returned a non-2xx response. -
E_VERCEL_BLOB_CONFIG_INVALIDAdapter config failed validation.