systemd
systemd is a suite of basic building blocks for a Linux system. It runs as PID 1 and is the system and service manager that bootstraps the rest of the userspace, supervises long-running services, and exposes a coordinated set of D-Bus and Varlink IPC interfaces for managing services (systemd1), users and sessions (logind), network interfaces (networkd), name resolution (resolved), containers/VMs (machined), home directories (homed), boot entries (boot1/sysupdate1), system hostname/locale/timedate, OOM protection (oomd), portable services, and image imports. The project also publishes a stable command-line surface (systemctl, journalctl, networkctl, resolvectl, loginctl, machinectl, hostnamectl, timedatectl, localectl, busctl, varlinkctl, bootctl, homectl, coredumpctl, oomctl, portablectl, importctl, systemd-analyze and more). systemd is dual-licensed (LGPL-2.1-or-later for libraries and most code, GPL-2.0-or-later for select tools) and developed openly on GitHub at systemd/systemd.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles systemd the way a machine reads it — 89 machine-readable artifacts across 34 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — systemd scores 36.1/100 (thin), with a separate agent-readiness read of 19/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-08-17 · rubric v0.11.0
Put this on your own site. The badge is drawn live from systemd's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/systemd/"
title="systemd on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/systemd.svg"
alt="systemd Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/systemd/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/systemd/"
title="systemd on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/systemd/card.svg"
alt="systemd Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile systemd
Each block below is one kind of artifact we hold for systemd. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 34
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
systemd-localed (org.freedesktop.locale1)
D-Bus API of systemd-localed for getting and setting the system locale, X11 keymap, and console keymap.
systemd-timedated (org.freedesktop.timedate1)
D-Bus API of systemd-timedated for getting and setting the system time, timezone, NTP enablement, and RTC-in-local-time policy.
systemd-timesyncd (org.freedesktop.timesync1)
D-Bus API of systemd-timesyncd exposing the current NTP server, peers, root delay/dispersion, and synchronization status.
systemd-homed (org.freedesktop.home1)
D-Bus API of systemd-homed for managing portable, encrypted user home directories (LUKS, btrfs subvol, fscrypt, CIFS, directory) including create/remove/update/list operations, ...
systemd-importd (org.freedesktop.import1)
D-Bus API of systemd-importd for importing, exporting, downloading, listing, and removing container/VM machine images (tar, raw, dkr/OCI, qcow2) used by machined and portable se...
systemd-oomd (org.freedesktop.oom1)
D-Bus API of systemd-oomd, the userspace out-of-memory killer that uses cgroup v2 PSI signals to kill cgroups under memory or swap pressure. Exposes per-slice/cgroup state and p...
systemd-portabled (org.freedesktop.portable1)
D-Bus API of systemd-portabled for attaching/detaching portable service images, listing attached images, inspecting them, and managing their lifecycle on the host.
systemd-sysupdated (org.freedesktop.sysupdate1)
D-Bus API of systemd-sysupdated for transactional A/B updates of system/host/portable/container images using systemd-sysupdate transfers, including target enumeration, version l...
LogControl1 (org.freedesktop.LogControl1)
Generic D-Bus interface that systemd daemons (and other services) implement to expose runtime log level and log target configuration. Allows tools like systemd-analyze to change...
systemd Boot API
The Boot API from systemd — 1 operation(s) for boot.
systemd Cache API
The Cache API from systemd — 2 operation(s) for cache.
systemd Cgroups API
Transient unit creation and cgroup-backed resource control.
systemd Configuration API
The Configuration API from systemd — 11 operation(s) for configuration.
systemd Credentials API
The Credentials API from systemd — 2 operation(s) for credentials.
systemd Hostname API
The Hostname API from systemd — 3 operation(s) for hostname.
systemd Image API
The Image API from systemd — 1 operation(s) for image.
systemd Images API
The Images API from systemd — 4 operation(s) for images.
systemd Inhibitors API
The Inhibitors API from systemd — 1 operation(s) for inhibitors.
systemd Jobs API
Pending and active jobs scheduled by the Manager.
systemd Links API
The Links API from systemd — 7 operation(s) for links.
systemd Machine Info API
The Machine Info API from systemd — 4 operation(s) for machine info.
systemd Machines API
The Machines API from systemd — 7 operation(s) for machines.
systemd Manager API
The Manager API from systemd — 12 operation(s) for manager.
systemd PCR API
The PCR API from systemd — 1 operation(s) for pcr.
systemd Power API
The Power API from systemd — 5 operation(s) for power.
systemd Resolution API
The Resolution API from systemd — 4 operation(s) for resolution.
systemd Resolve API
The Resolve API from systemd — 1 operation(s) for resolve.
systemd Seats API
The Seats API from systemd — 1 operation(s) for seats.
systemd Sessions API
The Sessions API from systemd — 5 operation(s) for sessions.
systemd Snapshots API
System state introspection.
systemd Unit API
The Unit API from systemd — 2 operation(s) for unit.
systemd Units API
Unit lifecycle and enumeration.
systemd UserDatabase API
The UserDatabase API from systemd — 3 operation(s) for userdatabase.
systemd Users API
The Users API from systemd — 3 operation(s) for users.
Scroll within the panel for all 34 ·
Open Collections 33
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONsystemd-hostnamed (org.freedesktop.hostname1)
OPEN COLLECTIONsystemd-logind (org.freedesktop.login1)
OPEN COLLECTIONsystemd-machined (org.freedesktop.machine1)
OPEN COLLECTIONsystemd-networkd (org.freedesktop.network1)
OPEN COLLECTIONsystemd-resolved (org.freedesktop.resolve1)
OPEN COLLECTIONsystemd-hostnamed (org.freedesktop.hostname1) Boot API
OPEN COLLECTIONsystemd-hostnamed (org.freedesktop.hostname1) Boot Cache API
OPEN COLLECTIONsystemd-hostnamed (org.freedesktop.hostname1) Boot Image API
OPEN COLLECTIONsystemd-hostnamed (org.freedesktop.hostname1) Boot Jobs API
OPEN COLLECTIONsystemd-hostnamed (org.freedesktop.hostname1) Boot Links API
OPEN COLLECTIONsystemd-hostnamed (org.freedesktop.hostname1) Boot PCR API
OPEN COLLECTIONsystemd-hostnamed (org.freedesktop.hostname1) Boot Power API
OPEN COLLECTIONsystemd-hostnamed (org.freedesktop.hostname1) Boot Seats API
OPEN COLLECTIONsystemd-hostnamed (org.freedesktop.hostname1) Boot Unit API
OPEN COLLECTIONsystemd-hostnamed (org.freedesktop.hostname1) Boot Units API
OPEN COLLECTIONsystemd-hostnamed (org.freedesktop.hostname1) Boot Users API
OPEN COLLECTIONsystemd Manager (org.freedesktop.systemd1)
OPEN COLLECTIONsystemd Varlink Interfaces (io.systemd.*)
OPEN COLLECTIONScroll within the panel for all 33 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Systemd Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
systemd API Rules
SPECTRALsystemd API Rules
SPECTRALJSON Schema 6
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
logind Session
JSON SCHEMAmachined Machine
JSON SCHEMAnetworkd Link
JSON SCHEMAsystemd Job
JSON SCHEMAsystemd Unit
JSON SCHEMAsystemd JSON User Record (partial)
JSON SCHEMAJSON Structure 1
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Systemd Structure
JSON STRUCTUREExamples 10
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Login1 Inhibit Example
EXAMPLELogin1 Listsessions Example
EXAMPLENetwork1 Listlinks Example
EXAMPLESystemd1 Listunits Example
EXAMPLESystemd1 Startunit Example
EXAMPLEScroll within the panel for all 10 ·
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for systemd — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 25
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 25 ·
Access & Security 1
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/systemd · machine-readable index on apis.io
This is an independent, third-party profile of systemd, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.