Skills for coding agents

Install the Nuitee Connect skill in Cursor or Claude Code when the agent should write a booking app in your repo. The skill keeps the API key on your server.

Building with AI has two pages. Use this skill when the agent should generate the app. Use the MCP server when the agent should call search, rates, and the rest of the API itself.

	Skill	MCP server
What it does	Teaches the agent how to build your app	Lets an agent call Nuitee Connect live
Install	Clone into the tool's skills folder	Add the MCP URL
API key	Server env var. Shared sandbox key if you do not set one	`X-API-Key` header. Send the shared sandbox key for sample calls
Stays current across chats	Yes	Yes, for tool calls

A one-shot paste that builds a hotel site still lives in the vibe-coding prompt. The skill is the same hotel flow, installed so later chats do not need the paste.

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 calls should hit your account. Sandbox keys start with sand_ or sandbox_. Production keys start with prod_. With no key of your own, 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-travel

Reload 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-travel

For 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_ca230deb-5a6b-42e7-bb72-869facd8892b

That value is the shared sandbox key. Replace it with your own key before a production deploy. On a host (Vercel, Netlify, Cloud Run), set LITEAPI_API_KEY in the project's environment variables.

If the agent also uses the MCP server and a tool call returns 401 unauthorized, the connector has no key. Add the same sandbox key on the X-API-Key header in the MCP config. Do not replace the API with a local mock.

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 bookingId and hotelConfirmationCode.

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. Go back to the hotel page and pick 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.

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.travel or book.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