Install the Nuitee Connect skill in Cursor or Claude Code. The agent builds a booking app on the REST API and keeps your API key on the server.
Install the skill once. The next time you ask Cursor or Claude Code for a booking site, it already knows search, prebook, payment, and book.
Building with AI has two main pages. This skill writes the app. The MCP server calls the API. The vibe-coding prompt is the one-shot paste of the same hotel flow.
The skill is a set of instructions the coding agent loads. It writes your app: server routes that call Nuitee Connect, and a UI that never sees the API key. It covers hotels in full, and it knows where flights, experiences, eSIMs, loyalty, and vouchers live.
| Skill | Vibe-coding prompt | MCP server | |
|---|---|---|---|
| What it does | Teaches the agent how to build your app | One-shot paste that builds a hotel site | Lets an agent call your account live |
| Install | Clone into the tool's skills folder | Paste into the chat | Add the MCP URL |
| API key | Server env var. Shared sandbox key if you do not set one | You paste a key into the prompt | X-API-Key header. Send the shared sandbox key for sample calls |
| Stays current across chats | Yes | Only in that chat | Yes, for tool calls |
Use the skill when you want a repo. Use the prompt for a one-off demo. Use MCP when the agent should search or book on your behalf instead of generating code.
Sample
Claude Code built this travel site in a few minutes from the prompt “create a travel booking website with liteapi.”
Prerequisites
- Cursor or Claude Code
- A Nuitee Connect API key if you want calls on your own account. Sandbox keys start with
sand_orsandbox_. Production keys start withprod_. With no key, sample requests use the shared sandbox key below. - Git
Install
Clone the skill into the project you want the agent to work in. The folder name must be liteapi-travel, and that folder must contain SKILL.md.
Cursor
mkdir -p .cursor/skills
git clone https://github.com/liteapi-travel/liteapi-travel-skill.git .cursor/skills/liteapi-travelReload the window. For every project on your machine, clone into ~/.cursor/skills/liteapi-travel instead.
Claude Code
mkdir -p .claude/skills
git clone https://github.com/liteapi-travel/liteapi-travel-skill.git .claude/skills/liteapi-travelFor every project, clone into ~/.claude/skills/liteapi-travel.
API key
Set the key where the server reads it. Do not put it in client code, and do not commit a key that is not the sample key below.
export LITEAPI_API_KEY=sand_your_key_hereIf you do not set a key, the skill uses the shared sandbox key sand_ca230deb-5a6b-42e7-bb72-869facd8892b for sample requests. Replace it with your own key before a production deploy.
If an MCP tool call returns 401 unauthorized, the connector has no key. Send that sandbox key on the X-API-Key header. Do not replace the API with a local mock.
On a host (Vercel, Netlify, Cloud Run), set LITEAPI_API_KEY in the project's environment variables.
Sandbox and production are a pair. A sand_ / sandbox_ key uses the Payment SDK in sandbox. A prod_ key uses live. Start on sandbox.
Ask the agent
Open the project and ask in plain language. You do not paste the API reference. Examples:
- "Build a hotel booking site. Search by city or by vibe, then prebook, pay, and book."
- "Add flights search and checkout next to the hotel flow."
- "Add a page that lists my bookings and cancels one."
The agent should create server routes that proxy Nuitee Connect, then a UI that calls those routes.
What you should get
For a hotel site, the flow is:
- Destination autocomplete, or a free-text search ("search by vibe").
- A hotel list with a live price.
- A hotel page with rates grouped by room.
- Guest name and email, then the Nuitee Connect Payment SDK.
- A confirmation page with
bookingIdandhotelConfirmationCode.
Hosts the agent should use:
| Host | Use |
|---|---|
https://api.liteapi.travel/v3.0 | Places, hotel content, rates, flights, experiences |
https://book.liteapi.travel/v3.0 | Hotel prebook, book, list, retrieve, cancel |
Every call sends X-API-Key from the server. The browser talks only to your own routes.
Try a sandbox booking
- Search a city and open a hotel.
- Pick a rate. Prebook can take 5–10 seconds.
- Enter a guest name and email.
- Pay with
4242424242424242, any CVC, and any future expiry. This card works only with a sandbox key. - Land on the confirmation page. You should see a booking id and a hotel confirmation code.
If prebook fails, the rate sold out. The user goes back to the hotel page and picks another rate. Search price and prebook price can differ. Show the prebook price before payment.
Other products
The skill's hotel wiring is specific. For every other endpoint it uses the MCP server (list_endpoints, then describe_endpoint) instead of guessing a request body. That catalog is the full OpenAPI set.
| Product | Where to read |
|---|---|
| Hotels | Vibe-coding prompt (same flow the skill encodes) |
| Flights | Flights |
| Endpoint index | Endpoints overview |
| Live tool schemas | MCP server |
Security
- Nuitee Connect requests run on your server. The API is not callable from the browser, and a key in frontend code can spend money.
- Do not log the API key, the prebook
secretKey, or card data. - Card numbers go to the Payment SDK. Do not send them to
api.liteapi.travelorbook.liteapi.travel. - Do not book, cancel, or amend from a public route with no check of your own. A client-supplied price is not the price. Confirm from the prebook response.
Source
Skill repository: github.com/liteapi-travel/liteapi-travel-skill
The hotel section matches the vibe-coding prompt. When that prompt changes, update the skill in the same change.

