> For the complete documentation index, see [llms.txt](https://docs.ai.neevcloud.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ai.neevcloud.com/api-reference/inventory.md).

# Inventory API

The Inventory API provides **real-time visibility into deployable compute** on the NeevAI platform. Use it to discover which GPU and CPU SKUs are currently available before you create a GPU Instance or model deployment, to look up the exact resource shape behind a configuration, and to register for an email alert when scarce hardware frees up.

The public endpoints surface only the SKUs that are deployable right now, so the inventory you see reflects what you can actually schedule rather than the full hardware catalog.

## What you can do

* **List inventory** — enumerate the deployable GPU/CPU inventory items currently available for scheduling.
* **GPU configuration details** — look up a GPU configuration by `config_id` to read its VRAM, CPU, and related presets used when sizing a deployment.
* **VM configuration details** — look up a VM configuration by `config_id`.
* **Availability notifications** — register to be emailed when a specific GPU configuration (for example, an H200 preset) becomes available, and list your pending notification requests.

Use the interactive reference below to inspect the response schemas and try each endpoint directly.


---

# 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.ai.neevcloud.com/api-reference/inventory.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.