Sustema

D06

Understand credits and limits

Candidate documentation for reading and synthetic examples. Account creation, live API access, SDKs, collections and MCP are not available here. A released service profile and matching integration instructions are required before use.

Use the actual offer and service profile shown for your workspace. There are no confirmed numeric tariffs, free allowances or production limits in this draft.

Usable credits, reserved credits and consumed credits mean different things. A visible balance may differ from the amount currently spendable because of reservations, delegated ceilings, expiry or other applicable limits. Request count also differs from chargeable work: follow the operation’s published treatment and receipt instead of assuming every HTTP request costs one credit or every GET is free.

The receipt and operation status explain whether usage is not started, reserved, settled, released, uncertain or unchanged. An uncertain result is not proof of either a charge or a release. Retrieving permitted original status or receipt metadata does not start the matching work again.

Keep atomic units as their exact decimal strings and apply the offer’s scale for display. Do not convert large values through an imprecise floating-point number or treat units from different offers as interchangeable.

The signed-in tester, REST clients and MCP share the applicable authority and limits. Opening another tab, making concurrent calls or changing adapter does not create a fresh allowance. Free access also depends on the qualified service’s funding and operating bounds; it must not be described as unlimited.