LogMan.io REST API (`lmio-rest-api`)¶

The REST API skill is the generic bridge from the sandbox to a live LogMan.io instance. Other skills (query, detection engineering) build on it.


Skill name	`lmio-rest-api`
Library path	`/AI/Skills/lmio-rest-api/SKILL.md`
Share	`lmio` → credentials at `/workspace/lmio/{instance}.json`

What it is for¶

Authenticated HTTP calls to LogMan.io microservices (through the instance URL / NGINX front door)
Tenant discovery
Any “call this API” task that is not covered by a more specific skill’s workflow
Supporting scripts used by lmio-query, detection engineering, and operations

Credentials and instance files¶

Each instance the agent may call is described by a JSON file on the lmio share:

/workspace/lmio/{instance}.json   # BASE_URL + API_KEY

The API key is sent in the Authorization header. Keep keys on the share; do not paste them into chat unnecessarily.

Shipped scripts¶

Skill docs and references live in the Library; run scripts from the sandbox Library mount:

/library/AI/Skills/lmio-rest-api/scripts/

Do not library_read a script and copy it into /workspace just to execute it.

Script	Role
`lmio-api-get-tenants.py`	List tenants (`GET /api/seacat-auth/tenant`)
`lmio-api.py`	General-purpose authenticated CLI (method, path, body, output format)

Example:

python3 /library/AI/Skills/lmio-rest-api/scripts/lmio-api-get-tenants.py mylmio

python3 /library/AI/Skills/lmio-rest-api/scripts/lmio-api.py mylmio \
  GET /api/lmio-chart/mytenant/datasources

Output and context cost¶

The CLI defaults to ZON output (Zero Overhead Notation) so large API responses consume fewer tokens in the model context than pretty JSON. Use pretty JSON only when a human must read the raw payload; write large bodies to /workspace files instead of dumping them into the tool result.

Request bodies¶

Prefer passing JSON bodies through shell_exec stdin (or a file prepared with write_file) instead of embedding huge JSON in the command string. That avoids quoting failures and keeps commands readable.

References in the Library¶

Under /AI/Skills/lmio-rest-api/references/ the skill ships endpoint notes, API key management hints, and examples (for example sending email through messaging integrations). Activate the skill and library_read those paths when needed.

LogMan.io REST API (lmio-rest-api)¶