Vercel can send your project's request logs to any HTTPS endpoint. Point a drain at LogZuno and every request that matters for AI visibility is classified and verified, with no change to your code. Drains are available on Vercel's Pro and Enterprise plans (source: Vercel drains docs, checked 23 October 2026).
Set up the drain
- In LogZuno, create a key with the Server traffic (AI visibility) scope under Project settings → API keys.
- In Vercel, open Team Settings → Drains and click Add Drain.
- Choose the Logs data type, give the drain a name and select the projects to drain.
- Under Custom Endpoint, set the URL to
https://api.logzuno.app/v1/drains/vercel. - Choose JSON or NDJSON: LogZuno accepts both.
- Under Custom Headers, add
Authorization: Bearer YOUR_SERVER_KEY. - Leave sampling at 100% and save.
Within a few minutes, requests from AI assistants and crawlers appear on your project's AI visibility page.
What LogZuno keeps
LogZuno reads the request record of each log line (method, host, path, status, user agent, client IP and referrer) and keeps only page requests from anything that isn't a mainstream browser, plus robots.txt, llms.txt and sitemaps. Several log lines from the same request count once. Build logs and function output are ignored.
To also keep browser page loads, which shows how many never ran your analytics script, use https://api.logzuno.app/v1/drains/vercel?all=1 as the URL. That uses more of your allowance.
When you reach the allowance
LogZuno answers drain deliveries with 200 OK, as Vercel requires, even when your organisation has used its server-request allowance for the period. The requests over the allowance are dropped, and LogZuno emails you at 80%, 90% and 100% so it never happens by surprise.