Keycloak
Keycloak is an open source identity and access management solution for modern applications and services, providing single sign-on, identity brokering, user federation, and fine-grained authorization using OAuth 2.0 and OpenID Connect.
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 Keycloak the way a machine reads it — 28 machine-readable artifacts across 6 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 — Keycloak scores 56.0/100 (developing), with a separate agent-readiness read of 55/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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Keycloak
Each block below is one kind of artifact we hold for Keycloak. 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 6
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.
Keycloak Clients API
Manage OAuth/OIDC clients within a realm
Keycloak Groups API
Manage user groups within a realm
Keycloak Identity Providers API
Manage identity providers for federated authentication
Keycloak Realms API
Manage Keycloak realms
Keycloak Roles API
Manage realm-level and client-level roles
Keycloak Users API
Manage users within a realm
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).
Keycloak Admin REST API
OPEN COLLECTIONArazzo Workflows 13
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
Keycloak Assign a User to a Group
Resolve a user and a group by name, add the membership, and verify it landed.
ARAZZOKeycloak Audit Group Membership
Resolve a group by name, read its roles and roster, and spot-check the effective roles of a member.
ARAZZOKeycloak Audit a User's Effective Access
Resolve a user by username and assemble their profile, realm role mappings, and group membership.
ARAZZOKeycloak Decommission a Client
Snapshot a client registration, disable it, and optionally delete it after a soak period.
ARAZZOKeycloak Federate an Identity Provider
Upsert an OIDC or SAML identity provider by alias and verify the stored configuration.
ARAZZOKeycloak Apply a Realm Security Baseline
Capture a realm's current settings, apply brute force protection and session hardening, and verify the result.
ARAZZOKeycloak Inventory a Realm
Discover available realms and assemble a full read-only inventory of one realm's clients, roles, groups, and identity providers.
ARAZZOKeycloak Offboard a User
Disable a user, strip realm role mappings and group membership, and optionally delete the account.
ARAZZOKeycloak Onboard a User
Provision a realm user, set an initial password, and grant a realm-level role.
ARAZZOKeycloak Provision a Group Hierarchy
Create a top-level group, resolve its id, nest a child group beneath it, and read back the hierarchy.
ARAZZOKeycloak Register a Confidential OIDC Client
Register an OpenID Connect client in a realm, resolve its internal UUID, and retrieve its generated secret.
ARAZZOKeycloak Rotate a Client Secret
Resolve a client by clientId, capture the outgoing secret, regenerate it, and verify the new value.
ARAZZOKeycloak Upsert a Realm Role
Create a realm-level role if it is missing, update it if it already exists, then read it back.
ARAZZOScroll within the panel for all 13 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Keycloak Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Keycloak Finops
FINOPSSpectral 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.
Keycloak 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 Keycloak — 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 1
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 16
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 16 ·
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/keycloak · machine-readable index on apis.io