Byte Engine Docs
Inspectorhttp

Close the application

DELETE/

Publishes an application close request. The HTTP response confirms publication, not process termination.

Response Body

curl -X DELETE "https://example.com"
Empty

Capture screenshots from the same frame POST

Captures up to 16 images, from any sinks and capture points, in one graphics frame, so you can compare targets that belong together. Each capture takes the same fields as the `GET /screenshots` query. The response is `multipart/form-data` with one part per capture, in request order. Each part is named by its zero-based capture index, has a file name built from the capture, and carries the same `Content-Type` and `X-Byte-Engine-*` headers as a single-image response, except `X-Byte-Engine-Frame`, which the response itself carries. If any capture fails, the request fails, and the error message starts with the failing capture index.

Summarize performance metrics GET

Returns the distribution of every metric over the retained ticks, in milliseconds. The engine retains the last 1024 ticks. CPU metrics are named after the engine `tracing` spans they sum, such as `GraphicsApplication::tick` for the whole tick or `Renderer::prepare` for frame preparation. GPU metrics are `frame` for all GPU work of a frame, `scene.<manager>` for each scene pipeline manager, `pass.<name>` for each post-scene render pass, and `stage.<name>` for each stage a scene pipeline or pass times inside its own commands, such as the visibility pipeline's `stage.shadow-maps` and `stage.material-evaluation`, with `@<sink>` appended on sinks after the first. A stage that recorded nothing on a frame has no value for it. GPU times arrive once the frame that recorded them completes, so the newest frames in flight have none yet. `delta` is the frame delta the application clock advanced by.