MAINCHAIN DOCUMENTATION

MainChain API and token model

Use MainChain programmatically through a complete PaaS subscription or an API-only plan without the GUI.

PaaS API access

API access is included in the MainChain PaaS licence alongside the GUI and platform services.

API-only access

API-only plans provide programmable access without the MainChain GUI. Each plan includes a defined token allowance.

Consumption model

A standard workflow uses 10 tokens. Monitor the allowance against the selected plan and expected transaction volume.

Authentication and environments

Use the credentials issued for the target environment. Keep development and production credentials separate and never embed them in client-side applications.

Events and integration

Integrations can coordinate asset registration, rights, workflow status, handover and audit events. The authenticated reference defines the available operations for the licensed environment.

Integration lifecycle

1. Authenticate the licensed environment2. Register the asset and authorised metadata3. Define the permitted production workflow4. Subscribe to status and audit events5. Reconcile token consumption and execution evidence

{
  "environment": "customer-production",
  "access": "paas-included | api-only",
  "workflow": {
    "asset": "customer-reference",
    "rights": "authorised-scope",
    "quantity": 1,
    "edge_server_required": true
  }
}

This illustrates the integration model without exposing environment-specific endpoints or credentials. The authenticated API reference supplied with the licence defines the available operations and payloads.