x-apisguru-driver
`x-apisguru-driver` appears in the info block. Its value is a string. Used by 98 providers across 106 OpenAPI documents. It sits in the `x-apisguru-` namespace, so its meaning is defined by apisguru tooling rather than by OpenAPI. Observed values include `external`. Consistent with data & schema semantics — this is inferred from where the key appears and what it carries, not from any published definition.
Where it appears
| Location in the document | Occurrences | |
|---|---|---|
| info | 106 |
What its value looks like
| Value shape | Occurrences |
|---|---|
| string | 106 |
Observed values
Sampled from the specifications, most frequent first.
Providers publishing it
Showing 50 of 98.
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.