meshmonitor

Use this skill for MeshMonitor API work.

What this skill assumes

• - MeshMonitor exposes its REST API at INLINECODE0
• API auth uses a Bearer token
• Swagger docs are usually available at INLINECODE1
• The installer/user will provide the base URL and token at runtime

First move

1. 1. Confirm the MeshMonitor base URL.
2. Confirm you have a valid API token.
3. Test auth with a lightweight request before doing anything bigger.

Use the helper script:

CODEBLOCK0

If auth fails, stop and ask for a fresh token. Do not guess token format.

Supported API areas

This skill is designed to use as much of the API as practical. Prefer these endpoint groups when available:

• - info → API/version metadata
• INLINECODE3 → list nodes, inspect node, position history
• INLINECODE4 → channel configuration
• INLINECODE5 → telemetry history and summaries
• INLINECODE6 → mesh messages/history
• INLINECODE7 → route/path history
• INLINECODE8 → network-wide statistics/topology summaries
• INLINECODE9 → raw packet logs
• INLINECODE10 → forecast/solar views when enabled

Workflow

1) Validate docs + auth

• - Read the live OpenAPI/Swagger if available.
• Run a single authenticated request.
• If docs and live behavior disagree, trust live behavior and note the mismatch.

2) Prefer read-heavy discovery first

Before building reports or automation:

• - inspect API info
• list nodes
• inspect one known node
• sample messages/telemetry/network endpoints

This tells you which features are populated on the actual instance.

3) Produce structured outputs

When the user asks for a report, return concise structured sections such as:

• - active nodes
• stale/offline nodes
• recent traffic
• telemetry anomalies
• route findings
• network health

4) Be careful with time filters

Many MeshMonitor endpoints are history-oriented. Prefer explicit params like:

• - INLINECODE11
• INLINECODE12
• INLINECODE13
• INLINECODE14
• INLINECODE15

When unsure, start with conservative limits.

Files in this skill

• - references/api-notes.md → known API groups and verified live behavior notes
• INLINECODE17 → helper CLI for authenticated calls, endpoint discovery, message sending, and report generation

Read references/api-notes.md when you need a quick endpoint map.

Helper CLI coverage

The helper now has first-class commands for:

• - INLINECODE19
• INLINECODE20
• INLINECODE21
• INLINECODE22
• INLINECODE23
• INLINECODE24
• INLINECODE25
• INLINECODE26
• INLINECODE27
• INLINECODE28
• INLINECODE29
• INLINECODE30
• INLINECODE31
• INLINECODE32
• INLINECODE33
• INLINECODE34
• INLINECODE35
• INLINECODE36
• INLINECODE37
• INLINECODE38
• INLINECODE39
• INLINECODE40
• INLINECODE41
• INLINECODE42
• INLINECODE43
• INLINECODE44

Recommended usage patterns

Quick health check

CODEBLOCK1

Inspect a node

CODEBLOCK2

Browse mesh traffic

CODEBLOCK3

Inspect topology

CODEBLOCK4

Send a message

CODEBLOCK5

Explore live API surface

CODEBLOCK6

Troubleshooting

Unauthorized / invalid token

• - MeshMonitor tokens are per-user and can be revoked by regeneration.
• Test with the exact bearer token the user provides.
• If the token fails, ask for a fresh token from MeshMonitor user settings.

Docs page works but API fails

• - The docs page is usually public/static.
• The API still requires Bearer auth.
• Verify the Authorization: Bearer ... header is present.

Endpoint exists in docs but returns empty data

That usually means the instance has the feature but no stored data yet. Report that clearly instead of treating it as a hard failure.

Deliverables this skill is good at

• - mesh health summaries
• node inventories
• message/telemetry digests
• troubleshooting whether MQTT / routing / node visibility is working
• reusable scripts or automations that call MeshMonitor cleanly