Data & schema semantics

x-guidance

`x-guidance` appears in the info block and on operations. Its value is a string. Used by 22 providers across 52 OpenAPI documents. Observed values include `POST a small JSON body (see each operation''s requestBody) with no`, `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,`. 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
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.
80 occurrences
52 documents
22 providers
purpose-named

Where it appears

Location in the documentOccurrences
info 52
operation 28

What its value looks like

Value shapeOccurrences
string78
object2

Observed values

Sampled from the specifications, most frequent first.

POST a small JSON body (see each operation''s requestBody) with noCall this once per website to order directory submissions. Save the submissionidSend a query that is either a plain IP address (like 8.8.8.8) or an ASN referencCall 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 optiSend an empty body for the newest available inflation report. Send 'period' as YSend a JSON body with a 'url' (required, must start with http:// or https://) anCall this endpoint with POST and a JSON body containing a ''domains'' array of b

Providers publishing it

All 22.

agent-ready-devagent402-devagmsg-worldalgovoi-co-ukbabyblueviper-comcablescanfly-aicoinrailz-comconnskill-comdoneexecution-marketgetemboss-aigonna-bondhilt-soingest0r-comliquidagent-ailitescrapeontopx402s1-devshveikvenice-aixquik-api

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.