Provisioning decisions

Which credential belongs in the service?

Use a Model API key for model inference and a Partner key for provisioning. A single application may hold both, but it should keep them in separate secret-store entries and send each only to its intended origin. In Business, Partner access is company-owner authority, not project-developer authority.

Does moving a key move money?

No. Keys and projects apply budget and routing context; the company wallet remains the billing source. Moving a key does not create a sub-wallet, transfer a balance or rewrite historical usage records.

Why does usage differ from lifetime spend?

usage can be reset and may be valued using reference prices and an extra multiplier. total_spent records actual historical charges. Clear usage only when intentionally opening a new budget window; it is not a refund operation.

A mutation timed out. Should I issue a new one?

Retry the same logical mutation with its original idempotency key and unchanged body. A fresh key represents a new operation and can duplicate the intended effect. Idempotency retention is seven days; keep your own durable operation-to-key association.

Where is the completion result?

For native async inference, request it by public request ID from /api/v1/requests/REQUEST_PUBLIC_ID, using the matching owner's Partner token. Results are retained for 24 hours. Signed callbacks offer a delivery path but still require application-side deduplication and reconciliation.

How should history be reconciled?

Use request history for recent per-key detail and immutable pricing snapshots. Follow the reported retention window. Balance transactions provide the long-lived wallet journal; minute-aggregated API debits are not one transaction per individual request. Do not reconstruct old financial history from today's model catalog.

How do shared project credentials affect employees?

Playground authorizes the employee currently signed in, even when the selected project key was created by someone else. This is a short-lived browser delegation, not disclosure of an owner-level reusable token. Server integrations should still use intentionally assigned long-lived credentials.

Dedicated Images results

A company owner’s Partner provisioning authority does not automatically disclose an employee’s Images files. Dedicated image operations are read on the inference host with their original authorized actor/project key and current group scope, not via the Partner native-async result endpoint.