HOST · Adapter
host-vercel
via Vercel
Deploy + manage projects on Vercel. Git-source mode, env-scope-aware.
@openagentry/adapter-host-vercel npm → — · Install
Use it
# Install
$ npm install @openagentry/adapter-host-vercel
# Or in a workspace registered with the CLI
$ npx agentry init @openagentry/adapter-host-vercel — · Default export
Pattern: lazy
The default export is always a frozen HOSTAdapter
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-host-vercel';
// → hostAdapter — category: 'host', id: 'host-vercel' — · Environment
Configuration
| Variable | Notes |
|---|---|
| OA_VERCEL_TOKEN | Required. |
— · Reported capabilities
What the manifest says
agentry capabilities --json reports these flags from
the package's openagentry.capabilities manifest block.
- deployMode
- git-source
- rollbackMode
- promote
- logsTail
- true
- stateExport
- true
- domainAttachVerification
- true
— · Failure modes
Error codes
10 stable codes this adapter throws. Each has a one-line resolution.
-
E_VERCEL_AUTHVercel token missing or rejected. -
E_VERCEL_NOT_FOUNDVercel project, deployment, or domain not found. -
E_VERCEL_PERMISSIONThe Vercel token lacks permission for the operation. -
E_VERCEL_INVALIDVercel rejected the input. -
E_VERCEL_RATE_LIMITVercel API rate limit reached. -
E_VERCEL_NETWORKNetwork failure reaching Vercel. -
E_VERCEL_UPSTREAMVercel returned a non-2xx HTTP status. -
E_VERCEL_NO_GIT_LINKProject has no git source linked — deploy cannot proceed. -
E_VERCEL_BAD_STATEProject is in a state that doesn't accept this operation. -
E_VERCEL_SCHEMAInput failed Zod validation.