Skip to main content
SCX.ai provides an OpenAI-compatible chat completions API for open-source models. Use Custom Endpoints in the AI Gateway to register SCX.ai once, keep the SCX.ai API key on the AI Gateway, and let your applications call models through a single TrueFoundry API key with access control and tracing.

Prerequisites

1

Create an SCX.ai account

Sign up at platform.scx.ai if you do not already have an account.
2

Generate an SCX.ai API key

In the SCX.ai platform, create an API key.Store the key securely. You will paste it into the AI Gateway’s Custom Headers configuration — not in client application code.
3

Get your TrueFoundry API key and gateway URL

You need a TrueFoundry API key (TFY_API_KEY) and your gateway base URL to call models through the AI Gateway. See Gateway base URL and Authentication.

Adding models

Add SCX.ai to the AI Gateway using Custom Endpoints.
1

Create a Custom Endpoint model account

In the TrueFoundry dashboard, go to AI Gateway → Models → Custom Endpoints and click Add Custom Endpoint.In Configure Account, set:
  • Name (Account Name): any unique label for this provider (for example, scx) — this is your model account name and appears as the first path segment in every request URL ({providerAccountName})
  • Endpoint Type: None
  • Header Auth: keep disabled
2

Add an SCX.ai endpoint

On the Endpoints step, add an integration and configure:
  • Display Name: any unique label for this endpoint (for example, inference) — this is your custom endpoint display name and appears as the second path segment in every request URL ({endpointName})
  • Base URL: https://api.scx.ai
Enable Custom Headers and add:
  • Authorization: Bearer <SCX_API_KEY>
Keep Header Auth and TLS Settings disabled unless your deployment requires them.
Custom Endpoint form for SCX.ai with Display Name inference, Base URL https://api.scx.ai, and an Authorization custom header

Endpoint settings — Base URL and upstream headers

The Authorization header here is sent from the AI Gateway to SCX.ai. Your application should only send the TrueFoundry API key to the AI Gateway.
You can click + Add Custom Endpoint to register multiple endpoints under the same account (for example, inference, vision, or fast-inference). Each gets its own Display Name in the URL, but they can all point to the same SCX.ai Base URL and headers. Which SCX.ai model runs is chosen in the request body model field — not by the display name.
3

Set access control and save

On the Access Control step, choose who can manage and use this model account, then Save.
  • Manager: users/teams who can edit or delete the custom endpoint
  • User: users/teams who can call the endpoint (for example, everyone)

Inference

Once saved, call SCX.ai through the AI Gateway’s proxy-api path. URL shape and path rules are documented under Custom Endpoints.

How the request URL is built

The AI Gateway URL has two values you configure in the dashboard — they are not SCX.ai model IDs: Full URL pattern:
With the example configuration above:
The AI Gateway forwards the request to:

Choosing an SCX.ai model

SCX.ai hosts many models. You do not need a separate custom endpoint per model — set the model field in the JSON request body to whichever SCX.ai model ID you want to run (for example, Meta-Llama-3.3-70B-Instruct). If you add multiple custom endpoints under the same account (different Display Name values), use the matching {endpointName} in the URL; each endpoint can still call any SCX.ai model via the request body.
Replace scx and inference in the URL with your own Account Name and Display Name if you used different values during setup.

Supported APIs

Before you start: Replace {GATEWAY_BASE_URL} with your gateway base URL (how to find it) and set TFY_API_KEY to your TrueFoundry API key.

Request headers (client → gateway)

Python (requests)

cURL

OpenAI Python SDK

Because SCX.ai is OpenAI-compatible, you can point the OpenAI SDK at the AI Gateway proxy path instead of SCX.ai directly:
Support scope: Custom Endpoints proxy requests transparently to SCX.ai. For gateway limitations on Custom Endpoints (HTTPS, streaming, and so on), see Custom Endpoints.