Data & schema semantics · Identity & relationships

x-api-key

`x-api-key` appears on schema objects and properties. Its value is a string. Used by 21 providers across 83 OpenAPI documents. Observed values include `G3VIdNTOjscKbVGPqb8aNMeCA1dAHxnz`, `integrator's key`, `my-api-key`, `MfAri03JO8hgVzerGiITA6FGafayv5XV`. Consistent with identity & relationships — 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.
174 occurrences
83 documents
21 providers
purpose-named

Where it appears

Location in the documentOccurrences
info 7
parameter 29
schema 83
securityScheme 27
other 3
header 11
operation 1
requestBody 8
response 5

What its value looks like

Value shapeOccurrences
string108
object63
empty3

Observed values

Sampled from the specifications, most frequent first.

G3VIdNTOjscKbVGPqb8aNMeCA1dAHxnzintegrator's keymy-api-keyMfAri03JO8hgVzerGiITA6FGafayv5XVYOUR_API_KEY070C895C-AE61-4629-A603-829FC54CD816sk_your_api_key — alternative to the Authorization header. Provide one of the$EXA_API_KEY\" \\\n -H \"Exa-Beta: agent-2026-05-07\" \\\n -d '{\n \"query\

Providers publishing it

All 21.

8x8adobe-launchadobe-suiteaetnaanyimagedetectorcachetdaytona-ioemburseemergeexa-aifaciliofirst-american-financialharnessmikmakmv-sistemasphotoroomportcastpubliqspektrsupagluetrustradius

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.