> For the complete documentation index, see [llms.txt](https://docs.nerovasystems.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nerovasystems.com/guides/verticals/barber.md).

# Barbershop

Build a barbershop platform on Nerova: the leanest certified contract in the catalog, with loyalty as the one retail extra that matters in the chair.

This guide shapes the Provider API contract for a barbershop platform. It is the leanest build in the catalog: no subjects, no intake, fast turnover, and a single retail extra (loyalty) that keeps regulars coming back.

What you declare here:

* The core nine booking capabilities, as every certified platform does.
* `CreateClients`, because most barbershop bookings are new walk-in numbers.
* `ReadLoyalty` and `RedeemLoyalty` so a regular's points surface in the WhatsApp conversation. Gift cards are optional; if your platform sells them, the salon retail flow applies unchanged.

What you leave out is the point: no `IntakeForms`, no subject capabilities, no vocabulary. A haircut needs a name, a number, a service, and a time.

The pages in order:

1. [Declare the shop](/guides/verticals/barber/manifest-and-services.md): a minimal manifest and a catalog built for speed.
2. [Booking and regulars](/guides/verticals/barber/booking.md): the booking round trip and loyalty in conversation.

Prerequisite: a Live API key and a Provider API v1 implementation that passes the core conformance checks, per [zero-to-live](/guides/zero-to-live/zero-to-live.md).

If your platform also runs full salons with consultation intake, read the [salon and nails guide](/guides/verticals/beauty-and-nails.md); the two contracts differ only in what they declare.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.nerovasystems.com/guides/verticals/barber.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.