Documentation & DX

x-documentation-url

`x-documentation-url` appears on operations. Its value is a string. Used by 2 providers across 3 OpenAPI documents. Observed values include `https://www.genderapi.io/docs-phone-validation-formatter-api`, `https://www.genderapi.io/docs-gender-from-name-single`, `https://www.genderapi.io/docs-gender-from-name-multiple`, `https://www.genderapi.io/docs-gender-from-email-single`. Consistent with documentation & dx — this is inferred from where the key appears and what it carries, not from any published definition.

Documentation & DX 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.
19 occurrences
3 documents
2 providers
purpose-named

Where it appears

Location in the documentOccurrences
info 1
operation 18

What its value looks like

Value shapeOccurrences
string19

Observed values

Sampled from the specifications, most frequent first.

https://www.genderapi.io/docs-phone-validation-formatter-apihttps://www.genderapi.io/docs-gender-from-name-singlehttps://www.genderapi.io/docs-gender-from-name-multiplehttps://www.genderapi.io/docs-gender-from-email-singlehttps://www.genderapi.io/docs-gender-from-email-multiplehttps://www.genderapi.io/docs-gender-from-username-singlehttps://www.genderapi.io/docs-gender-from-username-multiplehttps://www.genderapi.io/docs-usage-and-quota

Providers publishing it

All 2.

firefliesozan-soft

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 documentation & dx job.