Loading documentation…
Loading documentation…
Understand the public usage and credit boundaries without exposing account state in Docs.
The Developer Portal is public and anonymous. It does not load private usage, billing, key, or credit data.
Use the SteamCall Dashboard for account-specific usage and credit information. Public documentation explains concepts and contract behavior only.
Treat documented rate and credit outcomes as explicit application states. Do not assume a successful request guarantees future capacity.
Successful metered responses include request-level product, charge, remaining-credit, and rate-limit metadata. Use the exact schema in the API Reference; do not calculate authoritative account state from a local request counter.
Record the request ID and product code when your application needs audit evidence. Do not log API keys or entire payloads merely to investigate usage. Account-wide balance and usage views belong in the Dashboard.
Stop automated retries when a documented credit outcome occurs. Surface an account action to an authorized operator and keep unrelated public users away from private billing details.