Vercel AI Gateway and Vercel Sandbox now available on Hermes Agent
Hermes can route inference through Vercel’s model gateway and move command execution into an opt-in cloud microVM, separating model access from the machine where the agent runs.
Hermes now connects to Vercel AI Gateway for **200+ models** with live availability and pricing, no token markup, and centralized request tracking. Its optional Sandbox backend runs commands in an **isolated microVM**.
Use the gateway when you want model choice and spend visibility in one place. Enable terminal.backend=vercel_sandbox when agent commands should run away from your workstation; available runtimes include **Node 24, Node 22, and Python 3.13**.
Hermes now connects to Vercel AI Gateway for **200+ models** with live availability and pricing, no token markup, and centralized request tracking. Its optional Sandbox backend runs commands in an **isolated microVM**. Use the gateway when you want model choice and spend visibility in one place. Enable terminal.backend=vercel_sandbox when agent commands should run away from your workstation; available runtimes include **Node 24, Node 22, and Python 3.13**. Commands remain local by default, so selecting the gateway alone does not isolate execution. Local development with the cloud backend also requires a **VERCEL_OIDC_TOKEN** and a linked Vercel project.
This combines centralized model access and spend visibility with an optional isolated execution backend for Hermes, but keeps the two controls independent: gateway selection does not move commands off the workstation. It turns sandboxing into an explicit deployment choice with runtime, project-linking, and OIDC prerequisites rather than an automatic property of using a managed model gateway.