Your request format stays familiar: chat completions, bearer authentication and model ids. The main changes are the endpoint, key and the set of models exposed by the catalog.
Do not assume one service is cheaper for every workload. Compare the exact model and input/output pattern you use, include reliability and latency in the test, and keep a fallback if your application is critical.
For teams in regions with payment friction, checkout displays the methods currently available to that account. Availability of cards, local transfers or crypto depends on the configured payment rail and can change.