GetAPI.ONE

Understand GetAPI.ONE pricing and usage

Identify the pricing mode, endpoint, unit, and group before use; read current values from Live pricing; then reconcile an actual request against account records.

Before sending a request

Open the model catalog and select the exact model and endpoint your client will use.
Open Live pricing immediately before use and read the current pricing mode, unit, and any group-specific information.
Check account balance or package status, plus the selected key’s quota and expiry.
Start with a bounded test request whose cost you are prepared to accept.

Recognize the pricing mode

Mode	What to inspect
Token based	Input/output or other token categories, the displayed unit, endpoint, model, and group. Do not assume all token types have one rate.
Per call / fixed unit	What one billable unit represents, plus parameters such as size, duration, quality, or count when shown.
Dynamic / expression based	The current UI explanation, request parameters that influence the result, and the resulting account log. Do not copy or recalculate the expression in a static guide.

Endpoint type matters because the same model identity may expose different operations or not support the protocol your client expects. Unit labels also matter: token, request, image, second, or another unit are not interchangeable.

Groups, keys, and limits

A key’s group can affect which models it can access and which displayed group information applies.
A key quota and expiry can stop a request even when the account still has balance.
Account balance, packages, key scope, rate limits, and model availability are separate checks; one passing check does not prove the others.

Reconcile an actual request

Record the request timestamp, exact model, endpoint, key name (not secret), and request identifier if the client provides one.
Open the console usage/request log and locate the corresponding record.
Compare the recorded model, endpoint, usage categories, group, status, and deduction information with the current pricing display.
If values differ or are unclear, preserve the unmodified record and current pricing view with secrets masked, then contact the channel appropriate to a billing question.

When a request is blocked

Symptom	Check in order
Insufficient quota / balance	Key quota and expiry, account balance/package, group access, then current model pricing.
Rate limited	Read the response details, reduce concurrency, respect any retry guidance, and avoid unbounded retries.
Unexpected deduction	Match one request by timestamp/id, verify model/endpoint/group/parameters, save the log and current pricing display, then escalate without sharing the key.