Gatepx uses three public hosts with different jobs. Choosing the right host keeps application configuration clear and makes failures easier to investigate. The inference base URL is https://api.gatepx.ai/v1.
gatepx.ai: your account and dashboard
Use gatepx.ai to sign in, create API keys, inspect usage, manage your account, and review the public pricing reference. These are browser-facing account and product tasks. Your website session is separate from the API key that an application sends with an inference request.
api.gatepx.ai: application requests
Send supported model requests to the API host. For an OpenAI-compatible SDK, set its base URL to https://api.gatepx.ai/v1. A chat request then goes to /chat/completions relative to that base URL.
import OpenAI from "openai";
const client = new OpenAI({
baseURL: "https://api.gatepx.ai/v1",
apiKey: process.env.GATEPX_API_KEY,
});The API host is not the destination for dashboard navigation or browser sign-in. Send the Gatepx API key in the Authorization header over HTTPS; do not put it in the address or query string. Keep the client configuration on your server.
docs.gatepx.ai: the integration reference
Use docs.gatepx.ai for endpoint examples, model discovery, streaming, request errors, and SDK configuration. Blog articles explain a workflow; the documentation provides the current reference details.
Check an existing integration
- Inspect the actual base URL used by the deployed application, including environment overrides and trailing paths. Avoid accidentally constructing
/v1/v1/chat/completions. - Confirm that the credential is a Gatepx API key. A provider API key or website password belongs to a different system.
- Choose an enabled model ID, make a small request, and confirm that the returned response matches what your application expects.
- Check application and dashboard usage records before increasing traffic.
Moving to the API host is a configuration change, but it still deserves an end-to-end test. If a request fails, record the destination host, HTTP status, and request ID without recording secrets. The first-request guide gives a minimal check, and the SDK migration guide covers the compatibility checks for an existing application.