x-internal

`x-internal` appears on schema objects and properties. Its value is a boolean flag. Used by 65 providers across 165 OpenAPI documents. Consistent with visibility — this is inferred from where the key appears and what it carries, not from any published definition.

Visibility 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.
1918 occurrences
165 documents
65 providers
purpose-named

Where it appears

Location in the documentOccurrences
schema 1370
operation 473
path 26
info 1
response 1
requestBody 1
server 2
root 29
other 3
parameter 6
components 2
tag 4

What its value looks like

Value shapeOccurrences
boolean1913
string5

Observed values

Sampled from the specifications, most frequent first.

falsetrue

Providers publishing it

Showing 50 of 65.

alpacaarmoraxlehireback-marketbeeceptorbigcommercecreatoriqdeakindeliverectdelphixdropboxeonerasmus-university-rotterdamev-energyfigsharefinixfinix-paymentsfireblocksfolkhabuhbkuhoneycomb-ioinsforgeironcore-labslianlian-globalliveramploughboroughlucidya-ltdmacquariemailmodonetlifynucleiopaqueopenchargemapordoropadletpalo-alto-networkspolygon-idprojectdiscoverypunchhqoveryqwiet-airegal-airentchecksendhubship24signwellsmallstepspreespree-commerce

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 visibility job.