Generate a Next.js route that serves /llms.txt.
—
Plugsky is OpenAI-compatible with flat-rate plans — see pricing or start on the free plan (2 free models, no card).
This page is a short step-by-step guide for Next.js developers adding Plugsky to a site, including the llms.txt use case. It walks through three steps: creating an API key in the dashboard, configuring a client with the Plugsky base URL, and testing and deploying. The examples use an OpenAI-compatible client, so the same pattern works with other tools. No account is needed to read the guide; building with the API requires a key.
It is a proposed plain-text file placed at a site root to give language models a curated map of important pages. The idea resembles robots.txt but for readable content rather than crawling permission. Adoption is still early, and not every assistant reads it, so treat it as a supplement to good HTML and structured data.
The guide's example uses the OpenAI SDK with a custom base URL, which works in any Next.js runtime, including route handlers and server actions. Keep API keys server-side in environment variables and never expose them to the browser.
Yes. Change the base URL to the Plugsky endpoint and use your Plugsky key; existing OpenAI SDK code works, including streaming, tool calling and JSON mode. The free plan includes 2 free models, and a 14-day full-access trial is available.
Canonical pricing and plans: plugsky.com/#sec-pricing · Terms · SLA · Docs