Data & schema semantics

x-metaDescription

`x-metaDescription` appears in the info block. Its value is a string. Used by a single provider across 21 OpenAPI documents. Observed values include `Find quick answers to questions about the Vonage Account API in this reference g`, `Find quick answers to questions about the Vonage Application API (v2.0) in this `, `Find quick answers to questions about the Vonage Audit API in this reference gui`, `Find quick answers to questions about the Vonage Conversation API (v1.0) in this`. 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.
21 occurrences
21 documents
1 providers
purpose-named

Where it appears

Location in the documentOccurrences
info 21

What its value looks like

Value shapeOccurrences
string21

Observed values

Sampled from the specifications, most frequent first.

Find quick answers to questions about the Vonage Account API in this reference gFind quick answers to questions about the Vonage Application API (v2.0) in this Find quick answers to questions about the Vonage Audit API in this reference guiFind quick answers to questions about the Vonage Conversation API (v1.0) in thisFind quick answers to questions about the Vonage Dispatch API in this reference Allows clients to request real-time information related to a phone number.Find quick answers to questions about the Vonage Media API in this reference guiFind quick answers to questions about the Vonage Meetings API in this reference

Providers publishing it

All 1.

vonage

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.