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

# Ler o inventário

Lista os primeiros 20 itens do seu inventário no console, sem mudar nada. Mostra:

* uma chamada assíncrona da [API de serviços](/documentacao/services.md) com callback;
* como tratar `ok = false` e o erro de envio;
* `ui.text` com o texto atualizado por `:label`.

Salve como `inventory_browser.lua` na pasta de scripts e ligue na aba **Scripts**.

```lua
-- @name Inventory API example
-- @description Lists real Perfect inventory items without changing them
-- @author Perfect
-- @version 1.1
ui.group("Inventory", "Real items from Perfect")
local status = ui.text("Press Refresh to read your inventory")
local busy = false
ui.button("Refresh", "Print the first 20 items in the console", function()
    if busy then return end
    busy = true
    local request, err = inventory.list({limit=20}, function(r)
        busy = false
        if not r.ok then status:label(r.error); return end
        status:label(tostring(r.total).." items")
        for _, item in ipairs(r.items) do
            print(item.id, item.name, item.custom_name, "equipped", item.equipped)
        end
    end)
    if not request then busy=false; status:label(err) end
end)
```


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.perfectcs2.com/exemplos/inventario.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.