Monetization

x-payment-info

`x-payment-info` appears on operations. Its value is a structured object. Used by 33 providers across 66 OpenAPI documents. Consistent with monetization — this is inferred from where the key appears and what it carries, not from any published definition.

Monetization 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.

746 occurrences

66 documents

33 providers

purpose-named

Where it appears

Location in the document	Occurrences
operation	743
info	2
root	1

What its value looks like

Value shape	Occurrences
string	2
object	744

Observed values

Sampled from the specifications, most frequent first.

&a3*a3

Providers publishing it

All 33.

agent-ready-dev agent402-dev agmsg-world algovoi-co-uk babyblueviper-com brick-blue cables canfly-ai coinrailz-com connskill-com done execution-market getemboss-ai gonna-bond graphadvocate-com hatchable-site hergertsynthora-com hilt-so ingest0r-com kannkidas-de liquidagent-ai litescrape machinelibrary-ai mercury-hq-com ontopx402 s1-dev shveik smklog-com snhp-dev taskfolk taskhawktech-com venice-ai xquik-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 monetization job.