Monetization
25 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.
25 extensions
2227 occurrences
1 vendor-named
The extensions
| Extension | What it appears to do | Uses | Providers |
|---|---|---|---|
| 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 a | 746 | 33 |
| 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-fodda-billing-type | `x-fodda-billing-type` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `standalone_supplemental`, `free`, `search`, `deep_res | 157 | 1 |
| x-fodda-price-usd | `x-fodda-price-usd` appears on operations. Its value is a number. Used by a single provider across 1 OpenAPI document. Observed values include `2.5`, `0`, `10`, `0.5`. Consistent with monetization — t | 157 | 1 |
| x-payment | `x-payment` appears on operations. Its value is a structured object. Used by 6 providers across 6 OpenAPI documents. Consistent with monetization — this is inferred from where the key appears and what | 124 | 6 |
| x-price | `x-price` appears on operations. Its value is a string. Used by 2 providers across 2 OpenAPI documents. Observed values include `$0.02`, `$0.01`, `$0.03`, `$0.05`. Consistent with monetization — this | 124 | 2 |
| 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-price-usd | `x-price-usd` appears on operations. Its value is a number. Used by a single provider across 1 OpenAPI document. Observed values include `0.25`, `0.5`, `0.05`, `0.1`. Consistent with monetization — th | 80 | 1 |
| x-humanmirror-pricing-tier | `x-humanmirror-pricing-tier` appears on operations. Its value is a string. Used by a single provider across 4 OpenAPI documents. Observed values include `granular_unit_0_010`, `granular_unit_0_001`, ` | 78 | 1 |
| x-humanmirror-price-usdc | `x-humanmirror-price-usdc` appears on operations. Its value is a string. Used by a single provider across 2 OpenAPI documents. Observed values include `0.010`, `0.001`, `0.050`, `5.000`. Consistent wi | 74 | 1 |
| x-credit-cost | `x-credit-cost` appears on operations. Its value is an integer. Used by 3 providers across 4 OpenAPI documents. Observed values include `1`, `2`, `Credits are consumed per processed record, not per HT | 61 | 3 |
| x-x402 | `x-x402` appears on operations. Its value is a structured object. Used by 5 providers across 7 OpenAPI documents. Consistent with monetization — this is inferred from where the key appears and what it | 56 | 5 |
| x-payment-accepts | `x-payment-accepts` appears at the root of the document. Its value is a list. Used by 2 providers across 27 OpenAPI documents. Consistent with monetization — this is inferred from where the key appear | 27 | 2 |
| x-pricing | `x-pricing` appears in the info block. Its value is a structured object. Used by 2 providers across 27 OpenAPI documents. Consistent with monetization — this is inferred from where the key appears and | 27 | 2 |
| x-x402-price-usdc | `x-x402-price-usdc` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `0.01`, `0.001`, `5.00`, `0.005`. Consistent with monetiz | 19 | 1 |
| x-moltrust-pricing | `x-moltrust-pricing` appears on operations. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with monetization — this is inferred from where the key ap | 12 | 1 |
| x-humanmirror-paid-price-usdc | `x-humanmirror-paid-price-usdc` appears on operations. Its value is a string. Used by a single provider across 3 OpenAPI documents. Observed values include `0.001`. Consistent with monetization — this | 6 | 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-mpp-charge | `x-mpp-charge` appears on operations. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with monetization — this is inferred from where the key appears | 3 | 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 |
| x-humanmirror-pricing-ladder | `x-humanmirror-pricing-ladder` appears at the root of the document. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with monetization — this is inferr | 1 | 1 |
| x-payment-client-guidance | `x-payment-client-guidance` appears on operations. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with monetization — this is inferred from where the | 1 | 1 |
| x-payment-protocol | `x-payment-protocol` appears in the info block. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `x402-v2`. Consistent with monetization — this is in | 1 | 1 |
| x-payment-tx | `x-payment-tx` appears on schema objects and properties. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with monetization — this is inferred from whe | 1 | 1 |
| x-x402-global | `x-x402-global` appears at the root of the document. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with monetization — this is inferred from where t | 1 | 1 |