Runtime & gateway

x-kong-security-openid-connect

`x-kong-security-openid-connect` appears on security schemes. Its value is a structured object. Used by a single provider across 9 OpenAPI documents. It sits in the `x-kong-` namespace, so its meaning is defined by kong tooling rather than by OpenAPI. Consistent with runtime & gateway — this is inferred from where the key appears and what it carries, not from any published definition.

Runtime & gateway x-kong- namespace derived description
How this description was produced. It is assembled from what was measured in the corpus — where this key appears in a document, what shape its value takes, the values observed, and how many providers use it. It is not taken from a published definition, because for most extensions none exists. Read it as evidence, not as a specification. If you own this extension and want it described properly, tell us.
9 occurrences
9 documents
1 providers
vendor-named

Where it appears

Location in the documentOccurrences
securityScheme 9

What its value looks like

Value shapeOccurrences
object9

Providers publishing it

All 1.

zinnia

Why this is not in OpenAPI

Extensions exist because a provider needed something the specification would not carry. Most of what they hold is not the API contract at all — it is operational metadata about the contract: documentation, lifecycle, policy, provenance, and now agents. That metadata is usually better placed alongside the contract, in an Overlay or an APIs.json index, than crammed inside it. See everything else doing the runtime & gateway job.