# GET /ui

> Talos next · Since 0.6

An exact read, like `GET /entities`: it takes `?at=` and reports the state it answered at, so an agent that pressed something, waited for the stamp, and then read the tree is looking at the tick it thinks it is.

A UI tree read half a tick after an activation is exactly the kind of thing that makes an agent chase a bug that was never there. # The cap At most `UI_TREE_MAX_NODES` nodes come back; past that the read is a 400 naming `?id=` and `?depth=`, the two filters that make it answerable. The alternative was a multi-megabyte response an agent did not ask for and mostly cannot use — see the constant for why this is a cap rather than paging.

## Example

```sh
curl "http://127.0.0.1:7700/ui"
```

Start a server with `argus run --serve`; the port is `--port` (7700 by default). The request and response fields are in the query API guide.