AI SDK gateway compatibility
passedai ^7.0.78 is installed and compatible with provider/model gateway routing.
Page guide
BrowserOps proves what happened in the browser. Public reads stay open; trusted-domain execution uses the configured platform key path.
Public-safe diagnosis for the browser evidence pipeline: Cloudflare execution and persistence, trace delivery, event recovery, integration handoffs, and Vercel AI Gateway readiness.
Run registry
Cloudflare D1 stores run metadata and Cloudflare R2 stores browser artifacts.
Browser runtime
Cloudflare Browser Run configured
Trace HTTP
BrowserOps emits protected, public-safe trace lifecycle evidence through the Trace HTTP contract.
Event storage
Cloudflare BrowserOps is configured; BrowserOps events are written to the D1 event log and mirrored in process memory.
AI Gateway
AI Gateway is partially configured; BrowserOps can show diagnosis but should not depend on model calls yet.
Suite registry
Canonical BrowserOps integration registry with service-owned handoff paths.
AI Gateway is partially configured; BrowserOps can show diagnosis but should not depend on model calls yet.
AI SDK
^7.0.78
gateway-compatible provider/model routing
Auth mode
vercel oidc runtime
Values are detected server-side and never exposed.
Default model
missing
Expected format: provider/model.
ai ^7.0.78 is installed and compatible with provider/model gateway routing.
The app is running on Vercel; AI Gateway can use Vercel-managed OIDC at runtime if the project has AI Gateway enabled.
No direct provider API keys were detected in the BrowserOps environment.
No default AI Gateway model is configured. BrowserOps will require callers to provide an explicit provider/model id before making model calls.
BrowserOps lists gaps instead of filling the dashboard with fake successful runs.