Add Inception to your Vercel storefront in one click.
Connect Vercel and we provision everything, then open a pull request that drops the middleware into your repo — catalog route-through enabled, SDK pinned. Merge it and you’re live at the edge. No config to hand-write.
Connect. Merge. Live.
The OAuth installer does the provisioning and opens the pull request. You review a clean diff and merge it — there’s nothing to wire up by hand.
Everything works together. Nothing to pick.
The default install wires every layer as one system — there are no parts to choose and nothing to assemble. It just runs.
Agent detection
AI traffic identified at the edge in under 5 ms. Human visitors pass through untouched.
Catalog route-through
Your real, normalized catalog served from your own domain when an agent asks for it.
Trace beacon
One component in your layout stitches agent-driven arrivals into your compounding intent graph.
MCP auto-proxy
Your /mcp route is signed and proxied to the hosted MCP backend automatically — for Claude clients.
Drop-in for the Vercel + Next.js stack.
Next.js 14+ App Router
Runs at the Vercel edge. Next.js 13 Pages Router works through the same middleware — no shim required.
Zero impact on humans
Detection is local pattern matching: under 2 ms of overhead and no external calls for human traffic.
Fully reversible
Remove the middleware and the env vars; your site reverts to its default behavior on the next deploy.
The how, and the why.
The integration is one click. When you want the technical detail or the full positioning, both are one link away.
Connect Vercel. Merge the PR. You’re live.
The one-click installer provisions your env vars and Edge Config and opens the pull request for you. Merge it, and your storefront is agent-ready at the edge.