Guide: review billing before adding credit

Use the product’s real billing flow for an account change.

Practical procedure

1. Open the authenticated GoCux billing surface and review the account, plan and current payment state.
2. Inspect the actual purchase or plan-change offer and amount before confirming any money action.
3. After the authorized transaction, wait for the product’s verified billing state and reread credits rather than assuming a browser success redirect grants access.

Call the supported chat contract

Normal web chat and the customer CLI use GoCux Gateway. Provider routing stays inside the service. The model catalog advertises the GoCux route alias gocux-deep, not an upstream provider identity. A compatible chat client supplies its message history and an explicit data-classification header; GoCux applies identity, policy, paid admission and credit reservation before a provider request.

Contract example

Developer examples below describe routes on an authorized, configured GoCux control-plane base URL. They are request shapes or operation references, not claims that a particular public hostname exposes the API. Use the workspace for the corresponding human workflow; availability and permissions depend on the actual deployment.

Operation reference for this workflow

GET /credits

Inspect the result

Read the returned choices and handle an error response before showing a completed answer. When streaming, consume complete events and distinguish connection closure from a successful terminal result. GoCux route aliases are product contracts; do not let a client-selected upstream model bypass server routing or display provider identities as customer configuration.

What to keep explicit

There is no generic add-to-balance API established here. A payment-verifying state must remain visible until the actual entitlement update is confirmed.

Handle incomplete and refused work

Declare X-GoCux-Data-Classification exactly once. A data_classification field in the chat-completions body is rejected rather than used as the declaration. Missing classification is unclassified and can be refused by policy. An optional Idempotency-Key helps identify an operation, but a paid replay can return 409 without replaying the original response or contacting the provider again.

Continue with related guides

• Use the GoCux chat-completions interface
• Understand chat compatibility boundaries
• Handle refusals and unavailable states
• Choose a GoCux workflow