Oso Cloud
Oso Cloud is an authorization-as-a-service platform that provides a REST API for defining and enforcing relationship-based access control policies. It enables developers to model RBAC, ReBAC, and ABAC authorization patterns, manage authorization facts, and query permissions at runtime with sub-10ms latency and 99.99% availability.
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 Oso Cloud the way a machine reads it — 66 machine-readable artifacts across 4 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 — Oso Cloud scores 55.1/100 (developing), with a separate agent-readiness read of 48/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 Oso Cloud
Each block below is one kind of artifact we hold for Oso Cloud. 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 4
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.
Oso Cloud Centralized Authorization Data API
The Centralized Authorization Data API from Oso Cloud — 6 operation(s) for centralized authorization data.
Oso Cloud Check API API
The Check API API from Oso Cloud — 6 operation(s) for check api.
Oso Cloud Local Check API API
The Local Check API API from Oso Cloud — 4 operation(s) for local check api.
Oso Cloud Policy API
The Policy API from Oso Cloud — 2 operation(s) for policy.
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.
Oso 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.
Oso 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.
Oso 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.
Oso 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.
Oso Cloud API Rules
SPECTRALJSON Schema 40
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.
ActionsQuery
JSON SCHEMAActionsResult
JSON SCHEMAApiError
JSON SCHEMAApiResult
JSON SCHEMAAuthorizeQuery
JSON SCHEMAAuthorizeResourcesQuery
JSON SCHEMAAuthorizeResourcesResult
JSON SCHEMAAuthorizeResult
JSON SCHEMABulk
JSON SCHEMAConcreteFact
JSON SCHEMAConstraint
JSON SCHEMAFact
JSON SCHEMAFactChangeset
JSON SCHEMAGetPolicyMetadataResult
JSON SCHEMAGetPolicyResult
JSON SCHEMAListQuery
JSON SCHEMAListResult
JSON SCHEMALocalActionsQuery
JSON SCHEMALocalActionsResult
JSON SCHEMALocalAuthQuery
JSON SCHEMALocalAuthResult
JSON SCHEMALocalListQuery
JSON SCHEMALocalListResult
JSON SCHEMALocalQuery
JSON SCHEMALocalQueryMode
JSON SCHEMALocalQueryResult
JSON SCHEMAPolicy
JSON SCHEMAPolicyError
JSON SCHEMAPolicyFailure
JSON SCHEMAPolicyMetadata
JSON SCHEMAPolicyTestResult
JSON SCHEMAQuery
JSON SCHEMAQueryDeprecated
JSON SCHEMAQueryResult
JSON SCHEMAQueryResultDeprecated
JSON SCHEMAResourceBlockData
JSON SCHEMASavePolicyError
JSON SCHEMATestSummary
JSON SCHEMATypedId
JSON SCHEMAValue
JSON SCHEMAScroll within the panel for all 40 ·
Examples 13
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.
Delete_Facts
EXAMPLEGet_Policy_Metadata
EXAMPLEPost_Actions
EXAMPLEPost_Actions_Query
EXAMPLEPost_Authorize
EXAMPLEPost_Authorize_Query
EXAMPLEPost_Batch
EXAMPLEPost_Evaluate_Query
EXAMPLEPost_Evaluate_Query_Local
EXAMPLEPost_Facts
EXAMPLEPost_List
EXAMPLEPost_List_Query
EXAMPLEPost_Policy
EXAMPLEScroll within the panel for all 13 ·
Security 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 Oso Cloud — 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 3
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 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/oso · machine-readable index on apis.io