SDK & code generation

x-ruby-regexp

`x-ruby-regexp` appears on schema objects and properties. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `(?-mix:\A[[:alpha:]\s‘’`'-]*\z)`, `(?-mix:\A[[:alpha:]\s`'\-.]*\z)`, `(?-mix:\A[a-zA-Z0-9&\/\\\-\s]+\z)`, `(?i-mx:\A[a-z0-9 ]+\Z)`. Consistent with sdk & code generation — this is inferred from where the key appears and what it carries, not from any published definition.

SDK & code generation 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.
34 occurrences
1 documents
1 providers
purpose-named

Where it appears

Location in the documentOccurrences
schema 33
operation 1

What its value looks like

Value shapeOccurrences
string34

Observed values

Sampled from the specifications, most frequent first.

(?-mix:\A[[:alpha:]\s‘’`'-]*\z)(?-mix:\A[[:alpha:]\s`'\-.]*\z)(?-mix:\A[a-zA-Z0-9&\/\\\-\s]+\z)(?i-mx:\A[a-z0-9 ]+\Z)(?-mix:\A[[:alpha:]\s`'\-]*\z)(?-mix:\A(id|forename|surname|percentage|avc_percentage|company_percentage|emplo(?-mix:\A[^<>]*\z)

Providers publishing it

All 1.

smart-pension

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 sdk & code generation job.