RBAC website screenshot

RBAC

Role-Based Access Control (RBAC) is a security paradigm that restricts system access based on assigned roles rather than individual user identities. Users are granted permissions through role membership, simplifying access management and ensuring the principle of least privilege. RBAC is foundational to enterprise identity, authorization, and compliance programs and is implemented across operating systems, cloud platforms, databases, and APIs. The NIST/ANSI/INCITS 359-2004 standard formally defines the RBAC model across four components: Core RBAC, Hierarchical RBAC, Static Separation of Duty, and Dynamic Separation of Duty. Cloud platforms (AWS IAM, Azure RBAC, GCP IAM) and Kubernetes all implement RBAC natively, making it the de facto authorization standard for enterprise and cloud-native environments.

RBAC is profiled on the APIs.io network. Tagged areas include Access Control, Authorization, Cloud-Native, Compliance, and Identity Management.

The RBAC catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.

RBAC’s developer surface includes code examples, documentation, and 12 more developer resources.

📡 Source on GitHub
15.2/100 emerging ▬ flat Agent 1/100 human only Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0
0 APIs
Access ControlAuthorizationCloud-NativeComplianceIdentity ManagementKubernetesRBACSecurity

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
Composite quality — 15.2/100 · emerging
Contract Quality 5.3 / 25
Developer Ergonomics 1.9 / 20
Access Clarity 0.0 / 20
Operational Transparency 0.0 / 13
Contract Governance 3.0 / 12
Discoverability 5.0 / 10
Agent readiness — 1/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 10
Documented Reversibility 0 / 6
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 7 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Delegated User Identity 0 / 6
Protected Resource Metadata 0 / 5
Registration Without a Human 0 / 6
Agentic Commerce Well-Known Document 0 / 5
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/rbac: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Rbac Context

8 classes · 12 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

RBAC API Rules

5 rules · 3 warnings 2 info

SPECTRAL

JSON Schema 3

Standalone JSON Schema definitions for this provider's data models.

RBAC Role Assignment

8 properties

JSON SCHEMA

RBAC Permission

6 properties

JSON SCHEMA

RBAC Role

8 properties

JSON SCHEMA

JSON Structure 3

JSON Structure definitions describing this provider's data shapes.

Rbac Assignment Structure

0 properties

JSON STRUCTURE

Rbac Permission Structure

0 properties

JSON STRUCTURE

Rbac Role Structure

0 properties

JSON STRUCTURE

Examples 3

Example request and response payloads for these APIs.

Rbac Assignment Example

10 fields

EXAMPLE

Rbac Permission Example

8 fields

EXAMPLE

Rbac Role Example

10 fields

EXAMPLE

Resources

Documentation 5

Reference material describing how the API behaves

JSONSchema
JSONSchema
 JSONSchema
JSONSchema
 JSONSchema
JSONSchema
 Documentation
Documentation
 Documentation
Documentation

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

JSONStructure
JSONStructure
 JSONStructure
JSONStructure
 JSONStructure
JSONStructure
 JSONLDContext
JSONLDContext
 Vocabulary
Vocabulary

Build 3

SDKs, sample code, and the tooling you integrate with

Examples
Examples
 Examples
Examples
 Examples
Examples

Other 1

Properties that don't map to a standard resource type

Standards
Standards

Source (apis.yml)

apis.yml Raw ↑ 
aid: rbac
name: RBAC
description: 'Role-Based Access Control (RBAC) is a security paradigm that restricts system access based on assigned roles
  rather than individual user identities. Users are granted permissions through role membership, simplifying access management
  and ensuring the principle of least privilege. RBAC is foundational to enterprise identity, authorization, and compliance
  programs and is implemented across operating systems, cloud platforms, databases, and APIs. The NIST/ANSI/INCITS 359-2004
  standard formally defines the RBAC model across four components: Core RBAC, Hierarchical RBAC, Static Separation of Duty,
  and Dynamic Separation of Duty. Cloud platforms (AWS IAM, Azure RBAC, GCP IAM) and Kubernetes all implement RBAC natively,
  making it the de facto authorization standard for enterprise and cloud-native environments.'
type: Index
deliveryModel:
  model: unknown
  open_source: false
  commercial: false
  callable_host: false
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - none
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source: []
  generated: '2026-07-22'
  method: derived
position: Consuming
access: 3rd-Party
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/rbac.png
url: https://raw.githubusercontent.com/api-evangelist/rbac/refs/heads/main/apis.yml
tags:
- Access Control
- Authorization
- Cloud-Native
- Compliance
- Identity Management
- Kubernetes
- RBAC
- Security
tags_raw:
- Access Control
- Authorization
- Cloud Native
- Compliance
- Identity Management
- Kubernetes
- RBAC
- Security
created: '2025-01-01'
modified: '2026-05-02'
specificationVersion: '0.23'
apis: []
common:
- type: JSONSchema
  name: RBAC Role Schema
  description: JSON Schema definition for an RBAC role.
  url: https://raw.githubusercontent.com/api-evangelist/rbac/refs/heads/main/json-schema/rbac-role.json
- type: JSONSchema
  name: RBAC Permission Schema
  description: JSON Schema definition for an RBAC permission.
  url: https://raw.githubusercontent.com/api-evangelist/rbac/refs/heads/main/json-schema/rbac-permission.json
- type: JSONSchema
  name: RBAC Assignment Schema
  description: JSON Schema definition for assigning roles to users.
  url: https://raw.githubusercontent.com/api-evangelist/rbac/refs/heads/main/json-schema/rbac-assignment.json
- type: JSONStructure
  name: RBAC Role Structure
  description: Field-level structure documentation for the RBAC role object.
  url: https://raw.githubusercontent.com/api-evangelist/rbac/refs/heads/main/json-structure/rbac-role-structure.json
- type: JSONStructure
  name: RBAC Permission Structure
  description: Field-level structure documentation for the RBAC permission object.
  url: https://raw.githubusercontent.com/api-evangelist/rbac/refs/heads/main/json-structure/rbac-permission-structure.json
- type: JSONStructure
  name: RBAC Assignment Structure
  description: Field-level structure documentation for the RBAC role assignment object.
  url: https://raw.githubusercontent.com/api-evangelist/rbac/refs/heads/main/json-structure/rbac-assignment-structure.json
- type: JSONLDContext
  name: RBAC JSON-LD Context
  description: JSON-LD context mapping RBAC vocabulary to linked data identifiers.
  url: https://raw.githubusercontent.com/api-evangelist/rbac/refs/heads/main/json-ld/rbac-context.jsonld
- type: Examples
  name: RBAC Role Example
  description: Example RBAC role object for a Content Editor.
  url: https://raw.githubusercontent.com/api-evangelist/rbac/refs/heads/main/examples/rbac-role-example.json
- type: Examples
  name: RBAC Permission Example
  description: Example RBAC permission object for publishing content.
  url: https://raw.githubusercontent.com/api-evangelist/rbac/refs/heads/main/examples/rbac-permission-example.json
- type: Examples
  name: RBAC Assignment Example
  description: Example RBAC role assignment binding a user to the Content Editor role.
  url: https://raw.githubusercontent.com/api-evangelist/rbac/refs/heads/main/examples/rbac-assignment-example.json
- type: Vocabulary
  name: RBAC Vocabulary
  description: Domain vocabulary for RBAC concepts, terms, and implementation patterns.
  url: https://raw.githubusercontent.com/api-evangelist/rbac/refs/heads/main/vocabulary/rbac-vocabulary.yml
- type: Standards
  name: ANSI/INCITS 359-2012 RBAC Standard
  description: The American National Standard for Role-Based Access Control.
  url: https://csrc.nist.gov/projects/role-based-access-control
- type: Documentation
  name: Kubernetes RBAC Authorization
  description: Official Kubernetes documentation for RBAC authorization.
  url: https://kubernetes.io/docs/reference/access-authn-authz/rbac/
- type: Documentation
  name: AWS IAM Role-Based Access Control
  description: AWS Identity and Access Management RBAC documentation.
  url: https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider 
curl "https://apis.io/api/v1/providers/rbac"
All providers 
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose 
curl "https://apis.io/api/v1/providers/rbac/operations?limit=25"
How their score was established 
curl "https://apis.io/api/v1/providers/rbac/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.