Byte Engine Docs
Inspectorhttp

Drain message publications

GET/messages

Returns message publication ranges observed since the previous call. This operation drains the shared inspector cursor. It preserves sequence order within each typed route but does not define ordering between routes. Message payloads remain opaque.

Response Body

application/json

curl -X GET "https://example.com/messages"
{  "messages": [    {      "topic": 3,      "scope": "world",      "type": "byte_engine::gameplay::transform::TransformationUpdate",      "first_sequence": 12,      "count": 2    }  ]}

List entities GET

Returns factory-created entities known to the shared message bus. Each result includes the numeric handle used as a message target and every complete Rust type name associated with the entity. Use either `type` or its compatibility alias `class` to filter by one complete Rust type name.

Post a message POST

Publishes one supported targeted message to the running application. The current protocol accepts only `TransformationUpdate`. The request object must contain exactly `type`, `target`, and `payload`.