• VillaSlotDocumentation
  • Introduction
  • Getting Started
  • Agents
    • Claude Code
    • Codex
    • OpenClaw
    • Hermes
  • API
    • Discovery
      • GETGet my context
    • Villas
      • GETList villas
      • POSTCreate a villa
      • GETGet a villa
      • PATCHRename a villa
      • POSTArchive a villa
      • POSTUpload a villa photo
      • GETGet opening hours
      • PUTReplace opening hours
      • GETGet the rate grid
      • PUTReplace the rate grid
      • GETGet availability
    • Bookings
      • GETList bookings over a period
      • POSTCreate a booking
      • GETGet a booking
      • POSTConfirm a booking
      • POSTComplete a booking
      • POSTCancel a booking
      • POSTReschedule a booking
    • Customers
      • GETList customers
      • POSTCreate a customer
      • POSTImport a batch of customers
      • GETGet a customer
      • PATCHUpdate a customer
    • Booking settings
      • GETGet booking settings
      • PATCHUpdate booking settings
  1. Documentation
  2. Agents
  3. Hermes
Buydocschangelogsdemocommunity

Hermes

PreviousOpenClawNextAPI
On this page
Install the skill for Hermes AgentConnect your VillaSlot organizationStart with a read-only reviewReview a rate changeWork with reservationsRecover from errors

Connect Hermes Agent to VillaSlot to review your villa listings and turn operational instructions into API calls. The VillaSlot skill explains available endpoints, booking rules and the limits of what the agent can change.

Install the skill for Hermes Agent

From the workspace where you use Hermes, run:

bash
npx skills add https://github.com/mikecodeur/skills --skill villaslot

Choose Hermes Agent in the installer. Its explicit agent identifier is hermes-agent:

bash
npx skills add https://github.com/mikecodeur/skills --skill villaslot --agent hermes-agent

Install the skill where your Hermes runtime can access it, then open a new session and ask it to use villaslot. If Hermes runs remotely, perform the setup in that environment.

Connect your VillaSlot organization

Open Account → API Keys in VillaSlot and generate a key for the target organization. Make it available securely as VILLASLOT_API_KEY in the agent's execution environment, together with:

bash
export VILLASLOT_BASE_URL="https://www.villaslot.io"

Installing a skill does not configure credentials or grant organization permissions. Keep the key out of committed files and make sure Hermes can reach the API over HTTPS.

Start with a read-only review

Use the villaslot skill. Read my organization context and list its villas.
For each active villa, show opening hours and the durations with a price.
Report missing configuration without changing anything.

Review the organization name and timezone in the result. A villa without a rate for a duration is not bookable for that duration, even if its calendar looks empty.

Review a rate change

Read Garden Villa's complete hourly rate grid. Prepare a change to its
two-hour rate of 1,500,000 IDR. Preserve all other durations and show me
the full proposed grid before applying it.

After you authorize the change, Hermes can submit the replacement grid if the API key belongs to an owner or admin. Rate updates replace the complete collection, so omitted durations would be removed. Existing bookings keep their frozen prices.

Amounts use the currency's minor unit. For IDR, 1500000 means 1,500,000 IDR; for EUR or USD, 2500 means 25.00. The agent should always read the organization's currency rather than assume a conversion.

Work with reservations

Find a three-hour slot at Garden Villa on 2026-10-20 after 09:00,
in the organization's timezone. Show the available options and prices.
Wait for my choice before creating the reservation.

Hermes can then find or create the customer and create an hourly booking with the status you request. Keep the returned booking ID for confirmation, rescheduling, completion or cancellation.

Recover from errors

If a request times out while creating a record, ask Hermes to reconcile the existing records before retrying. Customer batch imports can partially succeed; preserve successful IDs and retry only failed rows.

Recording cash or bank payments, Stripe checkout and refunds are not available through API v1. Confirming a booking does not mark it paid. For endpoint details and supported operations, see the API reference.

See also Agents, OpenClaw, and the Skills CLI documentation.