> 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/readme.md).

# Guides

Build and operate your platform's API integration with Nerova's API-first SaaS. These guides explain tasks; reference material for individual endpoints stays authoritative in the [API documentation](https://docs.nerovasystems.com/documentation).

The first release is for Platform accounts serving human medical/clinic, salon/barber, and beauty businesses including nails, not veterinary or other verticals. Vaccination-specific automation and the deprecated customer WhatsApp payment flow are outside the offer; Nerova SaaS billing is not. See [First-release scope](https://docs.nerovasystems.com/documentation/console/platform-access#first-release-scope) for source-versus-release caveats.

## New to Nerova? Follow the journey

Start with [Platform access](https://docs.nerovasystems.com/documentation/console/platform-access): Nerova approves your platform, which then gets a Live key and a free testing allowance before any commercial agreement.

The [zero-to-live walkthrough](/guides/zero-to-live/zero-to-live.md) takes you from your first API call to a live merchant with that one Live key. No other key type exists.

## Already integrated? Pick a task

Each guide covers one job end to end.

| Operate                                                                                                           | Observe                                                                     |
| ----------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------- |
| [Read and steer conversations](/guides/operate-the-digital-employee/conversations.md)                             | [Audit work and receipts](/guides/observe-and-account/work-and-receipts.md) |
| [Send customer notifications](/guides/operate-the-digital-employee/notifications.md)                              | [Report on performance](/guides/observe-and-account/performance.md)         |
| [Work the attention queue](https://github.com/Nerova-Systems/Project-Songbird/tree/main/docs/guides/attention.md) | [Monitor incidents](/guides/observe-and-account/incidents.md)               |
| [Manage employee memory](/guides/operate-the-digital-employee/memory.md)                                          | [Meter usage for billing](/guides/observe-and-account/usage.md)             |
| [Set the autonomy mandate](/guides/operate-the-digital-employee/mandate.md)                                       |                                                                             |

| Provision                                                               | Build well                                                        |
| ----------------------------------------------------------------------- | ----------------------------------------------------------------- |
| [Provision and activate tenants](/guides/provision/partner-playbook.md) | [Handle errors and retries](/guides/build-well/error-handling.md) |
| [Go-live checklist](/guides/provision/go-live.md)                       | [Receive events with webhooks](/guides/build-well/webhooks.md)    |


---

# 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/readme.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.