Catalog and profile selection
Filter the public catalog or console catalog by name, maker, protocol and capabilities. One profile must satisfy all selected conditions. Details distinguish the catalog model ID, execution UUID and wire; keep them together in examples.
Pending prices and unavailable protocols mean the configuration cannot currently be tried, not that usage is free. Refreshing can change availability. Old visible data does not authorize execution. Missing channel observations do not mean the model lacks capabilities.
Details provide cURL, JavaScript/TypeScript, Python, Go and Rust examples. Python/Go/Rust are HTTP examples, not evidence of published Acosmi SDKs. If compatibility is disabled, only supported legacy HTTP endpoints are shown.
Memory-only credential and transparent execution
- Open the playground from an available configuration and check its model and protocol.
- Explicitly create or paste a personal PAYG key. It stays in current page memory, not URLs or persistent browser storage.
- Enter the prompt and output budget. For V2, obtain a quote for these parameters before explicitly running.
- Observe output and errors and keep original request identifiers.
- Inspect My requests, Usage, and Billing.
Reload, logout, account changes and credential updates clear sensitive inputs and prior output. Do not restore another account’s key or prompt. Clearing an input does not revoke a key; rotation does not erase past costs.
Original records and financial status
| Identifier / state | Meaning |
|---|---|
| Transport request ID | Correlates the HTTP request |
| Consumption request ID | Associates original execution and costs |
| Delivered / normal stream terminal | Output completed, not proof of settlement |
| Reserved / pending reconciliation | Financial confirmation remains; neither free nor independently additive |
| Settled / released / refunded | Separate original records; missing amounts remain unknown |
Components, observations and monthly budget
V2 separates input, output, cache reads and cache writes, in CNY and corresponding Credits. Applicable tiers and time windows follow the contract; a catalog reference is not a frozen request quote.
A console quote does not execute the model. Changes to prompt, budget or configuration require a matching quote. Changed prices or insufficient caps require another decision, never automatic increases. Programmatic calls use the effective version and explicit max_credits; CNY 1 is the string "1000000".
A monthly key budget applies to its existing budget scope; rotation does not reset it. Query uncertain budget changes using the original operation association instead of repeatedly creating changes. See billing.
Public performance observations come from qualified samples in a bounded window. Missing, insufficient and stale samples are not invented latency or success rates and do not replace availability checks.
Fulfilled continuation and deployment boundary
Keep the selected model/profile/wire through a recharge continuation. A payment redirect is not fulfillment. After confirmed fulfillment, return manually; do not restore a key/prompt or automatically execute.
A visible catalog, working frontend or copied example does not prove a model has been released. Execution still checks identity, permissions, prices and availability. Query unknown outcomes using the original request; see retries.