Vercel AI SDK · drop-in tool() wrappers.
Fleet's Vercel AI SDK adapter ships scope-checked tool() wrappers and a server-side verifier middleware. Intended to be a one-import switch for teams already on the AI SDK — same agent-action envelope shape as MCP, OpenAI, and Anthropic adapters.
What it does
The Vercel AI SDK has converged on a clean tool() primitive that serializes naturally across providers. The adapter wraps it once:
ocTool({verb, parameters, execute})— a scope-aware replacement fortool()that pulls the live delegation from request context, verifies the exercised scope, and runsexecuteonly if admissible.- Server middleware that turns each successful call into a signed agent-action envelope (kind 30084), pushes it to your audit bundle, and surfaces it to
fleet.ochk.iofor the operator dashboard. - Provider-agnostic — your underlying model can be Anthropic, OpenAI, Cohere, or anything the AI SDK speaks. The envelope shape is the same.
Why this might land first
The Vercel AI SDK is the Express of the agent-stack era — small surface, viral adoption, clean tool primitive. A single adapter covers a large fraction of teams shipping production agents. Design-partner demand for this adapter will likely pull it ahead of the per-provider variants.
Status
Adapter package: @orangecheck/agent-vercel@0.2.0 is on npm. Source in oc-packages/agent-vercel. MIT. Ships stampToolCall, postActionToFleet, and the high-level ocTool({verb, parameters, execute}) wrapper — provider-agnostic; underlying model can be Anthropic, OpenAI, or anything the AI SDK speaks.
What Fleet adds on top: the managed signing pipeline, OC Stamp anchoring, Nostr publishing, audit-bundle assembly, and the operator dashboard.
Already using the package?
Fleet adds the managed pipeline (OC Stamp anchoring, Nostr publishing, audit-bundle assembly, operator dashboard) on top of the open package. Design partners pair with an OrangeCheck engineer for the integration.