Free Store
Get started

network · wired today

MikroTik RouterOS, wired into your agent workforce

External systems are where agent answers come from. The MikroTik RouterOS connector is one of 222 executable connectors and gives agents 5 read-only tools, with the credential held in the vault and every call receipted.

Connecting MikroTik RouterOS takes one credential

You provide base URL, username, password from your MikroTik RouterOS account; Quox sends it as HTTP basic credentials. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.

Where to get it: MikroTik RouterOS's own API documentation ↗ covers creating and scoping the credential.

What agents can run against MikroTik RouterOS

get_identity

Get the RouterOS device identity (its configured name)

get_resource

Get system resource usage: RouterOS version, uptime, CPU load, free/total memory, board name and architecture

list_interfaces

List network interfaces with name, type, running state and disabled flag

list_ip_addresses

List configured IPv4 addresses with the interface each is bound to

list_routes

List IPv4 routes with destination, gateway, distance and active state

Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.

How proven is this?

LIVE-PROVEN: every tool on this page was executed with real credentials against a real running MikroTik RouterOS instance (provisioned for the proof, then destroyed), and every call answered successfully. The strongest proof class a connector can carry before it runs inside your own deployment.

  • Credentialed The vault stores, tests and just-in-time resolves its credential; agents never see the secret.
  • Read-only It ships read tools only, so there is nothing to approval-gate.
  • Agent-owned No dedicated agent owns it yet; the orchestrator can drive it on request.
  • Schedulable Not yet exposed in the workflow builder; that integration is on the connector roadmap.
  • Evidenced Per-call evidence envelopes are on the roadmap; vault credential use is already receipted.

MikroTik RouterOS integration FAQ

What can Quox agents do with MikroTik RouterOS?

Agents can run 5 read-only tools against MikroTik RouterOS: get identity, get resource, list interfaces, list ip addresses, list routes. Every call is receipted in the evidence trail.

What does the MikroTik RouterOS integration need?

You provide base URL, username, password from your MikroTik RouterOS account; Quox sends it as HTTP basic credentials. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.

Do agents see my MikroTik RouterOS credentials?

No. Credentials live encrypted in the Quox vault and are resolved server-side at call time. Agents invoke tools; they never receive the underlying secret.

How proven is the MikroTik RouterOS connector?

LIVE-PROVEN: every tool on this page was executed with real credentials against a real running MikroTik RouterOS instance (provisioned for the proof, then destroyed), and every call answered successfully. The strongest proof class a connector can carry before it runs inside your own deployment.