RomM
RomM is a free, self‑hosted application for scanning, organizing, and playing your retro video‑game collection. It aggregates metadata from over ten providers, synchronizes saves across devices, and supports more than 400 platforms. RomM offers a web‑based interface with built‑in emulators, OIDC single‑sign‑on, and a REST API for integration. The project is open‑source, AGPL‑3.0 licensed, and can be deployed via Docker, Kubernetes, or various NAS solutions.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles RomM the way a machine reads it — 50 machine-readable artifacts across 1 API, 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 — RomM scores 41.4/100 (developing), with a separate agent-readiness read of 32/100 (agent ready). 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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Put this on your own site. The badge is drawn live from RomM'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/romm/"
title="RomM on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/romm.svg"
alt="RomM Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/romm/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/romm/"
title="RomM on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/romm/card.svg"
alt="RomM 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 RomM
Each block below is one kind of artifact we hold for RomM. 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 33
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.
RomM Activity API
The activity API from RomM — 3 operation(s) for activity.
RomM Audit API
The audit API from RomM — 1 operation(s) for audit.
RomM Auth API
The auth API from RomM — 7 operation(s) for auth.
RomM Client Tokens API
The client-tokens API from RomM — 8 operation(s) for client-tokens.
RomM Collections API
The collections API from RomM — 12 operation(s) for collections.
RomM Config API
The config API from RomM — 9 operation(s) for config.
RomM Device Auth API
The device-auth API from RomM — 5 operation(s) for device-auth.
RomM Devices API
The devices API from RomM — 6 operation(s) for devices.
RomM Export API
The export API from RomM — 2 operation(s) for export.
RomM Feeds API
The feeds API from RomM — 12 operation(s) for feeds.
RomM Firmware API
The firmware API from RomM — 5 operation(s) for firmware.
RomM Logs API
The logs API from RomM — 1 operation(s) for logs.
RomM Memory Cards API
The memory-cards API from RomM — 8 operation(s) for memory-cards.
RomM Music API
The music API from RomM — 14 operation(s) for music.
RomM Netplay API
The netplay API from RomM — 1 operation(s) for netplay.
RomM Notification Channels API
The notification-channels API from RomM — 7 operation(s) for notification-channels.
RomM Notifications API
The notifications API from RomM — 3 operation(s) for notifications.
RomM Permissions API
The permissions API from RomM — 6 operation(s) for permissions.
RomM Platforms API
The platforms API from RomM — 5 operation(s) for platforms.
RomM Play Sessions API
The play-sessions API from RomM — 2 operation(s) for play-sessions.
RomM Recommendations API
The recommendations API from RomM — 1 operation(s) for recommendations.
RomM Roms API
The roms API from RomM — 42 operation(s) for roms.
RomM Saves API
The saves API from RomM — 13 operation(s) for saves.
RomM Screenshots API
The screenshots API from RomM — 3 operation(s) for screenshots.
RomM Search API
The search API from RomM — 2 operation(s) for search.
RomM States API
The states API from RomM — 9 operation(s) for states.
RomM Stats API
The stats API from RomM — 1 operation(s) for stats.
RomM Streaming API
The streaming API from RomM — 16 operation(s) for streaming.
RomM Sync API
The sync API from RomM — 5 operation(s) for sync.
RomM System API
The system API from RomM — 4 operation(s) for system.
RomM Tasks API
The tasks API from RomM — 5 operation(s) for tasks.
RomM Upload API
The upload API from RomM — 4 operation(s) for upload.
RomM Users API
The users API from RomM — 8 operation(s) for users.
Scroll within the panel for all 33 ·
Agent Skills 4
An agent skill packages the how-to for driving these APIs from an assistant — the prompts, the sequence, the guardrails — so the knowledge to use the API travels with it.
Packaged agent skills for driving this provider's APIs from an AI assistant.
romm-add-and-get-user
AGENT SKILLromm-add-collection-with-roms
AGENT SKILLromm-create-and-dismiss-notification
AGENT SKILLromm-register-device
AGENT SKILLEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Romm Webhooks
ASYNCAPISemantic 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.
Romm Context
JSON-LDSpectral Rules 1
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.
RomM 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.
Body_update_rom_api_roms__id__put
JSON SCHEMAConfigResponse
JSON SCHEMADetailedRomSchema
JSON SCHEMAPlatformSchema
JSON SCHEMASearchRomSchema
JSON SCHEMASimpleRomSchema
JSON SCHEMASecurity Posture 2
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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
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 RomM — 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.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
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/romm · machine-readable index on apis.io
This is an independent, third-party profile of RomM, 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.