Opal Security
Opal Security (legal entity Perma Security, Inc.) is a next-generation access management and identity security platform that gives enterprises comprehensive visibility into access across their systems, orchestrates just-in-time and least-privilege access, designs intelligent access policies, and automates user access reviews (UARs). Opal exposes a RESTful API at https://api.opal.dev/v1 covering apps, resources, groups, users, bundles, access requests, access rules, owners, events, event streaming, sessions, and tokens, plus official SDKs (Python, Go), a CLI, a Terraform provider, and three hosted Model Context Protocol (MCP) servers for AI agents. Backed by Greylock. Sector: cybersecurity.
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 Opal Security the way a machine reads it — 51 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 — Opal Security scores 50.7/100 (developing), with a separate agent-readiness read of 40/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 Opal Security'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/opal-security/"
title="Opal Security on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/opal-security.svg"
alt="Opal Security Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/opal-security/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/opal-security/"
title="Opal Security on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/opal-security/card.svg"
alt="Opal Security 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 Opal Security
Each block below is one kind of artifact we hold for Opal Security. 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 22
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.
Opal Security access-rules API
Operations related to access rules
Opal Security apps API
Operations related to apps
Opal Security bundles API
Operations related to bundles
Opal Security configuration-templates API
Operations related to configuration templates
Opal Security delegations API
Operations related to request reviewer delegations
Opal Security event-streams API
Operations related to event streaming connections
Opal Security events API
Operations related to events
Opal Security group-bindings API
Operations related to group bindings
Opal Security groups API
Operations related to groups
Opal Security idp-group-mappings API
Operations related to IDP group mappings
Opal Security message-channels API
Operations related to message channels
Opal Security non-human-identities API
Operations related to non-human identities
Opal Security on-call-schedules API
Operations related to on-call schedules
Opal Security opal-queries API
Operations related to OpalQuery
Opal Security owners API
Operations related to owners
Opal Security requests API
Operations related to requests
Opal Security resources API
Operations related to resources
Opal Security sessions API
Operations related to sessions
Opal Security tags API
Operations related to tags
Opal Security tokens API
Operations related to API tokens
Opal Security uars API
Operations related to UARs
Opal Security users API
Operations related to users
Scroll within the panel for all 22 ·
Open Collections 23
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).
API Collection
OPEN COLLECTIONOpal access-rules API
OPEN COLLECTIONOpal access-rules apps API
OPEN COLLECTIONOpal access-rules bundles API
OPEN COLLECTIONOpal access-rules configuration-templates API
OPEN COLLECTIONOpal access-rules delegations API
OPEN COLLECTIONOpal access-rules event-streams API
OPEN COLLECTIONOpal access-rules events API
OPEN COLLECTIONOpal access-rules group-bindings API
OPEN COLLECTIONOpal access-rules groups API
OPEN COLLECTIONOpal access-rules idp-group-mappings API
OPEN COLLECTIONOpal access-rules message-channels API
OPEN COLLECTIONOpal access-rules non-human-identities API
OPEN COLLECTIONOpal access-rules on-call-schedules API
OPEN COLLECTIONOpal access-rules opal-queries API
OPEN COLLECTIONOpal access-rules owners API
OPEN COLLECTIONOpal access-rules requests API
OPEN COLLECTIONOpal access-rules resources API
OPEN COLLECTIONOpal access-rules sessions API
OPEN COLLECTIONOpal access-rules tags API
OPEN COLLECTIONOpal access-rules tokens API
OPEN COLLECTIONOpal access-rules uars API
OPEN COLLECTIONOpal access-rules users API
OPEN COLLECTIONScroll within the panel for all 23 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
Opal Security MCP Server
Opal Security hosts three specialized, self-hosted Model Context Protocol (MCP) servers that let AI agents interact with the Opal access-management platform through its REST API...
MCP SERVEREvent 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.
Opal Security Events Webhooks
ASYNCAPISecurity Posture 4
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.
Resources
Every other property we hold for Opal Security — 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 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/opal-security · machine-readable index on apis.io
This is an independent, third-party profile of Opal Security, 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.