Monetization
4 distinct extensions were invented to do this job. Each one is a provider deciding OpenAPI would not carry something and building their own way through. Where a job has many names and few uses each, nobody won — the problem was solved privately, over and over.
4 extensions
471 occurrences
1 vendor-named
The extensions
| Extension | What it appears to do | Uses | Providers |
|---|---|---|---|
| x-token-cost | `x-token-cost` appears on operations. Its value is an integer. Used by a single provider across 2 OpenAPI documents. Observed values include `10`, `20`, `5`, `6`. Consistent with monetization — this i | 371 | 1 |
| x-endpoint-cost | `x-endpoint-cost` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `medium`, `light`, `0.01`, `heavy`. Consistent with monetiz | 94 | 1 |
| x-x402-price | `x-x402-price` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `$0.001`, `$0.05`, `$1.00`. Consistent with monetization — thi | 4 | 1 |
|
x-amz-request-charged
vendor |
`x-amz-request-charged` appears on header objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. It sits in the `x-amz-` namespace, so its meaning is defined b | 2 | 1 |