







OpenAPI, AsyncAPI, JSON Schema, Arazzo, Overlay, Spectral, APIs.json, MCP, A2A, GraphQL, gRPC, JSON-RPC, OAuth 2.0, OpenID Connect, Protected Resource Metadata, Dynamic Client Registration, Agent Skills, the AI Catalog, the RFC 9727 API Catalog, UCP and ORD — read from their published schemas, mapped by what each one points at, which property does which job, and how much vocabulary they share.
OpenAI Model Spec
The Model Spec specifies desired behavior for the models underlying OpenAI's products (including our APIs).

You See a Spec, I See a Common Language, and a Common Understanding
Many engineers I’ve worked with over the years see OpenAPI and AsyncAPI as a configuration for whatever tooling outcome they desire. I see OpenAPI, AsyncAPI,...

The Arazzo Specification v1.1.0
The Arazzo Specification provides a mechanism that can define sequences of calls and their dependencies to be woven together and expressed in the context of delivering a particular outcome or set of outcomes when dealing with API descriptions (such as OpenAPI descriptions)
Tools for working with OpenAPI | OpenAPI.tools
A comprehensive and open source list of resources for developers working with OpenAPI.

oauth-client-metadata.json | AT Protocol Community Wiki
A community-maintained wiki for the AT Protocol ecosystem
Schema-Validated, Rules-Guided, and Policy-Driven Experiences
I struggle to share the entirety of my vision for API governance as it requires prior awareness of multiple API specifications and the current state of gover...

The Specification Is Not a Document - The Phoenix Architecture
Imagine joining a software project a few years from now. It is a large, mature system. It has thousands of business rules, years of operational experience,…

OAuth Client ID Metadata Document
This specification defines a mechanism through which an OAuth client can identify itself to authorization servers, without prior dynamic client registration or other existing registration. This is through the usage of a URL as a client_id in an OAuth flow, where the URL refers to a document containing the necessary client metadata, enabling the authorization server to fetch the metadata about the client as needed.

OAuth Client ID Metadata Document
This specification defines a mechanism through which an OAuth client can identify itself to authorization servers, without prior dynamic client registration or other existing registration. This is through the usage of a URL as a client_id in an OAuth flow, where the URL refers to a document containing the necessary client metadata, enabling the authorization server to fetch the metadata about the client as needed.

hey-api/openapi-ts
🌀 OpenAPI to TypeScript codegen. Production-ready SDKs, Zod schemas, TanStack Query hooks, and 20+ plugins. Used by Vercel, OpenCode, and PayPal.
OpenAPI 3.x Extensions in API Gateway | Google Cloud Documentation
API Gateway accepts a set of Google-specific extensions to the OpenAPI specification that configure the behaviors of the gateway. These extensions allow you to specify API management settings, authentication methods, quota limits, and backend integrations directly within your OpenAPI document. Understanding these extensions helps you tailor your service behavior and integrate with API Gateway features.
Using and publishing Open Data and Information
Detailed guidance on working with data and APIs, guidance for institutions to publish proactive publications, open data and information. Using Open Data How to work with data and APIs Information and tips using some of the formats presented in the Open Data Portal

