> 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/api-reference/start-here.md).

# Start here

How to use the API reference, where to start for your experience level, and where to check live service status.

Every page that follows is generated from the live `/api/v1` OpenAPI contract: paths, schemas, and error shapes are the contract, not a copy of it. Pick your starting point:

* **New to APIs?** Begin with [Get started](https://docs.nerovasystems.com/documentation/get-started/quickstart), which walks provisioning end to end before you touch a single endpoint.
* **Know REST, new to Nerova?** Skim the [conventions](https://docs.nerovasystems.com/documentation/tenant-api-v1/conventions) (auth header, environments, idempotency, problem details), then call `GET /api/v1/status` from the Status and context page.
* **Already integrated?** Head to the [changelog](https://docs.nerovasystems.com/changelog) for what shipped and what changed.

## Good to know

* One host serves both environments: `https://api.nerovasystems.com`. The key prefix (`nrv_test_` / `nrv_live_`) selects the Test environment or Production.
* Errors return RFC 7807 problem details with a `correlationId`. Quote it when contacting support. The [error catalog](https://docs.nerovasystems.com/documentation/tenant-api-v1/error-catalog) lists every code.
* Live service availability: [status.nerovasystems.com](https://status.nerovasystems.com).


---

# 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/api-reference/start-here.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.