---
title: "Deploy to Vercel"
description: "Push your changes to redeploy the feedback API so the llms.txt and markdown docs endpoints are live at your public URL."
canonical_url: "https://vercel.com/academy/agent-friendly-apis/deploy-your-docs"
md_url: "https://vercel.com/academy/agent-friendly-apis/deploy-your-docs.md"
docset_id: "vercel-academy"
doc_version: "1.0"
last_updated: "2026-04-11T17:57:45.329Z"
content_type: "lesson"
course: "agent-friendly-apis"
course_title: "Agent-Friendly APIs"
prerequisites:  []
---

<agent-instructions>
Vercel Academy — structured learning, not reference docs.
Lessons are sequenced.
Adapt commands to the human's actual environment (OS, package manager, shell, editor) — detect from project context or ask, don't assume.
The lesson shows one path; if the human's project diverges, adapt concepts to their setup.
Preserve the learning goal over literal steps.
Quizzes are pedagogical — engage, don't spoil.
Quiz answers are included for your reference.
</agent-instructions>

# Deploy to Vercel

# Deploy Your Docs

You deployed the starter project back in lesson 1.1. Since then, you've built the data utility, the feedback endpoints, the summary route, and all the agent-friendly docs. None of that is live yet. Your Vercel deployment still has the stubs.

Time to ship.

## Outcome

Push your changes to redeploy the feedback API so your llms.txt, docs, and feedback endpoints are live at your public URL.

## Fast Track

1. Commit your changes and push to your repo
2. Vercel redeploys automatically
3. Curl your live `/llms.txt`, `/api/docs.md`, and `/api/feedback` endpoints to confirm they work

## Push and redeploy

Since your project is already connected to Vercel from the deploy button in lesson 1.1, every push to `main` triggers a new deployment automatically. Commit your latest changes and push:

```bash
git add -A
git commit -m "feat: add feedback API, docs, and llms.txt endpoints"
git push
```

Head to your Vercel dashboard and you'll see the deployment building. Once it finishes, your live URL has everything.

## Try It

Let's verify that the agent-friendly endpoints are live. Replace the URL below with your actual deployment URL.

Fetch the llms.txt file:

```bash
curl https://your-project-name.vercel.app/llms.txt
```

You should see the plain-text markdown with the project name, summary blockquote, and links to your endpoints.

Fetch the API docs via the markdown endpoint:

```bash
curl https://your-project-name.vercel.app/api/docs.md
```

The full markdown documentation should come back with all the endpoint signatures, parameter tables, and examples.

Fetch some feedback:

```bash
curl https://your-project-name.vercel.app/api/feedback
```

You should see the JSON array of seed feedback entries.

**Troubleshooting:**

- If you get a 404 on `/llms.txt`, check that the folder is named exactly `llms.txt` inside `app/`. The deployment mirrors your local file structure.
- If the deploy fails with a build error, check the Vercel build logs for TypeScript errors. The production build runs `next build`, which is stricter than the dev server about type checking.

\*\*Warning: Data doesn't persist in production\*\*

The feedback data lives in a JSON file that gets read at runtime. Since Vercel Functions are serverless, any POST requests that write to that file won't persist across invocations. The function's filesystem resets on each cold start. This is fine for the course because the seed data is what matters for testing. In a real app, you'd use a database.

## Commit

You already committed and pushed in the exercise above. If you made any additional fixes during troubleshooting, commit those too:

```bash
git add -A
git commit -m "fix: resolve build issues for production deploy"
git push
```

## Done-When

- [ ] Your latest code is pushed and Vercel has redeployed
- [ ] Curling `<your-url>/llms.txt` returns the plain-text llms.txt content
- [ ] Curling `<your-url>/api/docs.md` returns the full markdown API documentation
- [ ] Curling `<your-url>/api/feedback` returns the seed feedback data as JSON

## Solution

No new code is required for this lesson. Push triggers a redeploy:

```bash
git push
```

If your project builds and serves correctly on localhost, it will work on Vercel. The framework detection is automatic, and Next.js App Router projects require no additional configuration files.


---

[Full course index](/academy/llms.txt) · [Sitemap](/academy/sitemap.md)