> For the complete documentation index, see [llms.txt](https://docs.hypertune.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hypertune.com/integrations/vercel-edge-config-integration.md).

# Vercel Edge Config integration

You can use Vercel Edge Config to initialize the Hypertune JavaScript SDK with near-zero latency in Vercel's edge environment.

To get started, follow the [Vercel Edge Config section in the Next.js quickstart](https://docs.hypertune.com/integrations/pages/C9d97myMYEqew55k8ZNf#id-6.-optional-use-vercel-edge-config).

Or deploy our [example app using Next.js with Vercel Edge Config](/example-apps/next.js-and-vercel-example-app.md).

Check out the [Hypertune integration in the Vercel marketplace](https://vercel.com/integrations/hypertune).

Read our [blog post](https://www.hypertune.com/blog/feature-flags-and-ab-testing-at-the-edge-with-hypertune-nextjs-and-vercel) on how we've partnered with Vercel.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.hypertune.com/integrations/vercel-edge-config-integration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.