Data & schema semantics
1336 distinct extensions were invented to do this job. Each one is a provider deciding OpenAPI would not carry something and building their own way through. Where a job has many names and few uses each, nobody won — the problem was solved privately, over and over.
1336 extensions
221735 occurrences
403 vendor-named
Inside this job
Identity & relationships128
Type system114
Validation & constraints64
Naming & aliasing56
Units & formatting36
Size & shape31
Defaults & examples20
Mutability & access16
Ordering & sorting11
The extensions
| Extension | What it appears to do | Uses | Providers |
|---|---|---|---|
|
x-microcks-default
vendor |
`x-microcks-default` appears on response objects. Its value is a boolean flag. Used by 442 providers across 988 OpenAPI documents. It sits in the `x-microcks-` namespace, so its meaning is defined by | 30352 | 442 |
|
x-microcks-operation
vendor |
`x-microcks-operation` appears on operations. Its value is a structured object. Used by 625 providers across 1,583 OpenAPI documents. It sits in the `x-microcks-` namespace, so its meaning is defined | 26468 | 625 |
| x-cds-type | `x-cds-type` appears on schema objects and properties. Its value is a string. Used by 40 providers across 41 OpenAPI documents. Observed values include `PositiveInteger`, `AmountString`, `URIString`, | 7574 | 40 |
|
x-github
vendor |
`x-github` appears on operations. Its value is a structured object. Used by 3 providers across 39 OpenAPI documents. It sits in the `x-github-` namespace, so its meaning is defined by github tooling r | 6792 | 3 |
|
x-ms-enum
vendor |
`x-ms-enum` appears on schema objects and properties. Its value is a structured object. Used by 14 providers across 578 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is defined b | 6723 | 14 |
|
x-stoplight
vendor |
`x-stoplight` appears on schema objects and properties. Its value is a structured object. Used by 23 providers across 128 OpenAPI documents. It sits in the `x-stoplight-` namespace, so its meaning is | 6161 | 23 |
| x-related-resource | `x-related-resource` appears on operations. Its value is a string. Used by a single provider across 158 OpenAPI documents. Observed values include `#/definitions/WorkRequest`, `#/definitions/ManagedDa | 5821 | 1 |
|
x-speakeasy-unknown-values
vendor |
`x-speakeasy-unknown-values` appears on schema objects and properties. Its value is a string. Used by 9 providers across 21 OpenAPI documents. It sits in the `x-speakeasy-` namespace, so its meaning i | 5170 | 9 |
| x-default-description | `x-default-description` appears on parameter objects. Its value is a string. Used by a single provider across 149 OpenAPI documents. Observed values include `null`, `The default value depends upon `so | 4594 | 1 |
| x-nullable | `x-nullable` appears on schema objects and properties. Its value is a boolean flag. Used by 31 providers across 121 OpenAPI documents. Consistent with type system — this is inferred from where the key | 4379 | 31 |
|
x-ms-discriminator-value
vendor |
`x-ms-discriminator-value` appears on schema objects and properties. Its value is a string. Used by 4 providers across 198 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is define | 4051 | 4 |
|
x-obmcs-top-level-enum
vendor |
`x-obmcs-top-level-enum` appears on schema objects and properties. Its value is a string. Used by a single provider across 122 OpenAPI documents. It sits in the `x-obmcs-` namespace, so its meaning is | 4039 | 1 |
| x-struct | `x-struct` appears on schema objects and properties. Its value is a string. Used by a single provider across 12 OpenAPI documents. Observed values include `null`, `Elixir.SwitchboardWeb.V1.Specs.PageI | 3505 | 1 |
| x-api-evangelist-processing | `x-api-evangelist-processing` appears on operations. Its value is a structured object. Used by 9 providers across 48 OpenAPI documents. Consistent with data & schema semantics — this is inferred from | 3475 | 9 |
|
x-speakeasy-name-override
vendor |
`x-speakeasy-name-override` appears on operations and on schema objects and properties. Its value is a string. Used by 23 providers across 34 OpenAPI documents. It sits in the `x-speakeasy-` namespace | 3463 | 23 |
|
x-ms-parameter-location
vendor |
`x-ms-parameter-location` appears on parameter objects. Its value is a string. Used by 9 providers across 536 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is defined by ms tooli | 3023 | 9 |
| x-schema-id | `x-schema-id` appears on schema objects and properties. Its value is a string. Used by 3 providers across 14 OpenAPI documents. Observed values include `LocalizedStrings`, `HybridIdentifier`, `Amount` | 2801 | 3 |
| x-conditional | `x-conditional` appears on operations and on schema objects and properties. Its value is a boolean flag. Used by 40 providers across 41 OpenAPI documents. Consistent with validation & constraints — th | 2501 | 40 |
|
x-ms-long-running-operation
vendor |
`x-ms-long-running-operation` appears on operations and on path items. Its value is a boolean flag. Used by 11 providers across 299 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning | 2380 | 11 |
|
x-ms-identifiers
vendor |
`x-ms-identifiers` appears on schema objects and properties. It is used as a marker with no value. Used by a single provider across 240 OpenAPI documents. It sits in the `x-ms-` namespace, so its mean | 2362 | 1 |
|
x-ms-client-flatten
vendor |
`x-ms-client-flatten` appears on schema objects and properties. Its value is a boolean flag. Used by 11 providers across 363 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is defi | 2209 | 11 |
| x-allOf | `x-allOf` appears on schema objects and properties. Its value is a list. Used by a single provider across 1 OpenAPI document. Consistent with type system — this is inferred from where the key appears | 1973 | 1 |
| x-spec-enum-id | `x-spec-enum-id` appears on operations and on schema objects and properties. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `65feb4244cc9110c`, `26 | 1656 | 1 |
| x-positive | `x-positive` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 15 OpenAPI documents. Consistent with type system — this is inferred from where the | 1613 | 1 |
| x-v | `x-v` appears on header objects. Its value is a structured object. Used by 40 providers across 41 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the key appea | 1484 | 40 |
|
x-atlassian-data-security-policy
vendor |
`x-atlassian-data-security-policy` appears on operations. Its value is a list. Used by a single provider across 91 OpenAPI documents. It sits in the `x-atlassian-` namespace, so its meaning is defined | 1443 | 1 |
|
x-obmcs-client-retries-enabled
vendor |
`x-obmcs-client-retries-enabled` appears on operations. Its value is a boolean flag. Used by a single provider across 119 OpenAPI documents. It sits in the `x-obmcs-` namespace, so its meaning is defi | 1345 | 1 |
|
x-obmcs-enumref
vendor |
`x-obmcs-enumref` appears on schema objects and properties and on parameter objects. Its value is a string. Used by a single provider across 104 OpenAPI documents. It sits in the `x-obmcs-` namespace, | 1328 | 1 |
|
x-ms-mutability
vendor |
`x-ms-mutability` appears on schema objects and properties. Its value is a list. Used by 6 providers across 177 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is defined by ms too | 1230 | 6 |
|
x-ms-long-running-operation-options
vendor |
`x-ms-long-running-operation-options` appears on operations and on path items. Its value is a structured object. Used by 4 providers across 162 OpenAPI documents. It sits in the `x-ms-` namespace, so | 1129 | 4 |
| x-add-datatype | `x-add-datatype` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred | 1127 | 1 |
|
x-ms-parameter-grouping
vendor |
`x-ms-parameter-grouping` appears on parameter objects. Its value is a structured object. Used by a single provider across 19 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is def | 1087 | 1 |
| x-value | `x-value` appears on schema objects and properties. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `Aim`, `Automation`, `CampaignPoll`, `Conversati | 1087 | 1 |
| x-enum-varnames | `x-enum-varnames` appears on schema objects and properties. Its value is a list. Used by 50 providers across 78 OpenAPI documents. Observed values include `[INPUT, FILTER, PRE_OUTPUT, OUTPUT]`, `['Use | 1084 | 50 |
|
x-junction-exhaustive
vendor |
`x-junction-exhaustive` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 8 OpenAPI documents. It sits in the `x-junction-` namespace, so its mean | 1032 | 1 |
| x-anyOf | `x-anyOf` appears on schema objects and properties. Its value is a list. Used by 3 providers across 6 OpenAPI documents. Consistent with type system — this is inferred from where the key appears and w | 1004 | 3 |
|
x-speakeasy-entity-operation
vendor |
`x-speakeasy-entity-operation` appears on operations. Its value is a structured object. Used by 4 providers across 5 OpenAPI documents. It sits in the `x-speakeasy-` namespace, so its meaning is defin | 988 | 4 |
| x-maturity | `x-maturity` appears on operations. Its value is a list. Used by a single provider across 32 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the key appears an | 981 | 1 |
| x-enumDescriptions | `x-enumDescriptions` appears on schema objects and properties. Its value is a list. Used by 23 providers across 53 OpenAPI documents. Observed values include `*ref_91`, `&ref_91`. Consistent with type | 929 | 23 |
| x-enum-descriptions | `x-enum-descriptions` appears on schema objects and properties. Its value is a structured object. Used by 15 providers across 44 OpenAPI documents. Consistent with type system — this is inferred from | 919 | 15 |
| x-referenceable | `x-referenceable` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 2 OpenAPI documents. Consistent with identity & relationships — this is inferr | 910 | 1 |
| x-allowNullValue | `x-allowNullValue` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 9 OpenAPI documents. Consistent with data & schema semantics — this is inferr | 862 | 1 |
|
x-ms-error-response
vendor |
`x-ms-error-response` appears on response objects. Its value is a boolean flag. Used by 2 providers across 43 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is defined by ms tooli | 844 | 2 |
|
x-ds-definition-name
vendor |
`x-ds-definition-name` appears on schema objects and properties. Its value is a string. Used by a single provider across 6 OpenAPI documents. It sits in the `x-ds-` namespace, so its meaning is define | 843 | 1 |
|
x-stainless-const
vendor |
`x-stainless-const` appears on schema objects and properties. Its value is a boolean flag. Used by 5 providers across 5 OpenAPI documents. It sits in the `x-stainless-` namespace, so its meaning is de | 818 | 5 |
| x-enumNames | `x-enumNames` appears on schema objects and properties. Its value is a list. Used by 12 providers across 20 OpenAPI documents. Consistent with type system — this is inferred from where the key appears | 771 | 12 |
| x-version | `x-version` appears on operations. Its value is a string. Used by 42 providers across 42 OpenAPI documents. Observed values include `2`, `1`, `3`, `5`. Consistent with data & schema semantics — this i | 764 | 42 |
| x-correlator | `x-correlator` appears on header objects. Its value is a structured object. Used by 3 providers across 58 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the k | 751 | 3 |
|
x-twilio
vendor |
`x-twilio` appears on path items. Its value is a structured object. Used by a single provider across 32 OpenAPI documents. It sits in the `x-twilio-` namespace, so its meaning is defined by twilio too | 746 | 1 |
|
x-mint
vendor |
`x-mint` appears on operations. Its value is a structured object. Used by 25 providers across 61 OpenAPI documents. It sits in the `x-mint-` namespace, so its meaning is defined by mint tooling rather | 745 | 25 |
| x-iam-actions | `x-iam-actions` appears on operations. Its value is a list. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from where the key appears a | 716 | 1 |
| x-oaiMeta | `x-oaiMeta` appears on schema objects and properties and on operations. Its value is a structured object. Used by 2 providers across 12 OpenAPI documents. Consistent with data & schema semantics — thi | 679 | 2 |
|
x-fabric-request-id
vendor |
`x-fabric-request-id` appears on header objects. Its value is a structured object. Used by a single provider across 10 OpenAPI documents. It sits in the `x-fabric-` namespace, so its meaning is define | 651 | 1 |
| x-alternatives | `x-alternatives` appears on schema objects and properties and on operations. Its value is a list. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is | 604 | 1 |
|
x-konfig-generated-schema
vendor |
`x-konfig-generated-schema` appears on schema objects and properties. Its value is a string. Used by a single provider across 1 OpenAPI document. It sits in the `x-konfig-` namespace, so its meaning i | 600 | 1 |
| x-enum-description | `x-enum-description` appears on schema objects and properties. Its value is a list. Used by a single provider across 15 OpenAPI documents. Consistent with type system — this is inferred from where the | 595 | 1 |
| x-description-1 | `x-description-1` appears on response objects. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `Invalid signature received for JSON Web Token valida | 591 | 1 |
|
x-plaid-business-unit-context
vendor |
`x-plaid-business-unit-context` appears on path items. Its value is a string. Used by a single provider across 37 OpenAPI documents. It sits in the `x-plaid-` namespace, so its meaning is defined by p | 581 | 1 |
| x-type-name | `x-type-name` appears on schema objects and properties and on parameter objects. Its value is a string. Used by a single provider across 16 OpenAPI documents. Observed values include `UtcDateTime`, `D | 561 | 1 |
|
x-ms-azure-resource
vendor |
`x-ms-azure-resource` appears on schema objects and properties. Its value is a boolean flag. Used by 11 providers across 215 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is defi | 543 | 11 |
| x-response-codes | `x-response-codes` appears on response objects. Its value is a structured object. Used by a single provider across 24 OpenAPI documents. Consistent with data & schema semantics — this is inferred from | 512 | 1 |
|
x-xgen-version
vendor |
`x-xgen-version` appears on response objects. Its value is a string. Used by a single provider across 1 OpenAPI document. It sits in the `x-xgen-` namespace, so its meaning is defined by xgen tooling | 502 | 1 |
|
x-ms-request-id
vendor |
`x-ms-request-id` appears on header objects and on operations. Its value is a structured object. Used by 2 providers across 23 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is de | 487 | 2 |
|
x-ds-method
vendor |
`x-ds-method` appears on operations. Its value is a string. Used by a single provider across 6 OpenAPI documents. It sits in the `x-ds-` namespace, so its meaning is defined by ds tooling rather than | 484 | 1 |
|
x-ds-service
vendor |
`x-ds-service` appears on operations. Its value is a string. Used by a single provider across 6 OpenAPI documents. It sits in the `x-ds-` namespace, so its meaning is defined by ds tooling rather than | 484 | 1 |
|
x-apideck-schema-id
vendor |
`x-apideck-schema-id` appears on schema objects and properties. Its value is a string. Used by a single provider across 4 OpenAPI documents. It sits in the `x-apideck-` namespace, so its meaning is de | 478 | 1 |
| x-evidence | `x-evidence` appears in the info block. Its value is a list. Used by 25 providers across 427 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the key appears an | 469 | 25 |
|
x-aws-operation-name
vendor |
`x-aws-operation-name` appears on operations. Its value is a string. Used by 3 providers across 3 OpenAPI documents. It sits in the `x-aws-` namespace, so its meaning is defined by aws tooling rather | 466 | 3 |
|
x-portone-description
vendor |
`x-portone-description` appears on operations and on schema objects and properties. Its value is a string. Used by a single provider across 1 OpenAPI document. It sits in the `x-portone-` namespace, s | 456 | 1 |
|
x-apifox-name
vendor |
`x-apifox-name` appears on response objects. Its value is a string. Used by 3 providers across 4 OpenAPI documents. It sits in the `x-apifox-` namespace, so its meaning is defined by apifox tooling ra | 454 | 3 |
| x-required-privilege | `x-required-privilege` appears on operations. Its value is a structured object. Used by a single provider across 20 OpenAPI documents. Consistent with validation & constraints — this is inferred from | 448 | 1 |
| x-required-privileges | `x-required-privileges` appears on operations. Its value is a list. Used by a single provider across 20 OpenAPI documents. Consistent with validation & constraints — this is inferred from where the ke | 448 | 1 |
| x-errors | `x-errors` appears on response objects. Its value is a list. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from where the key appears | 440 | 1 |
| x-operation-name | `x-operation-name` appears on operations. Its value is a string. Used by 3 providers across 4 OpenAPI documents. Observed values include `get`, `list`, `delete`, `update`. Consistent with naming & ali | 438 | 3 |
| x-exegesis-controller | `x-exegesis-controller` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `Organization`, `Delivery`, `User`, `Location`. Consi | 437 | 1 |
|
x-ibm-ahub-byok
vendor |
`x-ibm-ahub-byok` appears on operations. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. It sits in the `x-ibm-` namespace, so its meaning is defined by ibm tooling r | 429 | 1 |
| x-disallowUser | `x-disallowUser` appears on operations. Its value is a boolean flag. Used by a single provider across 17 OpenAPI documents. Consistent with validation & constraints — this is inferred from where the k | 424 | 1 |
|
x-apifox-folder
vendor |
`x-apifox-folder` appears on operations. Its value is a string. Used by 3 providers across 4 OpenAPI documents. It sits in the `x-apifox-` namespace, so its meaning is defined by apifox tooling rather | 400 | 3 |
|
x-apifox-status
vendor |
`x-apifox-status` appears on operations. Its value is a string. Used by 3 providers across 4 OpenAPI documents. It sits in the `x-apifox-` namespace, so its meaning is defined by apifox tooling rather | 396 | 3 |
| x-run-in-apifox | `x-run-in-apifox` appears on operations. Its value is a string. Used by 3 providers across 4 OpenAPI documents. Observed values include `https://app.apifox.com/web/project/7948067/apis/api-430293359-r | 396 | 3 |
| x-accepts | `x-accepts` appears on operations. Its value is a string. Used by 7 providers across 10 OpenAPI documents. Observed values include `application/json`. Consistent with data & schema semantics — this is | 378 | 7 |
| x-isnullable | `x-isnullable` appears on schema objects and properties. Its value is a boolean flag. Used by 2 providers across 2 OpenAPI documents. Consistent with type system — this is inferred from where the key | 353 | 2 |
| x-is-money | `x-is-money` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 8 OpenAPI documents. Consistent with type system — this is inferred from where the | 351 | 1 |
| x-operation-settings | `x-operation-settings` appears on operations. Its value is a structured object. Used by 6 providers across 17 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where t | 351 | 6 |
|
x-fds-fql-formula
vendor |
`x-fds-fql-formula` appears on schema objects and properties. Its value is a string. Used by a single provider across 4 OpenAPI documents. It sits in the `x-fds-` namespace, so its meaning is defined | 350 | 1 |
|
x-box-resource-id
vendor |
`x-box-resource-id` appears on schema objects and properties. Its value is a string. Used by a single provider across 51 OpenAPI documents. It sits in the `x-box-` namespace, so its meaning is defined | 346 | 1 |
| x-properties | `x-properties` appears on operations and in the document. Its value is a structured object. Used by 2 providers across 129 OpenAPI documents. Consistent with data & schema semantics — this is inferred | 346 | 2 |
|
x-ms-skip-url-encoding
vendor |
`x-ms-skip-url-encoding` appears on parameter objects. Its value is a boolean flag. Used by 2 providers across 163 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is defined by ms | 339 | 2 |
| x-enum-elements | `x-enum-elements` appears on schema objects and properties. Its value is a list. Used by 9 providers across 15 OpenAPI documents. Consistent with type system — this is inferred from where the key appe | 337 | 9 |
| x-trace-id | `x-trace-id` appears on header objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with identity & relationships — this is inferred from where th | 332 | 1 |
| x-body-name | `x-body-name` appears on request bodies. Its value is a string. Used by 3 providers across 6 OpenAPI documents. Observed values include `body`, `source`, `environment`, `engine_id`. Consistent with na | 324 | 3 |
|
x-obmcs-terraform
vendor |
`x-obmcs-terraform` appears on operations. Its value is a structured object. Used by a single provider across 47 OpenAPI documents. It sits in the `x-obmcs-` namespace, so its meaning is defined by ob | 324 | 1 |
| x-extra-attributes | `x-extra-attributes` appears on response objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with size & shape — this is inferred from where the | 317 | 1 |
| x-practice-access | `x-practice-access` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `share_patients" need to be set for data access among pra | 316 | 1 |
| x-constraint | `x-constraint` appears on schema objects and properties and on operations. Its value is a structured object. Used by 2 providers across 2 OpenAPI documents. Consistent with validation & constraints — | 307 | 2 |
| x-description-2 | `x-description-2` appears on response objects. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `Client is not global.`, `Invalid signature received | 305 | 1 |
| x-endpoint-status | `x-endpoint-status` appears on operations. Its value is a string. Used by 13 providers across 13 OpenAPI documents. Observed values include `confirmed`, `modeled`. Consistent with data & schema semant | 304 | 13 |
| x-go-type | `x-go-type` appears on schema objects and properties. Its value is a string. Used by 23 providers across 29 OpenAPI documents. Observed values include `float64`, `uuid.UUID`, `int64`, `net/netip.Addr` | 304 | 23 |
|
x-ms-client-request-id
vendor |
`x-ms-client-request-id` appears on parameter objects and on header objects. Its value is a boolean flag. Used by 2 providers across 16 OpenAPI documents. It sits in the `x-ms-` namespace, so its mean | 304 | 2 |
|
x-apidog-name
vendor |
`x-apidog-name` appears on response objects. Its value is a string. Used by 2 providers across 2 OpenAPI documents. It sits in the `x-apidog-` namespace, so its meaning is defined by apidog tooling ra | 303 | 2 |
| x-orum-error-invalid | `x-orum-error-invalid` appears on schema objects and properties and on parameter objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with validat | 302 | 1 |
|
x-veeam-spec
vendor |
`x-veeam-spec` appears on parameter objects. Its value is a structured object. Used by a single provider across 2 OpenAPI documents. It sits in the `x-veeam-` namespace, so its meaning is defined by v | 301 | 1 |
| x-go-type-skip-optional-pointer | `x-go-type-skip-optional-pointer` appears on schema objects and properties. Its value is a boolean flag. Used by 9 providers across 10 OpenAPI documents. Consistent with type system — this is inferred | 295 | 9 |
| x-position | `x-position` appears on parameter objects and on operations. Its value is an integer. Used by 3 providers across 11 OpenAPI documents. Observed values include `1`, `2`, `3`, `4`. Consistent with order | 295 | 3 |
|
x-speakeasy-entity
vendor |
`x-speakeasy-entity` appears on schema objects and properties. Its value is a string. Used by 4 providers across 5 OpenAPI documents. It sits in the `x-speakeasy-` namespace, so its meaning is defined | 288 | 4 |
| x-feature | `x-feature` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `TeamMessaging`, `ReadExtensions`, `SMSSending`, `EditUsers`. Con | 285 | 1 |
| x-max-interval-in-months | `x-max-interval-in-months` appears on schema objects and properties. Its value is an integer. Used by 3 providers across 11 OpenAPI documents. Observed values include `3`, `1`. Consistent with validat | 285 | 3 |
| x-path-item-properties | `x-path-item-properties` appears on operations. Its value is a structured object. Used by a single provider across 8 OpenAPI documents. Consistent with size & shape — this is inferred from where the k | 283 | 1 |
| x-stripeBypassValidation | `x-stripeBypassValidation` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 29 OpenAPI documents. Consistent with validation & constraints — this | 281 | 1 |
| x-shortName | `x-shortName` appears in the document. Its value is a string. Used by 40 providers across 40 OpenAPI documents. Observed values include `Products`, `Accounts`, `Account Balances`, `Transactions`. Cons | 280 | 40 |
| x-expandableFields | `x-expandableFields` appears on schema objects and properties and on response objects. Its value is a list. Used by a single provider across 47 OpenAPI documents. Consistent with identity & relationsh | 274 | 1 |
| x-custom-config | `x-custom-config` appears on operations. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from where th | 272 | 1 |
|
x-apideck-api
vendor |
`x-apideck-api` appears on operations. Its value is a string. Used by a single provider across 4 OpenAPI documents. It sits in the `x-apideck-` namespace, so its meaning is defined by apideck tooling | 255 | 1 |
| x-experimental | `x-experimental` appears on operations. Its value is a boolean flag. Used by 4 providers across 37 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the key appe | 244 | 4 |
| x-last-validated | `x-last-validated` appears in the info block. Its value is a string. Used by 134 providers across 242 OpenAPI documents. Observed values include `2026-04-18`, `2026-06-02`, `2026-05-30`, `2026-04-19`. | 242 | 134 |
|
x-veeam-authorize
vendor |
`x-veeam-authorize` appears on operations. Its value is a structured object. Used by a single provider across 2 OpenAPI documents. It sits in the `x-veeam-` namespace, so its meaning is defined by vee | 236 | 1 |
| x-node_available_in | `x-node_available_in` appears on schema objects and properties. Its value is a list. Used by a single provider across 21 OpenAPI documents. Consistent with data & schema semantics — this is inferred f | 235 | 1 |
| x-one-of | `x-one-of` appears on schema objects and properties. Its value is a string. Used by a single provider across 7 OpenAPI documents. Observed values include `config`, `ProjectIdentifier`, `principal`, `p | 222 | 1 |
|
x-ms-odata
vendor |
`x-ms-odata` appears on path items and on operations. Its value is a string. Used by 3 providers across 35 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is defined by ms tooling | 220 | 3 |
| x-audience | `x-audience` appears on operations. Its value is a string. Used by 19 providers across 44 OpenAPI documents. Observed values include `public`, `external-public`, `external-partner`, `external-merchant | 206 | 19 |
| x-gitbook-description-html | `x-gitbook-description-html` appears on schema objects and properties. Its value is a structured object. Used by 2 providers across 2 OpenAPI documents. Consistent with data & schema semantics — this | 204 | 2 |
| x-pushable | `x-pushable` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 4 OpenAPI documents. Consistent with data & schema semantics — this is inferred fro | 204 | 1 |
| x-typelizer | `x-typelizer` appears on schema objects and properties. Its value is a boolean flag. Used by 2 providers across 4 OpenAPI documents. Consistent with data & schema semantics — this is inferred from whe | 203 | 2 |
| x-field-extra-annotation | `x-field-extra-annotation` appears on schema objects and properties. Its value is a string. Used by 5 providers across 22 OpenAPI documents. Observed values include `@com.redis.om.spring.annotations.I | 202 | 5 |
| x-expansionResources | `x-expansionResources` appears on schema objects and properties. Its value is a structured object. Used by a single provider across 33 OpenAPI documents. Consistent with identity & relationships — thi | 198 | 1 |
|
x-apidog-folder
vendor |
`x-apidog-folder` appears on schema objects and properties and on operations. Its value is a string. Used by 2 providers across 2 OpenAPI documents. It sits in the `x-apidog-` namespace, so its meanin | 195 | 2 |
| x-required | `x-required` appears on schema objects and properties. Its value is a list. Used by a single provider across 10 OpenAPI documents. Consistent with validation & constraints — this is inferred from wher | 195 | 1 |
| x-allowableValues | `x-allowableValues` appears on parameter objects. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `Existing account token`, `Existing statement summ | 188 | 1 |
|
x-portone-status-code
vendor |
`x-portone-status-code` appears on schema objects and properties. Its value is an integer. Used by a single provider across 1 OpenAPI document. It sits in the `x-portone-` namespace, so its meaning is | 185 | 1 |
| x-request-id | `x-request-id` appears on header objects. Its value is a structured object. Used by 10 providers across 25 OpenAPI documents. Consistent with identity & relationships — this is inferred from where the | 183 | 10 |
| x-response-identifier | `x-response-identifier` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `id`, `name`, `ip`, `access`. Consistent with identit | 183 | 1 |
|
x-microcks-refs
vendor |
`x-microcks-refs` appears on response objects. Its value is a list. Used by a single provider across 1 OpenAPI document. It sits in the `x-microcks-` namespace, so its meaning is defined by microcks t | 182 | 1 |
| x-apiary-response-models | `x-apiary-response-models` appears on response objects. Its value is a list. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from where | 175 | 1 |
| x-filterable | `x-filterable` appears on schema objects and properties and on operations. Its value is a list. Used by 2 providers across 5 OpenAPI documents. Consistent with data & schema semantics — this is inferr | 174 | 2 |
|
x-ms-version
vendor |
`x-ms-version` appears on header objects. Its value is a structured object. Used by a single provider across 5 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is defined by ms tool | 170 | 1 |
| x-auditable | `x-auditable` appears on schema objects and properties. Its value is a boolean flag. Used by 4 providers across 4 OpenAPI documents. Consistent with data & schema semantics — this is inferred from whe | 167 | 4 |
| x-pattern-message | `x-pattern-message` appears on schema objects and properties. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `should be 'Logs' or 'Metrics' or 'Slo | 166 | 1 |
| x-source | `x-source` appears in the info block. Its value is a string. Used by 100 providers across 148 OpenAPI documents. Observed values include `https://tidal-music.github.io/tidal-api-reference/tidal-api-oa | 161 | 100 |
|
x-fds-dh
vendor |
`x-fds-dh` appears on schema objects and properties. Its value is a string. Used by a single provider across 2 OpenAPI documents. It sits in the `x-fds-` namespace, so its meaning is defined by fds to | 160 | 1 |
|
x-apideck-enum-id
vendor |
`x-apideck-enum-id` appears on schema objects and properties. Its value is a string. Used by a single provider across 4 OpenAPI documents. It sits in the `x-apideck-` namespace, so its meaning is defi | 159 | 1 |
|
x-merge-override
vendor |
`x-merge-override` appears on schema objects and properties. Its value is a structured object. Used by a single provider across 1 OpenAPI document. It sits in the `x-merge-` namespace, so its meaning | 159 | 1 |
|
x-ms-parameterized-host
vendor |
`x-ms-parameterized-host` appears at the root of the document. Its value is a structured object. Used by 2 providers across 159 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is d | 159 | 2 |
| x-node_unavailable_in | `x-node_unavailable_in` appears on schema objects and properties. It is used as a marker with no value. Used by a single provider across 13 OpenAPI documents. Consistent with data & schema semantics — | 158 | 1 |
| x-pattern | `x-pattern` appears on operations and on schema objects and properties. Its value is a string. Used by 4 providers across 4 OpenAPI documents. Observed values include `[\\u0020-\\uD7FF\\uE000-\\uFFFD\ | 157 | 4 |
| x-references | `x-references` appears on path items. Its value is a structured object. Used by 2 providers across 4 OpenAPI documents. Consistent with identity & relationships — this is inferred from where the key a | 156 | 2 |
|
x-toast-read-only
vendor |
`x-toast-read-only` appears on schema objects and properties. Its value is a boolean flag. Used by 2 providers across 2 OpenAPI documents. It sits in the `x-toast-` namespace, so its meaning is define | 156 | 2 |
| x-discriminator | `x-discriminator` appears on schema objects and properties. Its value is a string. Used by 2 providers across 4 OpenAPI documents. Observed values include `type`, `actionType`, `cloudCredentialsType`, | 155 | 2 |
|
x-apideck-weights
vendor |
`x-apideck-weights` appears on schema objects and properties. Its value is a structured object. Used by a single provider across 4 OpenAPI documents. It sits in the `x-apideck-` namespace, so its mean | 153 | 1 |
|
x-box-sanitized
vendor |
`x-box-sanitized` appears on operations. Its value is a boolean flag. Used by a single provider across 11 OpenAPI documents. It sits in the `x-box-` namespace, so its meaning is defined by box tooling | 151 | 1 |
| x-derived | `x-derived` appears on schema objects and properties. Its value is a structured object. Used by 4 providers across 6 OpenAPI documents. Consistent with mutability & access — this is inferred from wher | 150 | 4 |
|
x-fds-sdf
vendor |
`x-fds-sdf` appears on schema objects and properties. Its value is a string. Used by a single provider across 2 OpenAPI documents. It sits in the `x-fds-` namespace, so its meaning is defined by fds t | 150 | 1 |
| x-providerName | `x-providerName` appears in the info block. Its value is a string. Used by 120 providers across 148 OpenAPI documents. Observed values include `amazonaws.com`, `azure.com`, `googleapis.com`, `Qlik`. C | 150 | 120 |
| x-state | `x-state` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `Generally available; added in 9.4.0`, `Technical Preview; added in | 150 | 1 |
| x-orum-error-missing | `x-orum-error-missing` appears on schema objects and properties and on parameter objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with data & | 148 | 1 |
| x-extensible-enum | `x-extensible-enum` appears on schema objects and properties. Its value is a list. Used by 13 providers across 21 OpenAPI documents. Consistent with type system — this is inferred from where the key a | 147 | 13 |
|
x-portone-error
vendor |
`x-portone-error` appears on operations. Its value is a structured object. Used by a single provider across 1 OpenAPI document. It sits in the `x-portone-` namespace, so its meaning is defined by port | 147 | 1 |
| x-serviceName | `x-serviceName` appears in the info block. Its value is a string. Used by 116 providers across 144 OpenAPI documents. Observed values include `iot`, `appmesh`, `cognito-identity`, `cognito-idp`. Consi | 145 | 116 |
|
x-speakeasy-ignore
vendor |
`x-speakeasy-ignore` appears on operations and on parameter objects. Its value is a boolean flag. Used by 9 providers across 12 OpenAPI documents. It sits in the `x-speakeasy-` namespace, so its meani | 145 | 9 |
| x-resourceId | `x-resourceId` appears on schema objects and properties. Its value is a string. Used by a single provider across 47 OpenAPI documents. Observed values include `refund`, `payment_method`, `apple_pay_do | 143 | 1 |
|
x-speakeasy-component
vendor |
`x-speakeasy-component` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. It sits in the `x-speakeasy-` namespace, so its mean | 143 | 1 |
|
x-amz-apigw-id
vendor |
`x-amz-apigw-id` appears on header objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. It sits in the `x-amz-` namespace, so its meaning is defined by amz t | 142 | 1 |
| x-amzn-RequestId | `x-amzn-RequestId` appears on header objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from whe | 142 | 1 |
| x-excluded | `x-excluded` appears on operations. Its value is a boolean flag. Used by 8 providers across 9 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the key appears a | 142 | 8 |
| x-expanded-response | `x-expanded-response` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `CloudProjectDatabaseServiceIntegration`, `CloudProject | 138 | 1 |
| x-js-format | `x-js-format` appears on schema objects and properties. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `bigint`. Consistent with type system — this | 137 | 1 |
| x-anchors | `x-anchors` appears at the root of the document. Its value is a structured object. Used by a single provider across 135 OpenAPI documents. Consistent with data & schema semantics — this is inferred fr | 136 | 1 |
| x-content-type | `x-content-type` appears on operations. Its value is a string. Used by 6 providers across 9 OpenAPI documents. Observed values include `application/json`, `application/octet-stream`, `application/x-ww | 136 | 6 |
| x-headers | `x-headers` appears in the document. Its value is a structured object. Used by a single provider across 135 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the | 135 | 1 |
| x-modeled | `x-modeled` appears on operations. Its value is a boolean flag. Used by 23 providers across 23 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the key appears | 134 | 23 |
| x-rbac-enabled | `x-rbac-enabled` appears on operations. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from where the key | 134 | 1 |
| x-execution-weight | `x-execution-weight` appears on operations. Its value is a string. Used by a single provider across 2 OpenAPI documents. Observed values include `medium`, `small`, `free`, `xl`. Consistent with orderi | 132 | 1 |
|
x-apideck-gotchas
vendor |
`x-apideck-gotchas` appears on operations. Its value is a list. Used by a single provider across 4 OpenAPI documents. It sits in the `x-apideck-` namespace, so its meaning is defined by apideck toolin | 129 | 1 |
| x-abstractType | `x-abstractType` appears on schema objects and properties. Its value is a structured object. Used by a single provider across 3 OpenAPI documents. Consistent with data & schema semantics — this is inf | 128 | 1 |
| x-cas-attribute | `x-cas-attribute` appears on schema objects and properties. Its value is a string. Used by a single provider across 2 OpenAPI documents. Observed values include `timeLatestTradePrice`, `valueLatestTra | 128 | 1 |
| x-hasPayrollUkProblem | `x-hasPayrollUkProblem` appears on operations. Its value is a boolean flag. Used by a single provider across 2 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where | 128 | 1 |
| x-rbac-allowed-groups | `x-rbac-allowed-groups` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `admin`, `admin,member`, `admin,saml-admin`, `admin,m | 127 | 1 |
| x-custom-attributes | `x-custom-attributes` appears on operations. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from wher | 126 | 1 |
| x-twitter | `x-twitter` appears in the info block. Its value is a string. Used by 107 providers across 125 OpenAPI documents. Observed values include `PermittedSoc`, `youtube`, `MercedesBenz`, `TomTom`. Consisten | 125 | 107 |
|
x-apifox
vendor |
`x-apifox` appears on schema objects and properties and on parameter objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. It sits in the `x-apifox-` namespac | 123 | 1 |
| x-correlation-id | `x-correlation-id` appears on header objects. Its value is a structured object. Used by 2 providers across 3 OpenAPI documents. Consistent with identity & relationships — this is inferred from where t | 123 | 2 |
| x-format | `x-format` appears on schema objects and properties. Its value is a string. Used by 2 providers across 2 OpenAPI documents. Observed values include `int64`, `address`, `decimal`, `+E.164`. Consistent | 123 | 2 |
|
x-atlassian-narrative
vendor |
`x-atlassian-narrative` appears at the root of the document. Its value is a structured object. Used by a single provider across 122 OpenAPI documents. It sits in the `x-atlassian-` namespace, so its m | 122 | 1 |
| x-preferred | `x-preferred` appears in the info block. Its value is a boolean flag. Used by 108 providers across 121 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the key | 122 | 108 |
| x-resources | `x-resources` appears on operations. Its value is a list. Used by a single provider across 1 OpenAPI document. Consistent with identity & relationships — this is inferred from where the key appears an | 119 | 1 |
|
x-portone-enum
vendor |
`x-portone-enum` appears on schema objects and properties. Its value is a structured object. Used by a single provider across 1 OpenAPI document. It sits in the `x-portone-` namespace, so its meaning | 118 | 1 |
| x-ratelimit-tier | `x-ratelimit-tier` appears on operations. Its value is an integer. Used by a single provider across 12 OpenAPI documents. Observed values include `3`, `2`, `4`, `1`. Consistent with data & schema sema | 116 | 1 |
| x-apiClientRegistration | `x-apiClientRegistration` appears in the info block. Its value is a structured object. Used by 103 providers across 114 OpenAPI documents. Consistent with data & schema semantics — this is inferred fr | 115 | 103 |
| x-additionalPropertiesName | `x-additionalPropertiesName` appears on schema objects and properties. Its value is a string. Used by 12 providers across 12 OpenAPI documents. Observed values include `locationId`, `fieldApiName`, `s | 114 | 12 |
| x-authorization-privileges | `x-authorization-privileges` appears on operations. Its value is a list. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from where the | 114 | 1 |
| x-rate-limit | `x-rate-limit` appears on operations. Its value is a string. Used by 2 providers across 2 OpenAPI documents. Observed values include `This interface is limited to 10 seconds/call;`, `This interface is | 114 | 2 |
| x-og-claims-required | `x-og-claims-required` appears on operations. Its value is a list. Used by a single provider across 1 OpenAPI document. Consistent with validation & constraints — this is inferred from where the key a | 113 | 1 |
| x-plan-products | `x-plan-products` appears on operations. Its value is a list. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from where the key appears | 113 | 1 |
| x-appdirect-api-stage | `x-appdirect-api-stage` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `Early Access`, `Deprecated`. Consistent with data & | 111 | 1 |
| x-stability-level | `x-stability-level` appears on schema objects and properties and on operations. Its value is a string. Used by 2 providers across 2 OpenAPI documents. Observed values include `beta`, `alpha`. Consiste | 109 | 2 |
|
x-yba-api-audit
vendor |
`x-yba-api-audit` appears on operations. Its value is a structured object. Used by a single provider across 2 OpenAPI documents. It sits in the `x-yba-` namespace, so its meaning is defined by yba too | 108 | 1 |
|
x-apisguru-driver
vendor |
`x-apisguru-driver` appears in the info block. Its value is a string. Used by 98 providers across 106 OpenAPI documents. It sits in the `x-apisguru-` namespace, so its meaning is defined by apisguru t | 106 | 98 |
| x-atMostOne | `x-atMostOne` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 8 OpenAPI documents. Consistent with data & schema semantics — this is inferred fr | 105 | 1 |
| x-createOnly | `x-createOnly` appears on schema objects and properties. Its value is a list. Used by a single provider across 3 OpenAPI documents. Consistent with data & schema semantics — this is inferred from wher | 101 | 1 |
| x-recommended-call-frequency | `x-recommended-call-frequency` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `1 day/call`, `15 seconds/call`, `1 minute/cal | 101 | 1 |
|
x-ms-external
vendor |
`x-ms-external` appears on schema objects and properties. Its value is a boolean flag. Used by 4 providers across 52 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is defined by m | 100 | 4 |
|
x-xgen-method-verb-override
vendor |
`x-xgen-method-verb-override` appears on operations. Its value is a structured object. Used by a single provider across 1 OpenAPI document. It sits in the `x-xgen-` namespace, so its meaning is define | 100 | 1 |
| x-audit-log | `x-audit-log` appears on operations. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from where the ke | 99 | 1 |
| x-data-access | `x-data-access` appears on operations. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from where the | 99 | 1 |
| x-hasAccountingValidationError | `x-hasAccountingValidationError` appears on operations. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with validation & constraints — this is inferred fr | 99 | 1 |
| x-security | `x-security` appears on operations. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from where the key | 98 | 1 |
| x-hasEquivalentPaths | `x-hasEquivalentPaths` appears at the root of the document. Its value is a boolean flag. Used by 89 providers across 97 OpenAPI documents. Consistent with data & schema semantics — this is inferred fr | 97 | 89 |
|
x-fern-type-name
vendor |
`x-fern-type-name` appears on schema objects and properties and on request bodies. Its value is a string. Used by 3 providers across 16 OpenAPI documents. It sits in the `x-fern-` namespace, so its me | 96 | 3 |
| x-apply-to | `x-apply-to` appears on operations. Its value is a list. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from where the key appears and | 95 | 1 |
|
x-obmcs-mysql-isDynamic
vendor |
`x-obmcs-mysql-isDynamic` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. It sits in the `x-obmcs-` namespace, so its meanin | 94 | 1 |
| x-operation-request-parameters-name | `x-operation-request-parameters-name` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `ListActionsRequestParameters`, `ListAc | 94 | 1 |
| x-cadl-name | `x-cadl-name` appears on schema objects and properties. Its value is a string. Used by a single provider across 5 OpenAPI documents. Observed values include `string[]`, `Rest.ResourceLocation`, `Recor | 93 | 1 |
|
x-speakeasy-alias
vendor |
`x-speakeasy-alias` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. It sits in the `x-speakeasy-` namespace, so its meaning is defined by speakeasy t | 91 | 1 |
|
x-box-variant
vendor |
`x-box-variant` appears on schema objects and properties. Its value is a string. Used by a single provider across 21 OpenAPI documents. It sits in the `x-box-` namespace, so its meaning is defined by | 90 | 1 |
| x-ratelimit-limit | `x-ratelimit-limit` appears on header objects. Its value is a structured object. Used by 10 providers across 12 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where | 90 | 10 |
| x-traitTag | `x-traitTag` appears on tags. Its value is a boolean flag. Used by 12 providers across 14 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the key appears and w | 89 | 12 |
| x-operationVersions | `x-operationVersions` appears on operations. Its value is a list. Used by a single provider across 13 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the key a | 87 | 1 |
|
x-fern-audiences
vendor |
`x-fern-audiences` appears on operations and in components. Its value is a list. Used by 2 providers across 2 OpenAPI documents. It sits in the `x-fern-` namespace, so its meaning is defined by fern t | 85 | 2 |
| x-oaiExpandable | `x-oaiExpandable` appears on schema objects and properties. Its value is a boolean flag. Used by 3 providers across 5 OpenAPI documents. Consistent with identity & relationships — this is inferred fro | 85 | 3 |
| x-readOnly | `x-readOnly` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 3 OpenAPI documents. Consistent with mutability & access — this is inferred from wh | 84 | 1 |
| x-anonymous-access | `x-anonymous-access` appears on operations. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from where the | 83 | 1 |
| x-resource-id | `x-resource-id` appears on schema objects and properties. Its value is a string. Used by 2 providers across 3 OpenAPI documents. Observed values include `BuyerTaxonomyNodes`, `BuyerTaxonomyNode`, `Err | 83 | 2 |
|
x-speakeasy-match
vendor |
`x-speakeasy-match` appears on parameter objects. Its value is a string. Used by 2 providers across 3 OpenAPI documents. It sits in the `x-speakeasy-` namespace, so its meaning is defined by speakeasy | 82 | 2 |
| x-insert-after | `x-insert-after` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred | 81 | 1 |
|
x-apidog-status
vendor |
`x-apidog-status` appears on operations. Its value is a string. Used by 2 providers across 2 OpenAPI documents. It sits in the `x-apidog-` namespace, so its meaning is defined by apidog tooling rather | 80 | 2 |
| x-run-in-apidog | `x-run-in-apidog` appears on operations. Its value is a string. Used by 2 providers across 2 OpenAPI documents. Observed values include `https://app.apidog.com/web/project/1056134/apis/api-20919916-ru | 80 | 2 |
| x-status | `x-status` appears in the info block and on operations. Its value is a string. Used by 26 providers across 56 OpenAPI documents. Observed values include `validated`, `modeled`, `deprecated`, `confirme | 79 | 26 |
| x-validation | `x-validation` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with validation & constraints — this is inferred f | 79 | 1 |
| x-criticality | `x-criticality` appears on operations. Its value is a string. Used by a single provider across 2 OpenAPI documents. Observed values include `high`, `medium`. Consistent with data & schema semantics — | 78 | 1 |
| x-oneOf | `x-oneOf` appears on schema objects and properties. Its value is a list. Used by 2 providers across 2 OpenAPI documents. Consistent with type system — this is inferred from where the key appears and w | 77 | 2 |
| x-ratelimit-reset | `x-ratelimit-reset` appears on header objects. Its value is a structured object. Used by 8 providers across 10 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where | 77 | 8 |
|
x-apidog
vendor |
`x-apidog` appears on operations. Its value is a structured object. Used by 2 providers across 2 OpenAPI documents. It sits in the `x-apidog-` namespace, so its meaning is defined by apidog tooling ra | 76 | 2 |
| x-foreign | `x-foreign` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 2 OpenAPI documents. Consistent with identity & relationships — this is inferred fro | 74 | 1 |
| x-is-jackson-optional-nullable | `x-is-jackson-optional-nullable` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with type system — this is infer | 74 | 1 |
|
x-fern-server-name
vendor |
`x-fern-server-name` appears on server objects and in the document. Its value is a string. Used by 4 providers across 30 OpenAPI documents. It sits in the `x-fern-` namespace, so its meaning is define | 72 | 4 |
|
x-stainless-skip
vendor |
`x-stainless-skip` appears on schema objects and properties. Its value is a boolean flag. Used by 7 providers across 7 OpenAPI documents. It sits in the `x-stainless-` namespace, so its meaning is def | 72 | 7 |
| x-default-client | `x-default-client` appears at the root of the document. Its value is a string. Used by 2 providers across 71 OpenAPI documents. Observed values include `cURL`. Consistent with defaults & examples — th | 71 | 2 |
| x-given | `x-given` appears on operations. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from where the key ap | 71 | 1 |
| x-targetService | `x-targetService` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `metadata`, `metadata-service`, `connectivity`. Consistent | 71 | 1 |
|
x-konfig-null-placeholder
vendor |
`x-konfig-null-placeholder` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. It sits in the `x-konfig-` namespace, so its mea | 70 | 1 |
| x-apievangelist-source | `x-apievangelist-source` appears in the info block. Its value is a string. Used by 48 providers across 69 OpenAPI documents. Observed values include `https://perfectday.com/wp-json/wp/v2`, `https://de | 69 | 48 |
| x-verbose-required | `x-verbose-required` appears on schema objects and properties. It is used as a marker with no value. Used by a single provider across 1 OpenAPI document. Consistent with validation & constraints — thi | 69 | 1 |
| x-allowExtraHeaders | `x-allowExtraHeaders` appears on operations. Its value is a boolean flag. Used by 3 providers across 3 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the key | 68 | 3 |
| x-api-evangelist-certified | `x-api-evangelist-certified` appears on operations. Its value is a string. Used by 2 providers across 15 OpenAPI documents. Observed values include `2025-07-16`, `2025-07-20`, `2025-07-18`. Consistent | 68 | 2 |
| x-arrayCheckCount | `x-arrayCheckCount` appears on operations. Its value is a boolean flag. Used by 3 providers across 3 OpenAPI documents. Consistent with size & shape — this is inferred from where the key appears and w | 68 | 3 |
| x-bodyMatchMode | `x-bodyMatchMode` appears on operations. Its value is a string. Used by 3 providers across 3 OpenAPI documents. Observed values include `NONE`, `RAW`. Consistent with data & schema semantics — this is | 68 | 3 |
| x-matchResponseSchema | `x-matchResponseSchema` appears on operations. Its value is a boolean flag. Used by 3 providers across 3 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the ke | 68 | 3 |
| x-api-key | `x-api-key` appears on parameter objects and on security schemes. Its value is a structured object. Used by 12 providers across 63 OpenAPI documents. Consistent with identity & relationships — this is | 67 | 12 |
|
x-aws-signingName
vendor |
`x-aws-signingName` appears in the info block. Its value is a string. Used by 65 providers across 66 OpenAPI documents. It sits in the `x-aws-` namespace, so its meaning is defined by aws tooling rath | 66 | 65 |
| x-is-date | `x-is-date` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 2 OpenAPI documents. Consistent with type system — this is inferred from where the k | 66 | 1 |
|
x-okta-parent
vendor |
`x-okta-parent` appears on schema objects and properties. Its value is a string. Used by a single provider across 1 OpenAPI document. It sits in the `x-okta-` namespace, so its meaning is defined by o | 66 | 1 |
| x-quoted | `x-quoted` appears on parameter objects. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from where the key | 66 | 1 |
|
x-speakeasy-param-suppress-computed-diff
vendor |
`x-speakeasy-param-suppress-computed-diff` appears on schema objects and properties. Its value is a boolean flag. Used by 2 providers across 3 OpenAPI documents. It sits in the `x-speakeasy-` namespac | 66 | 2 |
|
x-ms-arm-id-details
vendor |
`x-ms-arm-id-details` appears on schema objects and properties. Its value is a structured object. Used by a single provider across 19 OpenAPI documents. It sits in the `x-ms-` namespace, so its meanin | 65 | 1 |
| x-apievangelist-generated | `x-apievangelist-generated` appears in the info block. Its value is a string. Used by 45 providers across 64 OpenAPI documents. Observed values include `true`, `2026-08-02`, `2026-07-19`, `2026-07-18` | 64 | 45 |
| x-apievangelist-method | `x-apievangelist-method` appears in the info block. Its value is a string. Used by 41 providers across 62 OpenAPI documents. Observed values include `generated`, `derived`, `searched`. Consistent with | 62 | 41 |
|
x-apifox-enum
vendor |
`x-apifox-enum` appears on schema objects and properties and on parameter objects. Its value is a list. Used by a single provider across 1 OpenAPI document. It sits in the `x-apifox-` namespace, so it | 62 | 1 |
|
x-ms-code-generation-settings
vendor |
`x-ms-code-generation-settings` appears in the info block. Its value is a structured object. Used by 2 providers across 62 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is define | 62 | 2 |
|
x-ms-enum-flags
vendor |
`x-ms-enum-flags` appears on schema objects and properties. Its value is a structured object. Used by a single provider across 8 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is | 62 | 1 |
| x-generated | `x-generated` appears in the info block. Its value is a string. Used by 45 providers across 58 OpenAPI documents. Observed values include `2026-07-19`, `2026-07-21`, `2026-07-20`, `2026-08-19`. Consis | 61 | 45 |
| x-operator | `x-operator` appears in the info block and at the root of the document. Its value is a string. Used by 29 providers across 60 OpenAPI documents. Observed values include `institution`, `tenant`. Consis | 60 | 29 |
| x-original-swagger-version | `x-original-swagger-version` appears at the root of the document. Its value is a string. Used by 40 providers across 60 OpenAPI documents. Observed values include `2.0`. Consistent with naming & alias | 60 | 40 |
| x-sample-urls | `x-sample-urls` appears on operations. Its value is a list. Used by a single provider across 1 OpenAPI document. Consistent with defaults & examples — this is inferred from where the key appears and w | 60 | 1 |
| x-typespec-generated | `x-typespec-generated` appears in the info block. Its value is a list. Used by a single provider across 60 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the | 60 | 1 |
| x-schema-source | `x-schema-source` appears on schema objects and properties. Its value is a string. Used by 12 providers across 17 OpenAPI documents. Observed values include `documentation`, `sdk`. Consistent with dat | 59 | 12 |
| x-api-version | `x-api-version` appears on operations and at the root of the document. Its value is a string. Used by 7 providers across 23 OpenAPI documents. Observed values include `1`, `4.4.0`, `4.0.2`, `2025-01-0 | 58 | 7 |
| x-endpoint-errors | `x-endpoint-errors` appears on operations. Its value is a list. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from where the key appea | 58 | 1 |
| x-wp-pattern | `x-wp-pattern` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `[\d]+`, `[\w-]+`. Consistent with validation & constraints — | 58 | 1 |
|
x-apideck-model
vendor |
`x-apideck-model` appears on tags. Its value is a structured object. Used by a single provider across 4 OpenAPI documents. It sits in the `x-apideck-` namespace, so its meaning is defined by apideck t | 57 | 1 |
|
x-apideck-resource-id
vendor |
`x-apideck-resource-id` appears on tags. Its value is a string. Used by a single provider across 4 OpenAPI documents. It sits in the `x-apideck-` namespace, so its meaning is defined by apideck toolin | 57 | 1 |
| x-200 | `x-200` appears on response objects. Its value is a string. Used by 3 providers across 3 OpenAPI documents. Observed values include `请求成功:`, `Create - Cash Transaction:`, `Create - Account credit Tran | 56 | 3 |
|
x-ms-correlation-request-id
vendor |
`x-ms-correlation-request-id` appears on header objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. It sits in the `x-ms-` namespace, so its meaning is defi | 56 | 1 |
| x-camara-commonalities | `x-camara-commonalities` appears in the info block. Its value is a string. Used by 4 providers across 54 OpenAPI documents. Observed values include `0.4.0`, `0.6`, `0.5`, `tbd`. Consistent with data & | 54 | 4 |
| x-dct-toolkit-subcommand | `x-dct-toolkit-subcommand` appears on schema objects and properties. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `oracle`, `mssql`, `appdata`, ` | 53 | 1 |
|
x-konfig-is-parameter
vendor |
`x-konfig-is-parameter` appears on schema objects and properties. Its value is a list. Used by a single provider across 1 OpenAPI document. It sits in the `x-konfig-` namespace, so its meaning is defi | 53 | 1 |
|
x-konfig-single-parameter-schema
vendor |
`x-konfig-single-parameter-schema` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. It sits in the `x-konfig-` namespace, so its meaning is defined by | 53 | 1 |
| x-method | `x-method` appears in the info block. Its value is a string. Used by 43 providers across 52 OpenAPI documents. Observed values include `generated`, `derived`, `probed`, `searched`. Consistent with dat | 52 | 43 |
| x-panMemberOf | `x-panMemberOf` appears on schema objects and properties. Its value is a list. Used by a single provider across 14 OpenAPI documents. Consistent with data & schema semantics — this is inferred from wh | 52 | 1 |
| x-solana-method | `x-solana-method` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `getAccountInfo`, `getBalance`, `getLargestAccounts`, `getM | 52 | 1 |
| x-deletion-date | `x-deletion-date` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `2023-03-15T00:00:00Z`, `2023-10-13T00:00:00Z`, `2020-10-01 | 51 | 1 |
| x-discriminator-value | `x-discriminator-value` appears on operations and on request bodies. Its value is a string. Used by 2 providers across 2 OpenAPI documents. Observed values include `RFQ`, `DCA`, `TWAP`, `GRID`. Consis | 51 | 2 |
| x-size-message | `x-size-message` appears on schema objects and properties. Its value is a string. Used by 2 providers across 7 OpenAPI documents. Observed values include `cannot be empty`, `Title is required`. Consis | 51 | 2 |
| x-endpointsModeled | `x-endpointsModeled` appears on operations. Its value is a boolean flag. Used by 15 providers across 16 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the key | 50 | 15 |
| x-objectArrayKey | `x-objectArrayKey` appears on schema objects and properties. Its value is a string. Used by a single provider across 2 OpenAPI documents. Observed values include `cis_settings`, `employees`, `accounts | 50 | 1 |
| x-request-max-body-size | `x-request-max-body-size` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `100m`, `1m`, `10m`, `20m`. Consistent with validat | 50 | 1 |
| x-returns-list | `x-returns-list` appears on operations. Its value is a boolean flag. Used by 2 providers across 2 OpenAPI documents. Consistent with size & shape — this is inferred from where the key appears and what | 50 | 2 |
| x-RateLimit-Limit | `x-RateLimit-Limit` appears on header objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from wh | 49 | 1 |
| x-RateLimit-Remaining | `x-RateLimit-Remaining` appears on header objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred fro | 49 | 1 |
| x-RateLimit-Reset | `x-RateLimit-Reset` appears on header objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from wh | 49 | 1 |
| x-chainweb-node-version | `x-chainweb-node-version` appears on header objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred f | 49 | 1 |
| x-concurrent-limit-ttl-ms | `x-concurrent-limit-ttl-ms` appears on path items. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `1800000`, `17" # p90 duration, ClickHouse mddsv | 49 | 1 |
| x-peer-addr | `x-peer-addr` appears on header objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from where th | 49 | 1 |
| x-server-timestamp | `x-server-timestamp` appears on header objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with units & formatting — this is inferred from where | 49 | 1 |
| x-beta | `x-beta` appears on operations. Its value is a boolean flag. Used by 6 providers across 8 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the key appears and w | 48 | 6 |
| x-coproduct | `x-coproduct` appears on schema objects and properties. Its value is a boolean flag. Used by 3 providers across 11 OpenAPI documents. Consistent with data & schema semantics — this is inferred from wh | 48 | 3 |
| x-is-msdate | `x-is-msdate` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 2 OpenAPI documents. Consistent with data & schema semantics — this is inferred fr | 48 | 1 |
| x-multi-segment | `x-multi-segment` appears on parameter objects and on operations. Its value is a boolean flag. Used by 2 providers across 7 OpenAPI documents. Consistent with data & schema semantics — this is inferre | 48 | 2 |
| x-stripeSpecFilename | `x-stripeSpecFilename` appears in the info block. Its value is a string. Used by a single provider across 48 OpenAPI documents. Observed values include `spec3`. Consistent with naming & aliasing — thi | 48 | 1 |
| x-weight | `x-weight` appears in the document. Its value is an integer. Used by a single provider across 1 OpenAPI document. Observed values include `820`, `420`, `170`, `210`. Consistent with ordering & sorting | 48 | 1 |
| x-api-id | `x-api-id` appears in the info block. Its value is a string. Used by 33 providers across 47 OpenAPI documents. Observed values include `solar-edge:solar-edge-monitoring-api`, `acuant:acas`, `acuant:as | 47 | 33 |
| x-class-extra-annotation | `x-class-extra-annotation` appears on schema objects and properties. Its value is a string. Used by 6 providers across 16 OpenAPI documents. Observed values include `@com.fasterxml.jackson.annotation. | 47 | 6 |
| x-rate-limit-remaining | `x-rate-limit-remaining` appears on header objects. Its value is a structured object. Used by 5 providers across 17 OpenAPI documents. Consistent with data & schema semantics — this is inferred from w | 47 | 5 |
| x-rate-limit-limit | `x-rate-limit-limit` appears on header objects. Its value is a structured object. Used by 4 providers across 16 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where | 46 | 4 |
| x-rate-limit-reset | `x-rate-limit-reset` appears on header objects. Its value is a structured object. Used by 4 providers across 16 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where | 46 | 4 |
| x-env-variable | `x-env-variable` appears on parameter objects. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `true`, `project`, `workspace`, `portfolio`. Consiste | 45 | 1 |
| x-groupName | `x-groupName` appears on operations. Its value is a string. Used by a single provider across 8 OpenAPI documents. Observed values include `General`, `Account holders`, `Verification`, `Accounts`. Cons | 45 | 1 |
| x-is-limit-param | `x-is-limit-param` appears on parameter objects. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from where | 45 | 1 |
|
x-spotify-policy-list
vendor |
`x-spotify-policy-list` appears on operations. Its value is a structured object. Used by a single provider across 1 OpenAPI document. It sits in the `x-spotify-` namespace, so its meaning is defined b | 45 | 1 |
| x-sendgrid | `x-sendgrid` appears in the info block. Its value is a structured object. Used by a single provider across 44 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where t | 44 | 1 |
| x-up42-endpoint-status | `x-up42-endpoint-status` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `modeled`, `confirmed`. Consistent with data & schem | 42 | 1 |
| x-convertToRelative | `x-convertToRelative` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 2 OpenAPI documents. Consistent with data & schema semantics — this is inf | 41 | 1 |
| x-exclude-from-lint | `x-exclude-from-lint` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is infe | 41 | 1 |
|
x-speakeasy-error-message
vendor |
`x-speakeasy-error-message` appears on schema objects and properties. Its value is a boolean flag. Used by 2 providers across 5 OpenAPI documents. It sits in the `x-speakeasy-` namespace, so its meani | 41 | 2 |
| x-contentType | `x-contentType` appears on operations. Its value is a string. Used by 2 providers across 2 OpenAPI documents. Observed values include `application/json`. Consistent with data & schema semantics — this | 40 | 2 |
| x-is-msdate-time | `x-is-msdate-time` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 2 OpenAPI documents. Consistent with units & formatting — this is inferred fr | 40 | 1 |
| x-panMultiple | `x-panMultiple` appears on schema objects and properties. Its value is a list. Used by a single provider across 8 OpenAPI documents. Consistent with data & schema semantics — this is inferred from whe | 40 | 1 |
| x-ratelimit-remaining | `x-ratelimit-remaining` appears on header objects. Its value is a structured object. Used by 10 providers across 10 OpenAPI documents. Consistent with data & schema semantics — this is inferred from w | 40 | 10 |
| x-riot-team-ownership | `x-riot-team-ownership` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `platform`, `simulation`, `inbox`, `awareness`. Consi | 40 | 1 |
| x-enum | `x-enum` appears on schema objects and properties. Its value is a list. Used by 2 providers across 8 OpenAPI documents. Consistent with type system — this is inferred from where the key appears and wh | 39 | 2 |
| x-eov-operation-handler | `x-eov-operation-handler` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `organization/businessEntities`, `organization/emis | 39 | 1 |
|
x-speakeasy-terraform-ignore
vendor |
`x-speakeasy-terraform-ignore` appears on schema objects and properties. Its value is a boolean flag. Used by 2 providers across 3 OpenAPI documents. It sits in the `x-speakeasy-` namespace, so its me | 39 | 2 |
| x-tier | `x-tier` appears on operations. Its value is an integer. Used by a single provider across 1 OpenAPI document. Observed values include `2`, `1`, `3`. Consistent with data & schema semantics — this is i | 39 | 1 |
| x-concreteTypes | `x-concreteTypes` appears on schema objects and properties. Its value is a list. Used by a single provider across 3 OpenAPI documents. Consistent with data & schema semantics — this is inferred from w | 38 | 1 |
| x-name | `x-name` appears on request bodies and on operations. Its value is a string. Used by 3 providers across 9 OpenAPI documents. Observed values include `request`, `requestBody`, `body`, `filter`. Consist | 38 | 3 |
| x-stability | `x-stability` appears on schema objects and properties. Its value is a string. Used by a single provider across 2 OpenAPI documents. Observed values include `beta`. Consistent with data & schema seman | 38 | 1 |
| x-codename | `x-codename` appears in the document. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `ais_position`, `ais_static`, `distancetoport`, `fleet`. Consi | 37 | 1 |
| x-apim-inline | `x-apim-inline` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 6 OpenAPI documents. Consistent with data & schema semantics — this is inferred | 36 | 1 |
|
x-box-variants
vendor |
`x-box-variants` appears on schema objects and properties. Its value is a list. Used by a single provider across 6 OpenAPI documents. It sits in the `x-box-` namespace, so its meaning is defined by bo | 36 | 1 |
| x-description-3 | `x-description-3` appears on response objects. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `Organizations are only available to first party clie | 36 | 1 |
| x-minimum | `x-minimum` appears on schema objects and properties. Its value is an integer. Used by 3 providers across 7 OpenAPI documents. Observed values include `0`, `1000`, `1`, `300000`. Consistent with data | 36 | 3 |
| x-application-context | `x-application-context` appears on header objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred fro | 35 | 1 |
| x-generatedAt | `x-generatedAt` appears at the root of the document. Its value is a string. Used by 4 providers across 35 OpenAPI documents. Observed values include `2021-04-19T12:58:58.637Z`, `2023-02-01T13:10:18.02 | 35 | 4 |
|
x-obmcs-get-work-request-operation
vendor |
`x-obmcs-get-work-request-operation` appears on operations. Its value is a string. Used by a single provider across 5 OpenAPI documents. It sits in the `x-obmcs-` namespace, so its meaning is defined | 35 | 1 |
|
x-amz-target
vendor |
`x-amz-target` appears on operations. Its value is a string. Used by 4 providers across 4 OpenAPI documents. It sits in the `x-amz-` namespace, so its meaning is defined by amz tooling rather than by | 33 | 4 |
| x-is-map | `x-is-map` appears on parameter objects. Its value is a boolean flag. Used by a single provider across 2 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the ke | 33 | 1 |
| x-isAttachment | `x-isAttachment` appears on response objects. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from where th | 33 | 1 |
| x-oas-optional | `x-oas-optional` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred | 32 | 1 |
|
x-okta-operations
vendor |
`x-okta-operations` appears on schema objects and properties. Its value is a list. Used by a single provider across 1 OpenAPI document. It sits in the `x-okta-` namespace, so its meaning is defined by | 32 | 1 |
| x-collection | `x-collection` appears on schema objects and properties. Its value is a string. Used by 2 providers across 2 OpenAPI documents. Observed values include `publicdailyactivity`, `publicdailycardiovascula | 31 | 2 |
| x-go-type-skip-optional-pointer-with-omitzero | `x-go-type-skip-optional-pointer-with-omitzero` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with type system | 31 | 1 |
| x-history-access | `x-history-access` appears on path items. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from where the ke | 31 | 1 |
| x-owner | `x-owner` appears on schema objects and properties. Its value is a string. Used by 2 providers across 2 OpenAPI documents. Observed values include `health-squad`, `movement-squad`, `sleep-squad`, `wel | 31 | 2 |
|
x-portone-discriminator
vendor |
`x-portone-discriminator` appears on schema objects and properties. Its value is a structured object. Used by a single provider across 1 OpenAPI document. It sits in the `x-portone-` namespace, so its | 31 | 1 |
|
x-aws-exception
vendor |
`x-aws-exception` appears on response objects. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. It sits in the `x-aws-` namespace, so its meaning is defined by aws too | 30 | 1 |
| x-operator-evidence | `x-operator-evidence` appears in the info block. Its value is a structured object. Used by 15 providers across 30 OpenAPI documents. Consistent with data & schema semantics — this is inferred from whe | 30 | 15 |
| x-remove-response | `x-remove-response` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 2 OpenAPI documents. Consistent with data & schema semantics — this is infer | 30 | 1 |
| x-maximum | `x-maximum` appears on schema objects and properties. Its value is an integer. Used by 2 providers across 6 OpenAPI documents. Observed values include `255`, `86400000`, `12`, `86399`. Consistent with | 29 | 2 |
|
x-okta-crud
vendor |
`x-okta-crud` appears on schema objects and properties. Its value is a list. Used by a single provider across 1 OpenAPI document. It sits in the `x-okta-` namespace, so its meaning is defined by okta | 29 | 1 |
|
x-postman-request
vendor |
`x-postman-request` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. It sits in the `x-postman-` namespace, so its meaning is defined by postman tooli | 29 | 1 |
|
x-postman-variants
vendor |
`x-postman-variants` appears on operations. Its value is a list. Used by a single provider across 1 OpenAPI document. It sits in the `x-postman-` namespace, so its meaning is defined by postman toolin | 29 | 1 |
| x-retention-policy | `x-retention-policy` appears on operations. Its value is a boolean flag. Used by a single provider across 5 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the | 29 | 1 |
| x-unicode-pattern | `x-unicode-pattern` appears on schema objects and properties. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `^[\p{L}\p{N}][\p{L}\p{N} _\-\.:/+'']* | 29 | 1 |
| x-apievangelist | `x-apievangelist` appears in the info block. Its value is a structured object. Used by 24 providers across 28 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where t | 28 | 24 |
| x-beamable-semantic-type | `x-beamable-semantic-type` appears on schema objects and properties. Its value is a string. Used by a single provider across 2 OpenAPI documents. Observed values include `Pid`, `Cid`, `Gamertag`, `Acc | 28 | 1 |
| x-derived-by | `x-derived-by` appears in the info block. Its value is a string. Used by 25 providers across 28 OpenAPI documents. Observed values include `API Evangelist enrichment pipeline`, `API Evangelist enrichm | 28 | 25 |
| x-endpoint-modeled | `x-endpoint-modeled` appears on operations. Its value is a boolean flag. Used by 5 providers across 5 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the key a | 28 | 5 |
| x-enforcer-exception-skip-codes | `x-enforcer-exception-skip-codes` appears on schema objects and properties. Its value is a string. Used by a single provider across 2 OpenAPI documents. Observed values include `WSCH006`. Consistent w | 28 | 1 |
| x-fieldValidation | `x-fieldValidation` appears on schema objects and properties. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `required`, `size(_,255)`, `required s | 28 | 1 |
| x-pass-resource-ids | `x-pass-resource-ids` appears on operations. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with identity & relationships — this is inferred from whe | 28 | 1 |
|
x-speakeasy-detail
vendor |
`x-speakeasy-detail` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 4 OpenAPI documents. It sits in the `x-speakeasy-` namespace, so its meanin | 28 | 1 |
|
x-bitmovin
vendor |
`x-bitmovin` appears on operations. Its value is a structured object. Used by a single provider across 1 OpenAPI document. It sits in the `x-bitmovin-` namespace, so its meaning is defined by bitmovin | 27 | 1 |
| x-derived-on | `x-derived-on` appears in the info block. Its value is a string. Used by 25 providers across 27 OpenAPI documents. Observed values include `2026-08-02`, `2026-08-04`, `2026-08-05`, `2026-08-09`. Consi | 27 | 25 |
| x-controller-name | `x-controller-name` appears on operations. Its value is a string. Used by a single provider across 2 OpenAPI documents. Observed values include `AgentController`, `ApplicationController`, `RumControll | 26 | 1 |
| x-go-enum-desc | `x-go-enum-desc` appears on schema objects and properties. Its value is a string. Used by a single provider across 2 OpenAPI documents. Observed values include `pending CommitStatusPending CommitStat | 26 | 1 |
| x-gw-ims-org-id | `x-gw-ims-org-id` appears on parameter objects. Its value is a structured object. Used by a single provider across 26 OpenAPI documents. Consistent with identity & relationships — this is inferred fro | 26 | 1 |
| x-schema-status | `x-schema-status` appears on schema objects and properties and on request bodies. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `modeled`. Consist | 26 | 1 |
| x-streaming-type | `x-streaming-type` appears on operations. Its value is a structured object. Used by a single provider across 6 OpenAPI documents. Consistent with type system — this is inferred from where the key appe | 26 | 1 |
| x-content-type-options | `x-content-type-options` appears on header objects. Its value is a string. Used by 3 providers across 11 OpenAPI documents. Observed values include `nosniff`. Consistent with type system — this is inf | 25 | 3 |
| x-devialet-minimal-firmware | `x-devialet-minimal-firmware` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `DOS >= 2.14`, `DOS >= 2.16`. Consistent with d | 25 | 1 |
| x-endpoints-modeled | `x-endpoints-modeled` appears on operations and in the info block. Its value is a boolean flag. Used by 8 providers across 10 OpenAPI documents. Consistent with data & schema semantics — this is infer | 25 | 8 |
|
x-github-plan
vendor |
`x-github-plan` appears in the info block. Its value is a string. Used by 2 providers across 25 OpenAPI documents. It sits in the `x-github-` namespace, so its meaning is defined by github tooling rat | 25 | 2 |
| x-isClosedInterval | `x-isClosedInterval` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 7 OpenAPI documents. Consistent with data & schema semantics — this is infe | 25 | 1 |
| x-operationName | `x-operationName` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `list`, `search all`, `search companies`, `search officers` | 25 | 1 |
| x-parsed-md-description | `x-parsed-md-description` appears on schema objects and properties. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — thi | 25 | 1 |
| x-type | `x-type` appears on schema objects and properties and on operations. Its value is a string. Used by 6 providers across 7 OpenAPI documents. Observed values include `String`, `object`, `true`. Consiste | 25 | 6 |
| x-expression | `x-expression` appears on schema objects and properties. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferr | 24 | 1 |
| x-migrated-v3 | `x-migrated-v3` appears on operations. Its value is a boolean flag. Used by a single provider across 2 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the key | 24 | 1 |
|
x-okta-added-version
vendor |
`x-okta-added-version` appears on parameter objects. Its value is a string. Used by a single provider across 1 OpenAPI document. It sits in the `x-okta-` namespace, so its meaning is defined by okta t | 24 | 1 |
|
x-postman-plan
vendor |
`x-postman-plan` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. It sits in the `x-postman-` namespace, so its meaning is defined by postman tooling | 24 | 1 |
| x-provider | `x-provider` appears in the info block. Its value is a string. Used by 11 providers across 24 OpenAPI documents. Observed values include `forgerock`, `Solidus Labs`, `cisco`, `Acuity Scheduling`. Cons | 24 | 11 |
| x-publicVersion | `x-publicVersion` appears in the info block. Its value is a boolean flag. Used by a single provider across 24 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where t | 24 | 1 |
| x-type-warning | `x-type-warning` appears on schema objects and properties. Its value is a string. Used by a single provider across 8 OpenAPI documents. Observed values include `FlaggableEnum`. Consistent with type sy | 24 | 1 |
|
x-bb-default-fields
vendor |
`x-bb-default-fields` appears on schema objects and properties. Its value is a list. Used by a single provider across 3 OpenAPI documents. It sits in the `x-bb-` namespace, so its meaning is defined b | 23 | 1 |
| x-curl-examples-parameters | `x-curl-examples-parameters` appears on operations. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred fr | 23 | 1 |
| x-kubernetes-int-or-string | `x-kubernetes-int-or-string` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this | 23 | 1 |
| x-rad-max | `x-rad-max` appears on schema objects and properties. Its value is an integer. Used by a single provider across 1 OpenAPI document. Observed values include `100`, `10000`, `200`, `3`. Consistent with | 23 | 1 |
|
x-speakeasy-include
vendor |
`x-speakeasy-include` appears on schema objects and properties. Its value is a boolean flag. Used by 3 providers across 3 OpenAPI documents. It sits in the `x-speakeasy-` namespace, so its meaning is | 23 | 3 |
|
x-stainless-any
vendor |
`x-stainless-any` appears on schema objects and properties. Its value is a boolean flag. Used by 5 providers across 6 OpenAPI documents. It sits in the `x-stainless-` namespace, so its meaning is defi | 23 | 5 |
| x-groq-metadata | `x-groq-metadata` appears on operations. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from where th | 22 | 1 |
| x-lua-required | `x-lua-required` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with validation & constraints — this is inferred | 22 | 1 |
| x-parent | `x-parent` appears in the document and on schema objects and properties. Its value is a string. Used by 7 providers across 8 OpenAPI documents. Observed values include `Brand Kits`, `true`, `Layers`, | 22 | 7 |
|
x-postman-request-names
vendor |
`x-postman-request-names` appears on operations. Its value is a list. Used by a single provider across 1 OpenAPI document. It sits in the `x-postman-` namespace, so its meaning is defined by postman t | 22 | 1 |
|
x-speakeasy-type-override
vendor |
`x-speakeasy-type-override` appears on schema objects and properties. Its value is a string. Used by 4 providers across 5 OpenAPI documents. It sits in the `x-speakeasy-` namespace, so its meaning is | 22 | 4 |
|
x-fern-token-variable-name
vendor |
`x-fern-token-variable-name` appears on security schemes. Its value is a string. Used by 2 providers across 21 OpenAPI documents. It sits in the `x-fern-` namespace, so its meaning is defined by fern | 21 | 2 |
| x-inline-with-overrides | `x-inline-with-overrides` appears on response objects. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with data & schema semantics — this is inferred from | 21 | 1 |
| x-metadata | `x-metadata` appears in the info block. Its value is a structured object. Used by 2 providers across 21 OpenAPI documents. Consistent with data & schema semantics — this is inferred from where the key | 21 | 2 |
|
x-ms-ccf-transaction-id
vendor |
`x-ms-ccf-transaction-id` appears on header objects. Its value is a structured object. Used by a single provider across 2 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is defined | 21 | 1 |
|
x-ms-paths
vendor |
`x-ms-paths` appears at the root of the document. Its value is a structured object. Used by a single provider across 21 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is defined b | 21 | 1 |
| x-url | `x-url` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 4 OpenAPI documents. Consistent with data & schema semantics — this is inferred from whe | 21 | 1 |
| x-verified | `x-verified` appears on operations. Its value is a string. Used by 6 providers across 10 OpenAPI documents. Observed values include `2026-08-19`, `2026-08-06`, `2026-08-04`, `2026-08-05`. Consistent w | 21 | 6 |
| x-version-timestamp | `x-version-timestamp` appears in the info block. Its value is a string. Used by a single provider across 21 OpenAPI documents. Observed values include `2025-11-26T19:10:23Z`, `2026-05-04T17:39:21Z`, ` | 21 | 1 |
Showing 400 of 1336. Use the search to reach the rest.
Work with this as data
Every extension here is available over the APIs.io API and to AI agents over MCP. OpenAPI Extensions is not yet its own endpoint on the v1 API. Reach it through catalog search and the tag graph, or the MCP server.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for openapi extensions
3 MCP tools reach this
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
Search the catalog
curl "https://apis.io/api/v1/search?q=data-schema-semantics&limit=10"
Everything under a tag
curl "https://apis.io/api/v1/tags/data-schema-semantics"Discovery needs no key. Ratings and market analysis are Pro.