mikro-doc
Generate a self-contained offline HTML API reference for RouterOS.
Discovers the full RouterOS API tree from a live router via the REST
interface, then produces a standalone HTML document (with search,
sidebar navigation, pagination and example curl commands) and a
Markdown reference — all usable directly from the file:// protocol
without a web server.
mikro-doc --host H --user U --pass P [--store-credentials] [--output-dir DIR] [--endpoints] [--no-docs]
mikro-doc --schema PATH [--output-dir DIR] [--endpoints] [--no-docs]
mikro-doc PATH [--output-dir DIR] [--endpoints] [--no-docs]
mikro-doc --no-fetch [--host H|--schema PATH] [options]
⚠ BIG FAT WARNING
This tool will query your router (potentially hundreds of times) to discover the API structure.
It is designed to be safe and non-intrusive, but the documentation it generates will include actual configuration
information from your router (e.g. interface names, user names). Do NOT share the generated documentation publicy.
It is for your eyes only. If you passed --store-credentials, the credentials will be stored in plaintext in the
output JSON file for future use. You have been warned.
Output
<output-dir>/<router>.schema.json — Full API schema (JSON)
<output-dir>/<router>.index.html — Standalone docs page (works on file://)
<output-dir>/<router>.md — Markdown reference
<output-dir>/<router>_Endpoints.json — Hierarchical endpoints tree (with --endpoints)
<output-dir>/<router>.log — Discovery log
Install
pipx install mikro-doc
This pulls from PyPI, creates an isolated environment, and installs the
mikro-doc command and its dependencies. On macOS, pip without a
virtual environment is blocked by system integrity protection; pipx
is the recommended alternative.
To upgrade: pipx upgrade mikro-doc
Alternatives
pip3 install --user mikro-doc(works on most Linux, blocked on macOS)python3 -m venv /path/to/venv && /path/to/venv/bin/pip install mikro-doc
Requirements
- Python 3.7+
Bundled Data
mikro-doc.hints is bundled inside the package and provides example
values for common RouterOS parameter types. Without it, placeholder values
(<paramname>) will be used in curl examples.
Release files for mikro-doc 1.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| mikro_doc-1.0.3.tar.gz | 34.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mikro_doc-1.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 69.1 kB
Release files / mikro_doc-1.0.3.tar.gz
| Download URL | mikro_doc-1.0.3.tar.gz |
|---|---|
| Size | 34.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0cfd49bef4bfbb09e937544e6723c66371cb4e908a5272a2c86dd7a3f5684c82
|
|
BLAKE2b-256 checksum How to use checksums |
f8182d03b12a606d6535d29add44e673850d49740bd7f4f57bc56e5923fc9664
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 1, 2026.
Transparency logRelease files / mikro_doc-1.0.3-py3-none-any.whl
| Download URL | mikro_doc-1.0.3-py3-none-any.whl |
|---|---|
| Size | 34.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4440d4cc0ad8b051f0655c5024f0280fcb62dd153b8a082340c785f5b37ba102
|
|
BLAKE2b-256 checksum How to use checksums |
4ad6448915d09b59d30253694faffd52e5fb9323492a64dcc0eaa34e156dc16e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 1, 2026.
Transparency log