← Leaderboard
8.3 L4

Keycloak

Native Assessed · Docs reviewed · Mar 23, 2026 Confidence 0.55 Last evaluated Mar 23, 2026

Scores 8.3/10 overall. with execution at 8.5 and access readiness at 8.0.

Verify before you commit

Trust read first, source links second, build decision third.

Use this page to sanity-check Keycloak quickly. We surface the evidence tier, freshness, and failure posture here, then put the official links where you can actually act on them, especially on mobile.

Evidence

Assessed

Docs reviewed · Mar 23, 2026

Freshness

Updated 2026-03-23T18:15:59.064899+00:00

Mar 23, 2026

Failures

Clear

No active failures listed

Score breakdown

Dimension Score Bar
Execution Score

Measures reliability, idempotency, error ergonomics, latency distribution, and schema stability.

8.5
Access Readiness Score

Measures how easily an agent can onboard, authenticate, and start using this service autonomously.

8.0
Aggregate AN Score

Composite score: 70% execution + 30% access readiness.

8.3

Autonomy breakdown

P1 Payment Autonomy
G1 Governance Readiness
W1 Web Agent Accessibility
Overall Autonomy
Pending

Active failure modes

No active failure modes reported.

Reviews

Published review summaries with trust provenance attached to each card.

How are reviews sourced?

Docs-backed Built from public docs and product materials.

Test-backed Backed by guided testing or evaluator-run checks.

Runtime-verified Verified from authenticated runtime evidence.

Keycloak: Comprehensive Agent-Usability Assessment

Docs-backed

Keycloak is the de facto open-source IAM platform — used in enterprise, government, and cloud-native environments where self-hosted SSO and OAuth2/OIDC are required. For agents, the Admin REST API enables: user CRUD (create users, assign roles, reset passwords, disable accounts), realm configuration management, client registration, token inspection (introspect), and user group management. Keycloak handles OAuth2/OIDC flows that other services rely on — it can be both the IAM authority and an API target for identity operations. High feature complexity; configuration-heavy initial setup. Quarkus-based since v17 (significantly improved performance vs. WildFly-based v16). Confidence is docs-derived.

Rhumb editorial team Mar 23, 2026

Keycloak: Auth & Access Control

Docs-backed

Admin API authentication: client credentials OAuth2 flow. Create a service account client in Keycloak admin console → generate client credentials → POST to /realms/{realm}/protocol/openid-connect/token with grant_type=client_credentials for a Bearer token. Service account needs admin realm role (realm-admin) or specific fine-grained permissions. Token expiry configurable per client (default 60s for admin tokens — must refresh frequently). HTTPS enforced in production. Keycloak itself manages OAuth2/OIDC for all integrated services.

Rhumb editorial team Mar 23, 2026

Keycloak: Documentation & Developer Experience

Docs-backed

keycloak.org/documentation provides comprehensive server documentation: admin REST API reference (fully generated from code), server administration guide, securing applications guide, server developer guide, and authorization services reference. Documentation is thorough but extensive — expect steep learning curve. Getting started via Docker: docker run quay.io/keycloak/keycloak:latest start-dev. Admin console available at /admin for visual configuration. Community support via Keycloak Discourse forum, GitHub, and Keycloak Slack.

Rhumb editorial team Mar 23, 2026

Keycloak: API Design & Integration Surface

Docs-backed

Admin REST API at {host}/admin/realms/{realm}. Resources: users, groups, roles, clients, client-scopes, realms, sessions, token. GET /users lists users with optional filtering (search, email, username). POST /users creates a user. PUT /users/{id} updates user attributes/enabled status. POST /users/{id}/role-mappings/realm assigns realm roles. GET /clients lists OAuth2 clients in the realm. POST /clients creates a new OAuth2 client. GET /{realm}/users/{id}/sessions lists active sessions for a user. DELETE /sessions/{sessionId} revokes a session. Pagination: first, max params.

Rhumb editorial team Mar 23, 2026

Keycloak: Error Handling & Operational Reliability

Docs-backed

Admin API errors: HTTP 400 for validation errors (with JSON errorMessage), 403 for insufficient scope, 404 for missing entity, 409 for conflicts (user already exists). Rate limiting: not built-in by default; load balancer/reverse proxy enforced. Short-lived admin tokens require frequent refresh (important for agent loops). Keycloak startup time: 3-10 seconds with Quarkus; full restart should be minimized in production. High availability via active-active clustering with JDBC or Infinispan. Keycloak Cloud (Keycloak.cloud) available for managed hosting.

Rhumb editorial team Mar 23, 2026

Use in your agent

mcp
get_score ("keycloak")
● Keycloak 8.3 L4 Native
exec: 8.5 · access: 8.0

Trust shortcuts

This score is documentation-derived. Treat it as a docs-based evaluation of API design, auth, error handling, and documentation quality.

Read how the score works, how disputes are handled, and how Rhumb scored itself before launch.

Overall tier

L4 Native

8.3 / 10.0

Alternatives

No alternatives captured yet.