Visibility

x-internal

`x-internal` appears on schema objects and properties and on operations. Its value is a boolean flag. Used by 88 providers across 253 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.

Also published under another name. This key exists in the wild spelled more than one way — differing only by case or a hyphen, which means no tool can treat them as the same thing: x-Internal. Each is catalogued separately here because that is how they exist.

4951 occurrences

253 documents

88 providers

purpose-named

Where it appears

Location in the document	Occurrences
operation	1505
schema	3150
path	77
info	2
response	13
requestBody	15
root	49
server	25
other	92
parameter	6
tag	11
securityScheme	4
components	2

What its value looks like

Value shape	Occurrences
boolean	4938
string	6
object	7

Observed values

Sampled from the specifications, most frequent first.

falsetruein ui this will be a select list of the pages on the service

Providers publishing it

Showing 50 of 88.

aftership alpaca apollo-insurance armor axlehire back-market beeceptor bigcommerce bond canonical creatoriq cybelangel delphix demandbase dropbox egym emarsys eon equipmentwatch ev-energy figshare finicity finix finix-payments fireblocks fixflo folk gr4vy gumlet habu harness insforge instaclustr ironcore-labs iugu kontaktio lianlian-global lili livelike liveramp lucidya-ltd mailmodo mediamath merqube netcorecloud netlify nuclei ok-capsule opaque openchargemap

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.