x-ai-instructions
`x-ai-instructions` appears on operations and in the info block. Its value is a string. Used by 2 providers across 27 OpenAPI documents. Observed values include `Call this once per website to order directory submissions. Save the submissionid`, `Send a query that is either a plain IP address (like 8.8.8.8) or an ASN referenc`, `Call this when a user asks whether a domain's email logo (BIMI) setup will work,`, `POST a JSON body with a required 'url' field (the endpoint to probe) and an opti`. Consistent with type system — 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 | 27 | |
| operation | 28 |
What its value looks like
| Value shape | Occurrences |
|---|---|
| string | 55 |
Observed values
Sampled from the specifications, most frequent first.
Providers publishing it
All 2.
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.