OpenAPI
OpenAPI (formerly Swagger Specification) is a standard, language-agnostic specification for describing RESTful APIs in a machine-readable format. It enables automated documentation generation, client code generation, and API testing, serving as a contract between API providers and consumers.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles OpenAPI the way a machine reads it — 61 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 — OpenAPI scores 34.2/100 (thin), with a separate agent-readiness read of 7/100 (human only). 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 OpenAPI
Each block below is one kind of artifact we hold for OpenAPI. 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 1
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.
OpenAPI Specification
The OpenAPI Specification (OAS) defines a standard, programming language-agnostic interface description for HTTP APIs.
Open Collections 29
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 COLLECTIONAPI Collection
OPEN COLLECTIONAPI Collection
OPEN COLLECTIONAPI Collection
OPEN COLLECTIONAPI Collection
OPEN COLLECTIONAPI Collection
OPEN COLLECTIONAPI Collection
OPEN COLLECTIONAPI Collection
OPEN COLLECTIONAPI Collection
OPEN COLLECTIONAPI Collection
OPEN COLLECTIONAPI Collection
OPEN COLLECTIONAPI Collection
OPEN COLLECTIONAPI Collection
OPEN COLLECTIONAPI Collection
OPEN COLLECTIONAPI Collection
OPEN COLLECTIONAPI Collection
OPEN COLLECTIONAPI Collection
OPEN COLLECTIONAPI Collection
OPEN COLLECTIONAPI Collection
OPEN COLLECTIONAPI Collection
OPEN COLLECTIONAPI Collection
OPEN COLLECTIONAPI Collection
OPEN COLLECTIONAPI Collection
OPEN COLLECTIONAPI Collection
OPEN COLLECTIONAPI Collection
OPEN COLLECTIONAPI Collection
OPEN COLLECTIONAPI Collection
OPEN COLLECTIONAPI Collection
OPEN COLLECTIONAPI Collection
OPEN COLLECTIONScroll within the panel for all 29 ·
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.
Rate 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.
Openapi 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.
Openapi 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.
Openapi 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.
OpenAPI API Rules
SPECTRALJSON Schema 25
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.
OpenAPI Components Object
JSON SCHEMAOpenAPI Contact Object
JSON SCHEMAOpenAPI Document
JSON SCHEMAOpenAPI Encoding Object
JSON SCHEMAOpenAPI Example Object
JSON SCHEMAOpenAPI External Documentation Object
JSON SCHEMAOpenAPI Header Object
JSON SCHEMAOpenAPI Info Object
JSON SCHEMAOpenAPI License Object
JSON SCHEMAOpenAPI Link Object
JSON SCHEMAOpenAPI Media Type Object
JSON SCHEMAOpenAPI OAuth Flow Object
JSON SCHEMAOpenAPI OAuth Flows Object
JSON SCHEMAOpenAPI Operation Object
JSON SCHEMAOpenAPI Parameter Object
JSON SCHEMAOpenAPI Path Item Object
JSON SCHEMAOpenAPI Paths Object
JSON SCHEMAOpenAPI Request Body Object
JSON SCHEMAOpenAPI Response Object
JSON SCHEMAOpenAPI Responses Object
JSON SCHEMAOpenAPI Security Requirement Object
JSON SCHEMAOpenAPI Security Scheme Object
JSON SCHEMAOpenAPI Server Variable Object
JSON SCHEMAOpenAPI Server Object
JSON SCHEMAOpenAPI Tag Object
JSON SCHEMAScroll within the panel for all 25 ·
Security Posture 1
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 OpenAPI — 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 1
Authentication, authorization, and security posture
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/openapi · machine-readable index on apis.io