Aserto
Aserto is a cloud-native authorization platform providing fine-grained, policy-based access control for applications and APIs. Built on Open Policy Agent (OPA) and a Google Zanzibar-inspired directory, Aserto exposes REST and gRPC APIs for the Authorizer (real-time authorization decisions), Directory (managing users, groups, objects, and relations), and Decision Logs (audit trails of authorization events). The open-source Topaz engine carries the technology forward after the commercial SaaS control plane was wound down in May 2025.
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 Aserto the way a machine reads it — 133 machine-readable artifacts across 8 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 — Aserto scores 42.5/100 (developing), with a separate agent-readiness read of 31/100 (agent aware). 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-08-17 · rubric v0.11.0
Put this on your own site. The badge is drawn live from Aserto'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/aserto/"
title="Aserto on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/aserto.svg"
alt="Aserto Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/aserto/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/aserto/"
title="Aserto on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/aserto/card.svg"
alt="Aserto 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 Aserto
Each block below is one kind of artifact we hold for Aserto. 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 8
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.
Aserto Decision Logs API
Collects and surfaces a complete audit trail of authorization decisions made by connected Authorizer instances. Supports compliance, debugging, and analytics use cases by record...
Aserto Control Plane API
Management API for the Aserto SaaS control plane (wound down May 2025, succeeded by the open-source Topaz project). Provided lifecycle management of policies, Edge Authorizer in...
Aserto Authorizer API
The Authorizer API from Aserto — 4 operation(s) for authorizer.
Aserto authzen API
The authzen API from Aserto — 5 operation(s) for authzen.
Aserto decision_logs API
The decision_logs API from Aserto — 6 operation(s) for decision_logs.
Aserto directory API
The directory API from Aserto — 14 operation(s) for directory.
Aserto Info API
The Info API from Aserto — 1 operation(s) for info.
Aserto Policy API
The Policy API from Aserto — 2 operation(s) for policy.
Scroll within the panel for all 8 ·
Open Collections 7
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 COLLECTIONaserto//v2/.proto Authorizer API
OPEN COLLECTIONaserto//v2/.proto Authorizer authzen API
OPEN COLLECTIONaserto//v2/.proto Authorizer decision_logs API
OPEN COLLECTIONaserto//v2/.proto Authorizer directory API
OPEN COLLECTIONaserto//v2/.proto Authorizer Info API
OPEN COLLECTIONaserto//v2/.proto Authorizer Policy API
OPEN COLLECTIONScroll within the panel for all 7 ·
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.
Aserto Plans Pricing
PLANSRate 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.
Aserto 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.
Aserto Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Aserto Context
JSON-LDSpectral 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.
Aserto API Rules
SPECTRALJSON Schema 107
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
apiIdentityContext
JSON SCHEMAapiIdentityType
JSON SCHEMAapiModule
JSON SCHEMAapiPolicyContext
JSON SCHEMAapiPolicyInstance
JSON SCHEMAauthorizerv2Decision
JSON SCHEMAprotobufAny
JSON SCHEMAprotobufNullValue
JSON SCHEMArpcStatus
JSON SCHEMAv2CompileRequest
JSON SCHEMAv2CompileResponse
JSON SCHEMAv2DecisionTreeOptions
JSON SCHEMAv2DecisionTreeRequest
JSON SCHEMAv2DecisionTreeResponse
JSON SCHEMAv2GetPolicyResponse
JSON SCHEMAv2InfoResponse
JSON SCHEMAv2IsRequest
JSON SCHEMAv2IsResponse
JSON SCHEMAv2ListPoliciesResponse
JSON SCHEMAv2QueryOptions
JSON SCHEMAv2QueryRequest
JSON SCHEMAv2QueryResponse
JSON SCHEMAprotobufAny
JSON SCHEMAprotobufNullValue
JSON SCHEMArpcStatus
JSON SCHEMAv2DecisionLog
JSON SCHEMAv2DecisionLogItem
JSON SCHEMAv2ExecuteQueryRequest
JSON SCHEMAv2ExecuteQueryResponse
JSON SCHEMAv2GetDecisionLogResponse
JSON SCHEMAv2GetDecisionsResponse
JSON SCHEMAv2GetUserResponse
JSON SCHEMAv2IdentityContext
JSON SCHEMAv2IdentityType
JSON SCHEMAv2ListDecisionLogsResponse
JSON SCHEMAv2ListUsersResponse
JSON SCHEMAv2PaginationRequest
JSON SCHEMAv2PaginationResponse
JSON SCHEMAv2PolicyContext
JSON SCHEMAv2PolicyInstance
JSON SCHEMAv2Result
JSON SCHEMAv2User
JSON SCHEMAv2UserItem
JSON SCHEMAprotobufAny
JSON SCHEMAprotobufNullValue
JSON SCHEMArpcStatus
JSON SCHEMAv1Page
JSON SCHEMAv3Assert
JSON SCHEMAv3Body
JSON SCHEMAv3CheckPermissionRequest
JSON SCHEMAv3CheckPermissionResponse
JSON SCHEMAv3CheckRelationRequest
JSON SCHEMAv3CheckRelationResponse
JSON SCHEMAv3CheckRequest
JSON SCHEMAv3CheckResponse
JSON SCHEMAEXPERIMENTAL
JSON SCHEMAEXPERIMENTAL
JSON SCHEMAv3DeleteAssertionResponse
JSON SCHEMAv3DeleteManifestResponse
JSON SCHEMAv3DeleteObjectResponse
JSON SCHEMAv3DeleteRelationResponse
JSON SCHEMAv3ExportResponse
JSON SCHEMAv3GetAssertionResponse
JSON SCHEMAv3GetGraphResponse
JSON SCHEMAv3GetManifestResponse
JSON SCHEMAv3GetObjectManyResponse
JSON SCHEMAv3GetObjectResponse
JSON SCHEMAv3GetObjectsResponse
JSON SCHEMAv3GetRelationResponse
JSON SCHEMAv3GetRelationsResponse
JSON SCHEMAv3ImportCounter
JSON SCHEMAv3ImportRequest
JSON SCHEMAv3ImportResponse
JSON SCHEMAv3ImportStatus
JSON SCHEMAv3ListAssertionsResponse
JSON SCHEMAv3Metadata
JSON SCHEMAv3Object
JSON SCHEMAObject identifier
JSON SCHEMAv3Opcode
JSON SCHEMAPagination request
JSON SCHEMAPagination response
JSON SCHEMAv3Relation
JSON SCHEMAv3SetAssertionRequest
JSON SCHEMAv3SetAssertionResponse
JSON SCHEMAv3SetManifestResponse
JSON SCHEMAv3SetObjectRequest
JSON SCHEMAv3SetObjectResponse
JSON SCHEMAv3SetRelationRequest
JSON SCHEMAv3SetRelationResponse
JSON SCHEMAScroll within the panel for all 107 ·
Examples 3
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Aserto Authorizer Examples
EXAMPLEAserto Directory Examples
EXAMPLESecurity Posture 2
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 Aserto — 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.
Documentation 1
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 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
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/aserto · machine-readable index on apis.io
This is an independent, third-party profile of Aserto, 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.