Data & schema semantics

x-source-page

`x-source-page` appears on operations. Its value is a string. Used by 4 providers across 20 OpenAPI documents. Observed values include `https://developer.westernalliancebank.com/s/postman-collection`, `https://docs.thefork.io/B2B-API/API specifications/post-v-1-call-center-call-rec`, `https://docs.thefork.io/B2B-API/API specifications/get-v-1-customers-eb6`, `https://docs.thefork.io/B2B-API/API specifications/get-v-1-customers-id-11e`. Consistent with data & schema semantics — this is inferred from where the key appears and what it carries, not from any published definition.

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

Where it appears

Location in the documentOccurrences
operation 69
info 12

What its value looks like

Value shapeOccurrences
string81

Observed values

Sampled from the specifications, most frequent first.

https://developer.westernalliancebank.com/s/postman-collectionhttps://docs.thefork.io/B2B-API/API specifications/post-v-1-call-center-call-rechttps://docs.thefork.io/B2B-API/API specifications/get-v-1-customers-eb6https://docs.thefork.io/B2B-API/API specifications/get-v-1-customers-id-11ehttps://docs.thefork.io/B2B-API/API specifications/patch-v-1-integration-status-https://docs.thefork.io/B2B-API/API specifications/get-v-1-reservations-60chttps://docs.thefork.io/B2B-API/API specifications/get-v-1-reservations-id-f82https://docs.thefork.io/B2B-API/API specifications/patch-v-1-reservations-id-e25

Providers publishing it

All 4.

airalolafourchettetheforkwestern-alliance-bancorporation

Why this is not in OpenAPI

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