Data & schema semantics · Naming & aliasing

x-original-source

`x-original-source` appears at the root of the document. Its value is a string. Used by 2 providers across 7 OpenAPI documents. Observed values include `https://developer.telesign.com/enterprise/openapi/email-intelligence-extended-re`, `https://developer.telesign.com/enterprise/openapi/engage-api-number-masking.json`, `https://developer.telesign.com/enterprise/openapi/engage-api-voice.json`, `https://developer.telesign.com/enterprise/openapi/engage-callbacks.json`. Consistent with naming & aliasing — 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.
7 occurrences
7 documents
2 providers
purpose-named

Where it appears

Location in the documentOccurrences
root 7

What its value looks like

Value shapeOccurrences
string7

Observed values

Sampled from the specifications, most frequent first.

https://developer.telesign.com/enterprise/openapi/email-intelligence-extended-rehttps://developer.telesign.com/enterprise/openapi/engage-api-number-masking.jsonhttps://developer.telesign.com/enterprise/openapi/engage-api-voice.jsonhttps://developer.telesign.com/enterprise/openapi/engage-callbacks.jsonhttps://developer.telesign.com/enterprise/openapi/sms-verify-api-callbacks.jsonhttps://developer.telesign.com/enterprise/openapi/verify-api-callbacks.jsonhttps://api.webcrawlerapi.com/swagger/doc.json

Providers publishing it

All 2.

telesignwebcrawlerapi-com

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.