Introduction

Nerve PMS is a hotel Property Management System reimagined for a world where AI agents — not just people — discover, book, and operate stays.

It is built on Open Hotel Protocols: an open, machine-readable interface layer so agents and partner systems can read availability, transact, and orchestrate the guest journey end to end.

Why another PMS#

Hotel software was designed around a human at a terminal. Every integration is a bespoke bridge, every partner a separate contract, and every new channel another sync to babysit. That model does not survive contact with agents that expect to read a schema, reason about it, and act.

Nerve PMS starts from the opposite premise: the interface is the product. Property data, rates, availability and the reservation lifecycle are exposed as one coherent, versioned, machine-readable contract — the same contract the front desk UI is built on.

Note

This documentation is published from the Nerve PMS CMS and updates without a redeploy. Topics that are not yet listed are simply not-yet-documented.

Where to go next#

If you are building against the API:

• Quickstart — make your first call.
• Open Hotel Protocols — the interface layer.

If you are going to use Nerve to run a hotel:

• Sign in and find your way around — the sidebar, the dashboard, and why your menu is yours.
• Workspaces, organisations and properties — what you are looking at, and how to switch.
• Why your menu differs from a colleague's — roles, app enablement and context.
• Your first week on Nerve — a sequenced setup, if the property is yours to open.

If you are starting a shift today:

• Front Desk overview — the module you will live in.