Documentation & DX

x-metaTitle

`x-metaTitle` appears in the info block. Its value is a string. Used by a single provider across 22 OpenAPI documents. Observed values include `Vonage Account API Reference | Vonage API Documentation`, `Vonage Application API (v2.0) Reference | Vonage API Documentation`, `Vonage Audit API Reference | Vonage API Documentation`, `Vonage Conversation API (v1.0) Reference | Vonage API Documentation`. 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.
22 occurrences
22 documents
1 providers
purpose-named

Where it appears

Location in the documentOccurrences
info 22

What its value looks like

Value shapeOccurrences
string22

Observed values

Sampled from the specifications, most frequent first.

Vonage Account API Reference | Vonage API DocumentationVonage Application API (v2.0) Reference | Vonage API DocumentationVonage Audit API Reference | Vonage API DocumentationVonage Conversation API (v1.0) Reference | Vonage API DocumentationVonage Dispatch API Reference | Vonage API DocumentationVonage Identity Insights API Reference | Vonage API DocumentationVonage Device Location Retrieval API Reference | Vonage API DocumentationVonage Media API Reference | Vonage API Documentation

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