Data & schema semantics

x-discovery-path-template

`x-discovery-path-template` appears on operations. Its value is a string. Used by a single provider across 2 OpenAPI documents. Observed values include `v2/{name}`, `v3/{name}`, `v2/{parent}/contexts`, `v2/{parent}/entityTypes`. 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.
437 occurrences
2 documents
1 providers
purpose-named

Where it appears

Location in the documentOccurrences
operation 414
path 23

What its value looks like

Value shapeOccurrences
string437

Observed values

Sampled from the specifications, most frequent first.

v2/{name}v3/{name}v2/{parent}/contextsv2/{parent}/entityTypesv3/{parent}/entityTypesv3/{parent}/versionsv2/{parent}/agentv2/{parent}/knowledgeBases

Providers publishing it

All 1.

google-dialogflow

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.