Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.
All 92 tools →
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/m3ter:m3ter-pricing-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: m3ter Pricing API
description: 'If you are using Postman, you can:
- Use the **Download** button above to download the m3ter Open API spec JSON file and then import this file as the **m3ter API Collection** into your Workspace. See Importing the m3ter Open API in our main user Documentation for details. - Copy this link: m3ter-Template API Collection and use it to import the **m3ter-Template API Collection** into your Workspace. See Importing the m3ter Template API Collection in our main user Documentation for details. ---
# Introduction
The m3ter platform supports two HTTP-based REST APIs returning JSON encoded responses:
- The **Ingest API**, which you can use for submitting raw data measurements. *(See the Submit Measurements endpoint in this API Reference.)*
- The **Config API**, which you can use for configuration and management. *(All other endpoints in this API Reference.)*
## Authentication and Authorization
Our APIs use an industry-standard authorization protocol known as the OAuth 2.0 specification. OAuth2 supports several grant types, each designed for a specific use case. m3ter uses the following two grant types:
- **Authorization Code**: Used for human login access via the m3ter Console. - **Client Credentials**: Used for machine-to-machine communication and API access. Complete the following flow for API access:
1. **Create a Service User and add Permissions**: Log in to the m3ter Console, go to **Settings**, **Access** then **Service Users** tab, and create a Service User. To enable API calls, grant the user **Administrator** permissions. 2. **Generate Access Keys**: In the Console, open the *Overview* page for the Service User by clicking on the name. Generate an **Access Key id** and **Api Secret**. Make sure you copy the **Api Secret** because it is only visible at the time of creation. See Service Authentication for detailed instructions and an example. 3. **Obtain a Bearer Token using Basic Auth**: We implement the OAuth 2.0 Client Credentials Grant authentication flow for Service User Authentication. Submit a request to the m3ter OAuth Client Credentials authentication flow, using your concatenated **Access Key id** and **Api Secret** to obtain a Bearer Token for your Service User. *See examples below.*
4. **Bearer Token Usage**: Use the HTTP ''Authorization'' header with the bearer token to authorise all subsequent API requests. > Warning: The Bearer Token is valid for 18,000 seconds or 5 hours. When the token has expired, you must obtain a new one. Below are two examples for obtaining a Bearer Token using Basic Auth: the first in cURL and the second as a Python script. ### cURL Example
1. Open your terminal or command prompt. 2. Use the following `cURL` command to obtain a Bearer Token:
```bash
curl -X POST https://api.m3ter.com/oauth/token \
-H ''Content-Type: application/x-www-form-urlencoded'' \
-u your_access_key_id:your_api_secret \
-d ''grant_type=client_credentials''
```
Replace `your_access_key_id` and `your_api_secret` with your actual **Access Key id** and **Api Secret**. 3. Run the command, and if successful, it will return a JSON response containing the Bearer Token. The response will look like this:
```json
{
"access_token": "your_bearer_token",
"token_type": "Bearer",
"expires_in": 18000
}
```
You can then use the Bearer Token *(the value of `"access_token"`)* for subsequent API calls to m3ter. ### Python Example
1. Install the `requests` library if you haven''t already:
```bash
pip install requests
```
2.'
version: '1.0'
x-logo:
url: https://console.m3ter.com/m3ter-logo-black.svg
servers:
- url: https://api.m3ter.com
security:
- OAuth2: []
tags:
- name: Pricing
description: 'Endpoints for listing, creating, updating, retrieving, or deleting Pricing.
Create the Pricing for a Plan/PlanTemplate with usage data Aggregations, and define a usage-based pricing structure for charging end customer Accounts put on the Plan.
See Reviewing Pricing Options for Plans and Plan Templates for more information.'
paths:
/organizations/{orgId}/pricings:
get:
tags:
- Pricing
summary: List Pricings
description: Retrieve a list of Pricings filtered by date/time, Plan ID, PlanTemplate ID, or Pricing ID.
operationId: ListPricings
parameters:
- name: orgId
in: path
description: UUID of the organization. The Organization represents your company as a direct customer of the m3ter service.
required: true
style: simple
explode: false
schema:
type: string
- name: pageSize
in: query
description: Number of Pricings to retrieve per page.
required: false
allowEmptyValue: true
style: form
explode: true
schema:
maximum: 100
minimum: 1
type: integer
format: int32
- name: nextToken
in: query
description: '`nextToken` for multi-page retrievals.'
required: false
allowEmptyValue: true
style: form
explode: true
schema:
type: string
- name: date
in: query
description: Date/Time *(in ISO-8601 format)* to retrieve active Pricings for.
required: false
allowEmptyValue: true
style: form
explode: true
schema:
type: string
- name: planId
in: query
description: UUID of the Plan to retrieve Pricings for.
required: false
allowEmptyValue: true
style: form
explode: true
schema:
maximum: 36
minimum: 36
type: string
- name: planTemplateId
in: query
description: UUID of the PlanTemplate to retrieve Pricings for.
required: false
allowEmptyValue: true
style: form
explode: true
schema:
maximum: 36
minimum: 36
type: string
- name: aggregationId
in: query
description: 'UUID of the Aggregation to retrieve Pricings for.
**NOTE:** You cannot use the `aggregationId` query parameter as a single filter condition, but must always use it in combination with either the `planId` or `planTemplateId` query parameter.'
required: false
allowEmptyValue: true
style: form
explode: true
schema:
maximum: 36
minimum: 36
type: string
- name: ids
in: query
description: 'List of Pricing IDs to retrieve. '
required: false
allowEmptyValue: true
style: form
explode: true
schema:
type: array
items:
type: string
responses:
'200':
description: Returns the list of requested Pricings
content:
application/json:
schema:
$ref: '#/components/schemas/PaginatedPricingResponseData'
4XX:
$ref: '#/components/responses/Error'
5XX:
$ref: '#/components/responses/Error'
post:
tags:
- Pricing
summary: Create Pricing
description: 'Create a new Pricing.
**Notes:**
* **Pricing Plan or Plan Template?** Exactly one of `planId` or `planTemplateId` request parameters are required for this call to be valid. If you omit both, then you will receive a validation error.
* **Using Aggregation or Compound Aggregation for Pricing?** Exactly one of `aggregationId` or `compoundAggregationId` request parameters are required for this call to be valid. If you omit both, then you will receive a validation error.
* **Using Negative Values for Pricing?** If you use the `type` request parameter with the `DEBIT` option, *you cannot use negative values* for `fixedPrice` or `unitPrice` in `pricingBands` or `overagePricingBands`, and you''ll receive a validation error. If you omit a `type` request parameter a `DEBIT` pricing is created by default and the same constraint on the use of negative values applies.'
operationId: PostPricing
parameters:
- name: orgId
in: path
description: UUID of the organization. The Organization represents your company as a direct customer of the m3ter service.
required: true
style: simple
explode: false
schema:
type: string
requestBody:
description: ''
content:
application/json:
schema:
$ref: '#/components/schemas/PricingRequest'
required: true
responses:
'200':
description: Returns the created Pricing
content:
application/json:
schema:
$ref: '#/components/schemas/PricingResponse'
4XX:
$ref: '#/components/responses/Error'
5XX:
$ref: '#/components/responses/Error'
/organizations/{orgId}/pricings/{id}:
get:
tags:
- Pricing
summary: Retrieve Pricing
description: Retrieve the Pricing with the given UUID.
operationId: GetPricing
parameters:
- name: orgId
in: path
description: UUID of the organization. The Organization represents your company as a direct customer of the m3ter service.
required: true
style: simple
explode: false
schema:
type: string
- name: id
in: path
description: The UUID of the Pricing to retrieve.
required: true
style: simple
explode: false
schema:
type: string
responses:
'200':
description: Returns the requested Pricing
content:
application/json:
schema:
$ref: '#/components/schemas/PricingResponse'
4XX:
$ref: '#/components/responses/Error'
5XX:
$ref: '#/components/responses/Error'
put:
tags:
- Pricing
summary: Update Pricing
description: 'Update Pricing for the given UUID.
**Notes:**
* **Pricing Plan or Plan Template?** Exactly one of `planId` or `planTemplateId` request parameters are required for this call to be valid. If you omit both, then you will receive a validation error.
* **Using Aggregation or Compound Aggregation for Pricing?** Exactly one of `aggregationId` or `compoundAggregationId` request parameters are required for this call to be valid. If you omit both, then you will receive a validation error.
* **Using Negative Values for Pricing?** If you use the `type` request parameter with the `DEBIT` option, *you cannot use negative values* for `fixedPrice` or `unitPrice` in `pricingBands` or `overagePricingBands`, and you''ll receive a validation error. If you omit a `type` request parameter a `DEBIT` pricing is created by default and the same constraint on the use of negative values applies.'
operationId: PutPricing
parameters:
- name: orgId
in: path
description: UUID of the organization. The Organization represents your company as a direct customer of the m3ter service.
required: true
style: simple
explode: false
schema:
type: string
- name: id
in: path
description: The UUID of the Pricing to update.
required: true
style: simple
explode: false
schema:
maximum: 36
minimum: 36
type: string
requestBody:
description: ''
content:
application/json:
schema:
$ref: '#/components/schemas/PricingRequest'
required: true
responses:
'200':
description: Returns the updated Pricing
content:
application/json:
schema:
$ref: '#/components/schemas/PricingResponse'
4XX:
$ref: '#/components/responses/Error'
5XX:
$ref: '#/components/responses/Error'
delete:
tags:
- Pricing
summary: Delete Pricing
description: Delete the Pricing with the given UUID.
operationId: DeletePricing
parameters:
- name: orgId
in: path
description: UUID of the organization. The Organization represents your company as a direct customer of the m3ter service.
required: true
style: simple
explode: false
schema:
type: string
- name: id
in: path
description: The UUID of the Pricing to delete.
required: true
style: simple
explode: false
schema:
maximum: 36
minimum: 36
type: string
responses:
'200':
description: Return the deleted Pricing
content:
application/json:
schema:
$ref: '#/components/schemas/PricingResponse'
4XX:
$ref: '#/components/responses/Error'
5XX:
$ref: '#/components/responses/Error'
components:
schemas:
PricingBand:
required:
- fixedPrice
- lowerLimit
- unitPrice
type: object
properties:
id:
type: string
description: The ID for the Pricing band.
lowerLimit:
minimum: 0
type: number
description: Lower limit for the Pricing band.
format: double
fixedPrice:
type: number
description: Fixed price charged for the Pricing band.
format: double
unitPrice:
type: number
description: Unit price charged for the Pricing band.
format: double
creditTypeId:
type: string
description: '**OBSOLETE - this is deprecated and no longer used.** '
description: ''
PricingRequest:
type: object
properties:
aggregationId:
maxLength: 36
type: string
description: UUID of the Aggregation used to create the Pricing. Use this when creating a Pricing for a segmented aggregation.
compoundAggregationId:
maxLength: 36
type: string
description: UUID of the Compound Aggregation used to create the Pricing.
type:
description: '* **DEBIT**. Default setting. The amount calculated using the Pricing is added to the bill as a debit.
* **PRODUCT_CREDIT**. The amount calculated using the Pricing is added to the bill as a credit *(negative amount)*. To prevent negative billing, the bill will be capped at the total of other line items for the same Product.
* **GLOBAL_CREDIT**. The amount calculated using the Pricing is added to the bill as a credit *(negative amount)*. To prevent negative billing, the bill will be capped at the total of other line items for the entire bill, which might include other Products the Account consumes.
**IMPORTANT!**
* If you use the `type` request parameter with the `DEBIT` option, *you cannot use negative values* for `fixedPrice` or `unitPrice` in `pricingBands` or `overagePricingBands`, and you''ll receive a validation error.
* If you omit a `type` request parameter a `DEBIT` pricing is created by default and the same constraint on the use of negative values applies.'
$ref: '#/components/schemas/PricingType'
segment:
type: object
additionalProperties:
type: string
description: 'Specifies the segment value which you are defining a Pricing for using this call:
- For each segment value defined on a Segmented Aggregation you must create a separate Pricing and use the appropriate `aggregationId` parameter for the call.
- If you specify a segment value that has not been defined for the Aggregation, you''ll receive an error.
- If you''ve defined segment values for the Aggregation using a single wildcard or multiple wildcards, you can create Pricing for these wildcard segment values also.
For more details on creating Pricings for segment values on a Segmented Aggregation using this call, together with some examples, see the [Using API Call to Create Segmented Pricings](https://www.m3ter.com/docs/guides/plans-and-pricing/pricing-plans/pricing-plans-using-segmented-aggregations#using-api-call-to-create-a-segmented-pricing) in our User Documentation.'
tiersSpanPlan:
type: boolean
description: 'The default value is **FALSE**.
* If **TRUE**, usage accumulates over the entire period the priced Plan is active for the account, and is not reset for pricing band rates at the start of each billing period.
* If **FALSE**, usage does not accumulate, and is reset for pricing bands at the start of each billing period.'
minimumSpend:
minimum: 0
type: number
description: The minimum spend amount per billing cycle for end customer Accounts on a Plan to which the Pricing is applied.
format: double
minimumSpendDescription:
maxLength: 200
type: string
description: Minimum spend description *(displayed on the bill line item)*.
minimumSpendBillInAdvance:
type: boolean
description: 'The default value is **FALSE**.
* When **TRUE**, minimum spend is billed at the start of each billing period.
* When **FALSE**, minimum spend is billed at the end of each billing period.
*(Optional)*. Overrides the setting at Organization level for minimum spend billing in arrears/in advance.'
overagePricingBands:
type: array
description: 'Specify Prepayment/Balance overage pricing in pricing bands for the case of a **Tiered** pricing structure. The overage pricing rates will be used to charge for usage if the Account has a Commitment/Prepayment or Balance applied to it and the entire Commitment/Prepayment or Balance amount has been consumed.
**Constraints:**
* Can only be used for a **Tiered** pricing structure. If cumulative is **FALSE** and you defined `overagePricingBands`, then you''ll receive an error.
* If `tiersSpanPlan` is set to **TRUE** for usage accumulates over entire contract period, then cannot be used.
* If the Commitment/Prepayement or Balance has an `overageSurchargePercent` defined, then this will override any `overagePricingBands` you''ve defined for the pricing.'
items:
$ref: '#/components/schemas/PricingBand'
description: ''
allOf:
- $ref: '#/components/schemas/BasePricingRequestWithPricingBands'
- $ref: '#/components/schemas/BasePricingRequest'
- $ref: '#/components/schemas/AbstractRequest'
BasePricingRequestWithPricingBands:
type: object
description: ''
allOf:
- $ref: '#/components/schemas/BasePricingRequest'
- $ref: '#/components/schemas/AbstractRequest'
- required:
- pricingBands
type: object
properties:
pricingBands:
minItems: 1
type: array
description: ''
items:
$ref: '#/components/schemas/PricingBand'
AbstractRequest:
type: object
properties:
version:
type: integer
description: 'The version number of the entity:
- **Create entity:** Not valid for initial insertion of new entity - *do not use for Create*. On initial Create, version is set at 1 and listed in the response.
- **Update Entity:** On Update, version is required and must match the existing version because a check is performed to ensure sequential versioning is preserved. Version is incremented by 1 and listed in the response.'
format: int64
x-stainless-terraform-configurability: computed
x-stainless-terraform-always-send: true
description: ''
BasePricingResponseWithPricingBands:
type: object
description: ''
allOf:
- $ref: '#/components/schemas/BasePricingResponse'
- $ref: '#/components/schemas/AbstractResponseWithAuditFields'
- $ref: '#/components/schemas/AbstractResponse'
- type: object
properties:
pricingBands:
type: array
description: ''
items:
$ref: '#/components/schemas/PricingBand'
BasePricingRequest:
type: object
description: ''
allOf:
- $ref: '#/components/schemas/AbstractRequest'
- required:
- startDate
type: object
properties:
code:
maxLength: 80
pattern: ^([^[\p{Cntrl}\s]])|([^[\p{Cntrl}\s]][[^[\p{Cntrl}\s]] ]*[^[\p{Cntrl}\s]])$
type: string
description: Unique short code for the Pricing.
planId:
type: string
description: UUID of the Plan the Pricing is created for.
planTemplateId:
type: string
description: UUID of the Plan Template the Pricing is created for.
cumulative:
type: boolean
description: 'Controls whether or not charge rates under a set of pricing bands configured for a Pricing are applied according to each separate band or at the highest band reached.
*(Optional)*. The default value is **FALSE**.
* When TRUE, at billing charge rates are applied according to each separate band.
* When FALSE, at billing charge rates are applied according to highest band reached.
**NOTE:** Use the `cumulative` parameter to create the type of Pricing you require. For example, for Tiered Pricing set to **TRUE**; for Volume Pricing, set to **FALSE**.'
startDate:
type: string
description: The start date *(in ISO-8601 format)* for when the Pricing starts to be active for the Plan or the Plan Template.*(Required)*
format: date-time
endDate:
type: string
description: 'The end date *(in ISO-8601 format)* for when the Pricing ceases to be active for the Plan or the Plan Template.
*(Optional)* If not specified, the Pricing remains active indefinitely.'
format: date-time
description:
maxLength: 200
type: string
description: Displayed on Bill line items.
accountingProductId:
maxLength: 36
minLength: 36
type: string
description: Optional Product ID this Pricing should be attributed to for accounting purposes
PricingType:
type: string
description: '* **DEBIT**. Default setting. The amount calculated using the Pricing is added to the bill as a debit.
* **PRODUCT_CREDIT**. The amount calculated using the Pricing is added to the bill as a credit *(negative amount)*. To prevent negative billing, the bill will be capped at the total of other line items for the *same* Product.
* **GLOBAL_CREDIT**. The amount calculated using the Pricing is added to the bill as a credit *(negative amount)*. To prevent negative billing, the bill will be capped at the total of other line items for the entire bill, which might include other Products the Account consumes.'
enum:
- DEBIT
- PRODUCT_CREDIT
- GLOBAL_CREDIT
AggregationType:
type: string
description: ''
enum:
- SIMPLE
- COMPOUND
PricingResponse:
type: object
description: ''
allOf:
- $ref: '#/components/schemas/BasePricingResponseWithPricingBands'
- $ref: '#/components/schemas/BasePricingResponse'
- $ref: '#/components/schemas/AbstractResponseWithAuditFields'
- $ref: '#/components/schemas/AbstractResponse'
- type: object
properties:
aggregationId:
type: string
description: UUID of the Aggregation used to create the Pricing. Use this when creating a Pricing for a segmented aggregation.
compoundAggregationId:
type: string
description: UUID of the Compound Aggregation used to create the Pricing.
type:
description: '* **DEBIT**. Default setting. The amount calculated using the Pricing is added to the bill as a debit.
* **PRODUCT_CREDIT**. The amount calculated using the Pricing is added to the bill as a credit *(negative amount)*. To prevent negative billing, the bill will be capped at the total of other line items for the *same* Product.
* **GLOBAL_CREDIT**. The amount calculated using the Pricing is added to the bill as a credit *(negative amount)*. To prevent negative billing, the bill will be capped at the total of other line items for the entire bill, which might include other Products the Account consumes.'
$ref: '#/components/schemas/PricingType'
segment:
type: object
additionalProperties:
type: string
description: 'Name of the segment for which you are defining a Pricing.
For each segment in a segmented aggregation, make a separate call using `aggregationId` parameter to update a Pricing.'
tiersSpanPlan:
type: boolean
description: 'The default value is **FALSE**.
* If TRUE, usage accumulates over the entire period the priced Plan is active for the account, and is not reset for pricing band rates at the start of each billing period.
* If FALSE, usage does not accumulate, and is reset for pricing bands at the start of each billing period.'
minimumSpend:
type: number
description: The minimum spend amount per billing cycle for end customer Accounts on a Plan to which the Pricing is applied.
format: double
minimumSpendDescription:
type: string
description: Minimum spend description *(displayed on the bill line item)*.
minimumSpendBillInAdvance:
type: boolean
description: 'The default value is **FALSE**.
* When TRUE, minimum spend is billed at the start of each billing period.
* When FALSE, minimum spend is billed at the end of each billing period.
*(Optional)*. Overrides the setting at Organization level for minimum spend billing in arrears/in advance.'
aggregationType:
description: ''
$ref: '#/components/schemas/AggregationType'
segmentString:
type: string
description: ''
overagePricingBands:
type: array
description: 'The Prepayment/Balance overage pricing in pricing bands for the case of a **Tiered** pricing structure. '
items:
$ref: '#/components/schemas/PricingBand'
accountingProductId:
type: string
description: ''
AbstractResponse:
required:
- id
type: object
properties:
id:
type: string
description: 'The UUID of the entity. '
version:
type: integer
description: 'The version number:
- **Create:** On initial Create to insert a new entity, the version is set at 1 in the response.
- **Update:** On successful Update, the version is incremented by 1 in the response.'
format: int64
x-stainless-terraform-configurability: computed
x-stainless-terraform-always-send: true
description: ''
AbstractResponseWithAuditFields:
type: object
description: ''
allOf:
- $ref: '#/components/schemas/AbstractResponse'
- type: object
properties:
dtCreated:
type: string
description: The DateTime when this item was created *(in ISO-8601 format)*.
format: date-time
x-stainless-skip: terraform
dtLastModified:
type: string
description: The DateTime when this item was last modified *(in ISO-8601 format)*.
format: date-time
x-stainless-skip: terraform
createdBy:
type: string
description: The ID of the user who created this item.
x-stainless-skip: terraform
lastModifiedBy:
type: string
description: The ID of the user who last modified this item.
x-stainless-skip: terraform
BasePricingResponse:
type: object
description: ''
allOf:
- $ref: '#/components/schemas/AbstractResponseWithAuditFields'
- $ref: '#/components/schemas/AbstractResponse'
- type: object
properties:
planId:
type: string
description: UUID of the Plan the Pricing is created for.
planTemplateId:
type: string
description: UUID of the Plan Template the Pricing was created for.
cumulative:
type: boolean
description: 'Controls whether or not charge rates under a set of pricing bands configured for a Pricing are applied according to each separate band or at the highest band reached.
The default value is **TRUE**.
* When TRUE, at billing charge rates are applied according to each separate band.
* When FALSE, at billing charge rates are applied according to highest band reached.'
startDate:
type: string
description: The start date *(in ISO-8601 format)* for when the Pricing starts to be active for the Plan of Plan Template.
format: date-time
endDate:
type: string
description: 'The end date *(in ISO-8601 format)* for when the Pricing ceases to be active for the Plan or Plan Template.
If not specified, the Pricing remains active indefinitely.'
format: date-time
code:
type: string
description: Unique short code for the Pricing.
description:
type: string
description: Displayed on Bill line items.
accountingProductId:
type: string
description: Optional Product ID this Pricing should be attributed to for accounting purposes.
PaginatedPricingResponseData:
type: object
properties:
data:
type: array
description: ''
items:
$ref: '#/components/schemas/PricingResponse'
nextToken:
type: string
description: ''
description: ''
responses:
Error:
description: Error message
content:
application/json:
schema:
type: object
properties:
message:
type: string
securitySchemes:
OAuth2:
type: oauth2
description: "m3ter supports machine to machine authentication using the `clientCredentials` OAuth2 flow.\n\nThe `authorizationCode` flow controls access for human users via the m3ter Console application. \n"
flows:
clientCredentials:
tokenUrl: /oauth/token
scopes:
m3ter-resources/m3ter-scope: m3ter resources
authorizationCode:
authorizationUrl: https://m3ter.auth.us-east-1.amazoncognito.com/oauth2/authorize
tokenUrl: https://m3ter.auth.us-east-1.amazoncognito.com/oauth2/token
scopes:
m3ter-resources/m3ter-scope: m3ter resources
openid: OpenID
email: email
x-provenance:
method: harvested
publisher: M3ter
source: https://docs.m3ter.com/openapi.json
note: split by refine-openapis from the provider's own published document, verified by fetch (openapi/_original/*.fetch.json);
stamped by stamp-openapi-provenance.py (roadmap#793)