v1 · design partnersoc · console
managed agent + pledge
§ integrations / vercel ai sdk

Vercel AI SDK · drop-in tool() wrappers.

Console'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.

· in design· targeted Q3 2026 · likely first follow-on after MCP given AI SDK adoption

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 for tool() that pulls the live delegation from request context, verifies the exercised scope, and runs execute only 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 console.ochk.io for 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: design in progress in oc-packages. Pulls forward when the first design partner asks for it. The primitives (@orangecheck/agent-core, @orangecheck/agent-signer) are stable; this is the AI-SDK-shaped wrapper around them.

Want this adapter sooner?

Adapter prioritization is design-partner-driven. Tell us your stack, the volume, and the compliance bar — adapters that named partners need move from "planned" to "shipping" inside a quarter.