October 2026FeatureSDK
Allowances counted across every runtime
- An allowance is counted by Monaiq across every runtime of a seat. Each runtime reserves a small share of the period's uses ahead, spends it locally and hands back what it did not use when it stops, so a use never waits on Monaiq and a scaled-out app never over-counts.
- A use the period cannot cover is refused in both SDKs with the date the period resets, and nothing is counted for it. Checking access never counts as a use.
- Seat reads show the period's figures: uses recorded, uses reserved by running instances, and what is left.
- Your app declares the seller and product it belongs to, and a seat of any other seller or product is refused.
- Adding seats and issuing a license code are safe to repeat: the same request answers the same seats or the same code, never a duplicate.
- A seller's invoice is billed on the seller's own Stripe account, or held until it can be; it never bills elsewhere.
- In the workbench, a feature's name and description can be edited in place, the products list shows how many offerings each product has, and the invoice list states the issue-date window it searched.
- Over MCP, every catalog create mints its own id, and the account API key is shown to owners only.