Please refer to our Pricing - Credits page for an explanation of credits. An excerpt:
When you or others work with your ShapeDiver account, credits are consumed for actions like computing the solution of a Grasshopper model for a set of parameters, generating a file export, or downloading an AR scene.
Billing of the Geometry Backend API usage is based on sessions. There are two types of sessions that we bill for differently:
-
Embedded sessions (sessions created using a ticket for embedding)
-
Use case: Applications that access the Geometry Backend API from web browsers, like the Viewer or when using App Builder. This typically means that API actions are somehow triggered by a human being.
-
Please refer to the explanation of credit usage of embedded sessions.
-
-
Backend sessions (sessions created using a ticket for backend access)
-
Use case: Applications that access the Geometry Backend API from a backend application (not from a web browser), like E-Commerce or ERP systems. This might include batch processing.
-