Skip to main content
AvraAPI uses product-specific billing models. Provider usage and Universal Payment Gateway capacity are deliberately separate.

​
Provider services

Microservice providers can consume your project’s available AvraAPI credits according to the active service pricing. Before releasing an integration, review the current pricing surface and confirm the cost behavior of the provider you intend to call.
Development requests are real requests. They are not mocked and can consume credits or trigger an upstream provider action, such as sending an SMS or generating an artifact.

​
UPG commercial model

UPG is a Workspace-licensed product. Purchasing or claiming a Workspace UPG plan provides capacity; it does not automatically enable a project.
1

Workspace plan or entitlement

Provides the underlying UPG authorization.
2

Available project capacity

The Workspace gains available slots.
3

Explicit project-slot attachment

A slot is assigned to a specific project.
4

Project gateway configuration

The project configures its Gateway Vault credentials.
5

New payment checkout

The project can now successfully create new UPG checkout sessions.
The Workspace plan governs included capacity, permitted gateway access, and any extra project slots. Project gateway credentials remain encrypted and project-specific.

​
Pricing changes and invoices

Quotes are calculated by the server from the current pricing version. Browser-supplied prices, discounts, capacity, and credits are never authoritative. A completed purchase keeps an immutable pricing snapshot for billing and invoice history. For the detailed commercial and capacity model, see Plans & capacity.
Last modified on October 1, 2026