RouterOS

RouterOS is MikroTik's powerful network operating system designed for managing routers, switches, access points, and other network devices. It provides a comprehensive REST API (v7.1+) and a TCP-based binary API for programmatic management of IP addresses, interfaces, firewall rules, routing, VPN configurations, DHCP, DNS, and system resources. RouterOS powers MikroTik hardware and can also be deployed as a virtual machine (CHR).

RouterOS publishes 11 API contracts indexed on the APIs.io network, including Bridge API, DHCP API, DNS API, and 8 more. Tagged areas include Networking, Router, Network Management, Firewall, and MikroTik.

The RouterOS catalog on APIs.io includes 1 JSON-LD context and 2 Spectral governance rulesets.

RouterOS’s developer surface includes engineering blog, authentication, documentation, and 14 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

36.0/100 thin ▬ flat Agent 21/100 agent aware Front door AI 2/6 trace Heartbeat 100/100 alive Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessFreemiumSelf serve⚡ Free to try

1 published contract

Networking Router Network Management FirewallMikroTik

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Telecom Network Operations Management

BC-2600

IP AddressInterface

PUT /ip/address PATCH /ip/address/{id} GET /interface PATCH /interface/{id}

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 36.0/100 · thin

Contract Quality 11.5 / 19

Developer Ergonomics 4.3 / 15

Access Clarity 1.2 / 15

Operational Transparency 2.3 / 10

Contract Governance 2.5 / 9

Discoverability 5.0 / 8

Regulatory Posture 3.4 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 21/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 0 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/routeros/"><img src="https://apis.io/badge/routeros/card.svg" alt="RouterOS on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)

9 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 7.9 — up to +18.4 composite points
Developer Ergonomics scores 28.6 — up to +14.3 composite points
Operational Transparency scores 23.7 — up to +9.9 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/routeros/apis.yml: open an issue on github.com/api-evangelist/routeros to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

APIs 11

Individual APIs this provider publishes, each with its own machine-readable definition.

RouterOS TCP API

The RouterOS TCP API is the native binary protocol for RouterOS, running on TCP port 8728 (standard) and TCP port 8729 (SSL/TLS). It uses a sentence-based word protocol with var...

RouterOS Bridge API

Bridge interface management

RouterOS DHCP API

DHCP server and client management

RouterOS DNS API

DNS cache and configuration

RouterOS Firewall API

Firewall rules, NAT, and address lists

RouterOS Interface API

Network interface management

RouterOS IP Address API

IP address configuration and management

RouterOS Routing API

Routing tables, BGP, OSPF, and static routes

RouterOS System API

System information, identity, and scripts

RouterOS VPN API

VPN tunnels and configurations

RouterOS Wireless API

Wireless interface and station management

Scroll for all 11

Open Collections 11

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

RouterOS REST Bridge API

OPEN COLLECTION

RouterOS REST Bridge DHCP API

OPEN COLLECTION

RouterOS REST Bridge DNS API

OPEN COLLECTION

RouterOS REST Bridge Firewall API

OPEN COLLECTION

RouterOS REST Bridge Interface API

OPEN COLLECTION

RouterOS REST Bridge IP Address API

OPEN COLLECTION

RouterOS REST API

OPEN COLLECTION

RouterOS REST Bridge Routing API

OPEN COLLECTION

RouterOS REST Bridge System API

OPEN COLLECTION

RouterOS REST Bridge VPN API

OPEN COLLECTION

RouterOS REST Bridge Wireless API

OPEN COLLECTION

Scroll for all 11

RouterOS API pricing

Not yet checked against RouterOS's own pricing page. Compiled by API Evangelist on 2026-05-04; confirm before you rely on a figure. A free plan or tier is listed.

Plan	Price
Free freemium	Free
Professional paid	Free
Enterprise enterprise	—

Plan details, limits and sources →

Rate limits

Free Tier Default: 10 requests per minute
Free Tier Monthly Quota: 1000 requests per month
Professional Tier Default: 100 requests per minute

Compiled by API Evangelist, not yet checked against RouterOS's documentation. All 5 limits →

Pricing Plans 1

Published pricing tiers and plan structures.

Routeros Plans Pricing

3 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Routeros Rate Limits

5 limits

RATE LIMITS

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

RouterOS

SLA

FinOps 1

Cost, billing, and metering signals for API financial operations.

Routeros Finops

FINOPS

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Routeros Context

0 classes · 24 properties

JSON-LD

Spectral Rules 2

Spectral governance rulesets for linting and validating these APIs.

RouterOS — jsonschema rules

5 rules · 3 warnings 2 info

SPECTRAL

RouterOS API Rules

10 rules · 6 warnings 2 info

SPECTRAL

JSON Schema 3

Standalone JSON Schema definitions for this provider's data models.

RouterOS Firewall Filter Rule

15 properties

JSON SCHEMA

RouterOS Interface

8 properties

JSON SCHEMA

RouterOS IP Address

7 properties

JSON SCHEMA

JSON Structure 1

JSON Structure definitions describing this provider's data shapes.

Routeros Ip Address Structure

0 properties

JSON STRUCTURE

Examples 3

Example request and response payloads for these APIs.

Routeros Get System Resource Example

4 fields

EXAMPLE

Routeros List Firewall Filters Example

4 fields

EXAMPLE

Routeros List Ip Addresses Example

4 fields

EXAMPLE

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Routeros Authentication

http · 1 scheme

SECURITY

Routeros Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Routeros Vulnerability Disclosure

security.txt · contact published

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Routeros Agentic Access

35 operations · 15 acting

AGENTIC

Resources

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Vocabulary

Vocabulary

JSONLDContext

JSONLDContext

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrg

GitHubOrg

Access & Security 3

Authentication, authorization, and security posture

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 2

Status, limits, changes, and where to get help

RateLimits

RateLimits

Forums

Forums

Commercial 2

Pricing, plans, and the legal terms of use

Plans

Plans

FinOps

FinOps

Company 3

The organization behind the API

Blog

Blog

BlogRSS

BlogRSS

Website

Website

Other 2

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Wiki

Wiki

Source (apis.yml)

aid: routeros
name: RouterOS
description: RouterOS is MikroTik's powerful network operating system designed for managing routers, switches, access points,
  and other network devices. It provides a comprehensive REST API (v7.1+) and a TCP-based binary API for programmatic management
  of IP addresses, interfaces, firewall rules, routing, VPN configurations, DHCP, DNS, and system resources. RouterOS powers
  MikroTik hardware and can also be deployed as a virtual machine (CHR).
type: Index
deliveryModel:
  model: unknown
  open_source: false
  commercial: false
  callable_host: false
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - openapi
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: freemium
  onboarding: self-serve
  trial: false
  try_now: true
  public: false
  gated: none
  gated_source:
  - onboarding
  label: Freemium · Self-serve signup
  confidence: medium
  source:
  - plans
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/routeros.png
tags:
- Networking
- Router
- Network Management
- Firewall
- MikroTik
tags_raw:
- Networking
- Routers
- Network Management
- Firewall
- MikroTik
url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/apis.yml
created: '2024-11-07'
modified: '2026-10-06'
specificationVersion: '0.23'
apis:
- aid: routeros:routeros-tcp-api
  name: RouterOS TCP API
  description: The RouterOS TCP API is the native binary protocol for RouterOS, running on TCP port 8728 (standard) and TCP
    port 8729 (SSL/TLS). It uses a sentence-based word protocol with variable-length encoding, supporting tagged concurrent
    commands, streaming changes via /listen, and cancellation. Used by most RouterOS client libraries (Python, PHP, Java,
    Go, etc.).
  humanURL: https://help.mikrotik.com/docs/spaces/ROS/pages/47579160/API
  baseURL: tcp://{router-ip}:8728
  version: 6.43+
  tags:
  - Networking
  - Router Management
  - TCP API
  - Binary Protocol
  properties:
  - url: https://help.mikrotik.com/docs/spaces/ROS/pages/47579160/API
    type: Documentation
  - url: https://wiki.mikrotik.com/wiki/Manual:API
    type: Documentation
- aid: routeros:routeros-bridge-api
  name: RouterOS Bridge API
  description: Bridge interface management
  humanURL: https://help.mikrotik.com/docs/spaces/ROS/pages/47579162/REST+API
  baseURL: https://{router-ip}/rest
  tags:
  - Bridge
  properties:
  - type: OpenAPI
    url: openapi/routeros-bridge-api-openapi.yml
  - type: Documentation
    url: https://help.mikrotik.com/docs/spaces/ROS/pages/47579162/REST+API
  - type: Documentation
    url: https://help.mikrotik.com/docs/spaces/ROS/pages/47579160/API
  - type: SpectralRules
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/rules/routeros-rules.yml
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-schema/routeros-ip-address-schema.json
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-schema/routeros-interface-schema.json
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-schema/routeros-firewall-filter-schema.json
  - type: JSONStructure
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-structure/routeros-ip-address-structure.json
  - type: JSONLDContext
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-ld/routeros-context.jsonld
  - type: Examples
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/examples/routeros-list-ip-addresses-example.json
  - type: Examples
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/examples/routeros-list-firewall-filters-example.json
  - type: Examples
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/examples/routeros-get-system-resource-example.json
  - type: Vocabulary
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/vocabulary/routeros-vocabulary.yml
- aid: routeros:routeros-dhcp-api
  name: RouterOS DHCP API
  description: DHCP server and client management
  humanURL: https://help.mikrotik.com/docs/spaces/ROS/pages/47579162/REST+API
  baseURL: https://{router-ip}/rest
  tags:
  - DHCP
  properties:
  - type: OpenAPI
    url: openapi/routeros-dhcp-api-openapi.yml
  - type: Documentation
    url: https://help.mikrotik.com/docs/spaces/ROS/pages/47579162/REST+API
  - type: Documentation
    url: https://help.mikrotik.com/docs/spaces/ROS/pages/47579160/API
  - type: SpectralRules
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/rules/routeros-rules.yml
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-schema/routeros-ip-address-schema.json
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-schema/routeros-interface-schema.json
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-schema/routeros-firewall-filter-schema.json
  - type: JSONStructure
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-structure/routeros-ip-address-structure.json
  - type: JSONLDContext
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-ld/routeros-context.jsonld
  - type: Examples
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/examples/routeros-list-ip-addresses-example.json
  - type: Examples
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/examples/routeros-list-firewall-filters-example.json
  - type: Examples
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/examples/routeros-get-system-resource-example.json
  - type: Vocabulary
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/vocabulary/routeros-vocabulary.yml
- aid: routeros:routeros-dns-api
  name: RouterOS DNS API
  description: DNS cache and configuration
  humanURL: https://help.mikrotik.com/docs/spaces/ROS/pages/47579162/REST+API
  baseURL: https://{router-ip}/rest
  tags:
  - DNS
  properties:
  - type: OpenAPI
    url: openapi/routeros-dns-api-openapi.yml
  - type: Documentation
    url: https://help.mikrotik.com/docs/spaces/ROS/pages/47579162/REST+API
  - type: Documentation
    url: https://help.mikrotik.com/docs/spaces/ROS/pages/47579160/API
  - type: SpectralRules
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/rules/routeros-rules.yml
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-schema/routeros-ip-address-schema.json
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-schema/routeros-interface-schema.json
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-schema/routeros-firewall-filter-schema.json
  - type: JSONStructure
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-structure/routeros-ip-address-structure.json
  - type: JSONLDContext
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-ld/routeros-context.jsonld
  - type: Examples
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/examples/routeros-list-ip-addresses-example.json
  - type: Examples
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/examples/routeros-list-firewall-filters-example.json
  - type: Examples
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/examples/routeros-get-system-resource-example.json
  - type: Vocabulary
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/vocabulary/routeros-vocabulary.yml
- aid: routeros:routeros-firewall-api
  name: RouterOS Firewall API
  description: Firewall rules, NAT, and address lists
  humanURL: https://help.mikrotik.com/docs/spaces/ROS/pages/47579162/REST+API
  baseURL: https://{router-ip}/rest
  tags:
  - Firewall
  properties:
  - type: OpenAPI
    url: openapi/routeros-firewall-api-openapi.yml
  - type: Documentation
    url: https://help.mikrotik.com/docs/spaces/ROS/pages/47579162/REST+API
  - type: Documentation
    url: https://help.mikrotik.com/docs/spaces/ROS/pages/47579160/API
  - type: SpectralRules
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/rules/routeros-rules.yml
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-schema/routeros-ip-address-schema.json
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-schema/routeros-interface-schema.json
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-schema/routeros-firewall-filter-schema.json
  - type: JSONStructure
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-structure/routeros-ip-address-structure.json
  - type: JSONLDContext
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-ld/routeros-context.jsonld
  - type: Examples
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/examples/routeros-list-ip-addresses-example.json
  - type: Examples
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/examples/routeros-list-firewall-filters-example.json
  - type: Examples
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/examples/routeros-get-system-resource-example.json
  - type: Vocabulary
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/vocabulary/routeros-vocabulary.yml
- aid: routeros:routeros-interface-api
  name: RouterOS Interface API
  description: Network interface management
  humanURL: https://help.mikrotik.com/docs/spaces/ROS/pages/47579162/REST+API
  baseURL: https://{router-ip}/rest
  tags:
  - Interfaces
  tags_raw:
  - Interface
  properties:
  - type: OpenAPI
    url: openapi/routeros-interface-api-openapi.yml
  - type: Documentation
    url: https://help.mikrotik.com/docs/spaces/ROS/pages/47579162/REST+API
  - type: Documentation
    url: https://help.mikrotik.com/docs/spaces/ROS/pages/47579160/API
  - type: SpectralRules
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/rules/routeros-rules.yml
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-schema/routeros-ip-address-schema.json
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-schema/routeros-interface-schema.json
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-schema/routeros-firewall-filter-schema.json
  - type: JSONStructure
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-structure/routeros-ip-address-structure.json
  - type: JSONLDContext
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-ld/routeros-context.jsonld
  - type: Examples
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/examples/routeros-list-ip-addresses-example.json
  - type: Examples
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/examples/routeros-list-firewall-filters-example.json
  - type: Examples
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/examples/routeros-get-system-resource-example.json
  - type: Vocabulary
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/vocabulary/routeros-vocabulary.yml
- aid: routeros:routeros-ip-address-api
  name: RouterOS IP Address API
  description: IP address configuration and management
  humanURL: https://help.mikrotik.com/docs/spaces/ROS/pages/47579162/REST+API
  baseURL: https://{router-ip}/rest
  tags:
  - IP Address
  properties:
  - type: OpenAPI
    url: openapi/routeros-ip-address-api-openapi.yml
  - type: Documentation
    url: https://help.mikrotik.com/docs/spaces/ROS/pages/47579162/REST+API
  - type: Documentation
    url: https://help.mikrotik.com/docs/spaces/ROS/pages/47579160/API
  - type: SpectralRules
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/rules/routeros-rules.yml
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-schema/routeros-ip-address-schema.json
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-schema/routeros-interface-schema.json
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-schema/routeros-firewall-filter-schema.json
  - type: JSONStructure
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-structure/routeros-ip-address-structure.json
  - type: JSONLDContext
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-ld/routeros-context.jsonld
  - type: Examples
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/examples/routeros-list-ip-addresses-example.json
  - type: Examples
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/examples/routeros-list-firewall-filters-example.json
  - type: Examples
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/examples/routeros-get-system-resource-example.json
  - type: Vocabulary
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/vocabulary/routeros-vocabulary.yml
- aid: routeros:routeros-routing-api
  name: RouterOS Routing API
  description: Routing tables, BGP, OSPF, and static routes
  humanURL: https://help.mikrotik.com/docs/spaces/ROS/pages/47579162/REST+API
  baseURL: https://{router-ip}/rest
  tags:
  - Routing
  properties:
  - type: OpenAPI
    url: openapi/routeros-routing-api-openapi.yml
  - type: Documentation
    url: https://help.mikrotik.com/docs/spaces/ROS/pages/47579162/REST+API
  - type: Documentation
    url: https://help.mikrotik.com/docs/spaces/ROS/pages/47579160/API
  - type: SpectralRules
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/rules/routeros-rules.yml
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-schema/routeros-ip-address-schema.json
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-schema/routeros-interface-schema.json
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-schema/routeros-firewall-filter-schema.json
  - type: JSONStructure
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-structure/routeros-ip-address-structure.json
  - type: JSONLDContext
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-ld/routeros-context.jsonld
  - type: Examples
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/examples/routeros-list-ip-addresses-example.json
  - type: Examples
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/examples/routeros-list-firewall-filters-example.json
  - type: Examples
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/examples/routeros-get-system-resource-example.json
  - type: Vocabulary
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/vocabulary/routeros-vocabulary.yml
- aid: routeros:routeros-system-api
  name: RouterOS System API
  description: System information, identity, and scripts
  humanURL: https://help.mikrotik.com/docs/spaces/ROS/pages/47579162/REST+API
  baseURL: https://{router-ip}/rest
  tags:
  - System
  properties:
  - type: OpenAPI
    url: openapi/routeros-system-api-openapi.yml
  - type: Documentation
    url: https://help.mikrotik.com/docs/spaces/ROS/pages/47579162/REST+API
  - type: Documentation
    url: https://help.mikrotik.com/docs/spaces/ROS/pages/47579160/API
  - type: SpectralRules
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/rules/routeros-rules.yml
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-schema/routeros-ip-address-schema.json
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-schema/routeros-interface-schema.json
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-schema/routeros-firewall-filter-schema.json
  - type: JSONStructure
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-structure/routeros-ip-address-structure.json
  - type: JSONLDContext
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-ld/routeros-context.jsonld
  - type: Examples
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/examples/routeros-list-ip-addresses-example.json
  - type: Examples
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/examples/routeros-list-firewall-filters-example.json
  - type: Examples
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/examples/routeros-get-system-resource-example.json
  - type: Vocabulary
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/vocabulary/routeros-vocabulary.yml
- aid: routeros:routeros-vpn-api
  name: RouterOS VPN API
  description: VPN tunnels and configurations
  humanURL: https://help.mikrotik.com/docs/spaces/ROS/pages/47579162/REST+API
  baseURL: https://{router-ip}/rest
  tags:
  - VPN
  properties:
  - type: OpenAPI
    url: openapi/routeros-vpn-api-openapi.yml
  - type: Documentation
    url: https://help.mikrotik.com/docs/spaces/ROS/pages/47579162/REST+API
  - type: Documentation
    url: https://help.mikrotik.com/docs/spaces/ROS/pages/47579160/API
  - type: SpectralRules
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/rules/routeros-rules.yml
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-schema/routeros-ip-address-schema.json
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-schema/routeros-interface-schema.json
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-schema/routeros-firewall-filter-schema.json
  - type: JSONStructure
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-structure/routeros-ip-address-structure.json
  - type: JSONLDContext
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-ld/routeros-context.jsonld
  - type: Examples
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/examples/routeros-list-ip-addresses-example.json
  - type: Examples
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/examples/routeros-list-firewall-filters-example.json
  - type: Examples
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/examples/routeros-get-system-resource-example.json
  - type: Vocabulary
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/vocabulary/routeros-vocabulary.yml
- aid: routeros:routeros-wireless-api
  name: RouterOS Wireless API
  description: Wireless interface and station management
  humanURL: https://help.mikrotik.com/docs/spaces/ROS/pages/47579162/REST+API
  baseURL: https://{router-ip}/rest
  tags:
  - Wireless
  properties:
  - type: OpenAPI
    url: openapi/routeros-wireless-api-openapi.yml
  - type: Documentation
    url: https://help.mikrotik.com/docs/spaces/ROS/pages/47579162/REST+API
  - type: Documentation
    url: https://help.mikrotik.com/docs/spaces/ROS/pages/47579160/API
  - type: SpectralRules
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/rules/routeros-rules.yml
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-schema/routeros-ip-address-schema.json
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-schema/routeros-interface-schema.json
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-schema/routeros-firewall-filter-schema.json
  - type: JSONStructure
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-structure/routeros-ip-address-structure.json
  - type: JSONLDContext
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-ld/routeros-context.jsonld
  - type: Examples
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/examples/routeros-list-ip-addresses-example.json
  - type: Examples
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/examples/routeros-list-firewall-filters-example.json
  - type: Examples
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/examples/routeros-get-system-resource-example.json
  - type: Vocabulary
    url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/vocabulary/routeros-vocabulary.yml
common:
- type: Plans
  url: plans/routeros-plans-pricing.yml
- type: RateLimits
  url: rate-limits/routeros-rate-limits.yml
- type: FinOps
  url: finops/routeros-finops.yml
- url: https://mikrotik.com/supportsec
  type: Blog
- url: https://cdn.mikrotik.com/web-assets/supportsec/rss.xml
  type: BlogRSS
- type: CapabilityMap
  url: capabilities/routeros-capability-edges.yml
  name: RouterOS Business Capability Map
- type: AgenticAccess
  url: agentic-access/routeros-agentic-access.yml
- type: VulnerabilityDisclosure
  url: security/routeros-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/routeros-domain-security.yml
- type: Authentication
  url: authentication/routeros-authentication.yml
- type: Website
  url: https://mikrotik.com
- type: Documentation
  url: https://help.mikrotik.com/docs/spaces/ROS
- type: GitHubOrg
  url: https://github.com/mikrotik
- type: Forums
  url: https://forum.mikrotik.com
- type: Wiki
  url: https://wiki.mikrotik.com
- type: Vocabulary
  url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/vocabulary/routeros-vocabulary.yml
- type: JSONLDContext
  url: https://raw.githubusercontent.com/api-evangelist/routeros/refs/heads/main/json-ld/routeros-context.jsonld
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

RouterOS API — frequently asked questions

Does RouterOS have an API?

Yes. APIs.io lists 11 APIs from RouterOS, including RouterOS TCP API, RouterOS Bridge API and RouterOS DHCP API, and 8 more.

Is there an OpenAPI specification for the RouterOS API?

Yes. APIs.io indexes 10 OpenAPI specifications for RouterOS, each linked for download from this page.

How do I authenticate with the RouterOS API?

RouterOS uses bearer-token authentication (http · 1 scheme). The details are profiled on APIs.io as Routeros Authentication.

How much does the RouterOS API cost?

APIs.io lists 3 pricing plans for RouterOS, with each plan's price, limits and inclusions under Pricing on this page.

Is the RouterOS API ready for AI agents?

RouterOS has a Kin Score of 36.0 out of 100 (thin) and an Agent Readiness score of 21.3 (agent-aware), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/routeros"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/routeros/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/routeros/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.