Deployment Connector

Install the hosted context layer

The narrowest useful deployment path is a root-level rewrite for /llms.txt. Use the Vercel file first. Keep the Next.js config version as the fallback.

Preview vs provisioned mode

The deployment connector can return preview files with YOUR_CLIENT_ID placeholders or provisioned files with the real hosted context URL after account setup.

vercel.json

Preferred Vercel path

Smallest possible change. Add this file at the repo root and redeploy.

{
  "rewrites": [
    {
      "source": "/llms.txt",
      "destination": "https://citemap.io/api/v1/context/YOUR_CLIENT_ID"
    }
  ]
}

next.config.mjs

Next.js fallback

Use this when rewrites must live directly in the Next.js config.

import createMDX from '@next/mdx';

/** @type {import('next').NextConfig} */
const nextConfig = {
  pageExtensions: ['js', 'jsx', 'md', 'mdx', 'ts', 'tsx'],
  turbopack: {
    root: process.cwd(),
  },
  async rewrites() {
    return [
      {
        source: '/llms.txt',
        destination: 'https://citemap.io/api/v1/context/YOUR_CLIENT_ID',
      },
    ];
  },
};

const withMDX = createMDX({});

export default withMDX(nextConfig);

1. Generate

Use the deployment connector after a benchmark or after provisioning to get the correct file contents.

2. Deploy

Commit the preferred file, redeploy on Vercel, and make sure the root route exposes the hosted context endpoint.

3. Verify

Rerun the benchmark and confirm that /llms.txt is now live and readable.