thatDIDs - Pricing

Pay-as-you-go pricing

MATTR uses a pay-as-you-go pricing model.

Each chargeable activity is represented by a SKU. A SKU will be charged on one of the following bases:

  1. Usage-based charges are determined by the volume of an activity x price per activity – SKUs charged on this basis may or may not be the direct result of your invocation of an API

  2. Variable recurring charges are calculated based on the quantity of a particular entity managed across time (such as the number of credentials stored in a given month x price per each credential stored)

  3. Fixed recurring charges are charged as a fixed monthly fee (often as a result of provisioning an Add-On)

MATTR pricing is tiered based on the volume of use of each SKU. If your usage volumes are likely to fall outside the published tiers, please contact us to discuss our high-volume discounts.

All prices presented are exclusive of any taxes that may apply.

Pricing for DIDs

SKU: DID Operation

A DID Operation SKU is charged for successful requests resulting in a write to the underlying Verifiable Data Registry used by the DID as per its DID method;

  • DID creation

  • DID deactivation

A DID Operation SKU is charged for each successful request to the Create a DID API endpoint to create a DID. When you create a DID you are required to specify a method attribute. The method attribute determines the DID method used and thus the specific SKU charged.

A DID Operation SKU is charged for each successful request to the Delete a DID API endpoint. When you created the DID you specified a method attribute. The method attribute determines the specific SKU charged when deactivating a DID.

MONTHLY VOLUME RANGE (Price per DID Operation)
SKU 0–1,000 1,001+
DID Operation
(did:key)
Contact us for pricing Contact us for volume pricing
MONTHLY VOLUME RANGE (Price per DID Operation)
SKU 0–20 21+
DID Operation
(did:ion, did:web)
Contact us for pricing Contact us for volume pricing

SKU: Manage DID

Whenever a DID is created, the key material and other requisite data is maintained to ensure ongoing management of the DID. Each month in which a DID has been managed (for all / or a portion of the month) a Manage DID SKU shall be charged. DIDs are managed until such time as they are deactivated via the Delete a DID API endpoint. When you created the DID you specified a method attribute. The method attribute determines the DID method managed and thus the specific Manage DID SKU charged.

MONTHLY VOLUME RANGE (Price per DID managed per month)
SKU 0–3,000 3,001+
Manage DID
(did:key)
Contact us for pricing Contact us for volume pricing
MONTHLY VOLUME RANGE (Price per DID managed per month)
SKU 0–60 61+
Manage DID
(did:ion, did:web)
Contact us for pricing Contact us for volume pricing

SKU: Resolve DID

A Resolve DID SKU is charged for each request to the Resolve a DID API endpoint. When you call the Resolve a DID API endpoint you specify a DID to be resolved. The DID contains a method-name component which determines the specific SKU that will be charged.

This SKU is charged only as a result of an explicit call to the Resolve a DID API endpoint and is not additionally charged as a result of DID resolution necessary to conduct Verifiable Credential verification.

MONTHLY VOLUME RANGE (Price per DID Resolved)
SKU 0–10,000 10,001+
Resolve DID
(did:key)
Contact us for pricing Contact us for volume pricing
Resolve DID
(did:ion, did:web)
Contact us for pricing Contact us for volume pricing