Matrix
Matrix is an open standard and decentralized protocol for real-time communication, providing federated messaging, voice, video, and IoT signalling across independently operated homeservers. The Matrix specification defines several REST APIs (Client-Server, Server-Server, Application Service, Identity Service, and Push Gateway) that interoperate across the federation. Authentication is typically performed via Bearer access tokens, with newer flows using OAuth 2.0.
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 Matrix the way a machine reads it — 27 machine-readable artifacts across 20 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 — Matrix scores 37.7/100 (thin), with a separate agent-readiness read of 47/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.
How we profile Matrix
Each block below is one kind of artifact we hold for Matrix. 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 20
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.
Matrix Client-Server API
REST API used by Matrix clients to communicate with a homeserver, covering login, room creation and management, message sending, sync, device management, end-to-end encryption, ...
Matrix Server-Server (Federation) API
Federation API that lets Matrix homeservers exchange events, presence, and key information with one another over signed JSON requests.
Matrix Application Service API
API used by application services (bridges, bots) to integrate with a homeserver, claim namespaces, and exchange events.
Matrix Identity Service API
API for looking up Matrix user IDs from third-party identifiers such as email addresses and phone numbers via federated identity servers.
Matrix Push Gateway API
Push Gateway API homeservers use to deliver notifications to mobile push services on behalf of Matrix clients.
Matrix Account API
The Account API from Matrix — 1 operation(s) for account.
Matrix Capabilities API
The Capabilities API from Matrix — 1 operation(s) for capabilities.
Matrix CreateRoom API
The CreateRoom API from Matrix — 1 operation(s) for createroom.
Matrix Devices API
The Devices API from Matrix — 1 operation(s) for devices.
Matrix Directory API
The Directory API from Matrix — 1 operation(s) for directory.
Matrix Join API
The Join API from Matrix — 1 operation(s) for join.
Matrix Keys API
The Keys API from Matrix — 1 operation(s) for keys.
Matrix Login API
The Login API from Matrix — 1 operation(s) for login.
Matrix Logout API
The Logout API from Matrix — 1 operation(s) for logout.
Matrix Profile API
The Profile API from Matrix — 2 operation(s) for profile.
Matrix PublicRooms API
The PublicRooms API from Matrix — 1 operation(s) for publicrooms.
Matrix Refresh API
The Refresh API from Matrix — 1 operation(s) for refresh.
Matrix Register API
The Register API from Matrix — 1 operation(s) for register.
Matrix Rooms API
The Rooms API from Matrix — 4 operation(s) for rooms.
Matrix Sync API
The Sync API from Matrix — 1 operation(s) for sync.
Scroll within the panel for all 20 ·
Open Collections 1
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).
Matrix Client-Server API
OPEN COLLECTIONEvent 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.
Matrix Client-Server Sync API
AsyncAPI description of the Matrix Client-Server sync mechanism. Matrix delivers real-time events to clients through the `/_matrix/client/v3/sync` endpoint, which is a long-live...
ASYNCAPISpectral 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.
Matrix API Rules
SPECTRALSecurity Posture 3
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 Matrix — 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 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/matrix · machine-readable index on apis.io