Data & schema semantics

x-ratelimit-remaining

`x-ratelimit-remaining` appears on header objects. Its value is a structured object. Used by 10 providers across 10 OpenAPI documents. 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 HTTP header, not an extension

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.

This is an HTTP header name, not a vendor extension. It appears under a headers: map, which is the same syntactic position an extension key occupies — but OpenAPI models headers natively and this is not extending anything. It is listed here because it turns up when you inventory the x- namespace, and leaving it out would hide why the namespace looks bigger than it is.

Also published under another name. This key exists in the wild spelled more than one way — differing only by case or a hyphen, which means no tool can treat them as the same thing: x-RateLimit-Remaining. Each is catalogued separately here because that is how they exist.

40 occurrences

10 documents

10 providers

purpose-named

Where it appears

Location in the document	Occurrences
header	39
info	1

What its value looks like

Value shape	Occurrences
object	39
integer	1

Observed values

Sampled from the specifications, most frequent first.

599

Providers publishing it

All 10.

bluecore ev-energy ezyvet limble-cmms overshoot overshootai pingcap remote-com usertesting zoominfo

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.