​
Internet direct routing

Internet direct routing bypasses our global API load balancer and directly routes your request to the machines where your deployment is running. This can save several tens or even hundreds of milliseconds of time-to-first-token (TTFT) latency.

To create a deployment using Internet direct routing:

$ firectl create deployment accounts/fireworks/models/llama-v3p1-8b-instruct \
    --direct-route-type INTERNET \
    --direct-route-api-keys <API_KEYS>

Name: accounts/my-account/deployments/abcd1234
...
Direct Route Handle: my-account-abcd1234.us-arizona-1.direct.fireworks.ai
Region: US_ARIZONA_1

If you have multiple API keys, use repeated fields, such as: --direct-route-api-keys=<API_KEY_1> --direct-route-api-keys=<API_KEY_2>. These keys can be any alpha-numeric string and are a distinct concept from the API keys provisioned via the Fireworks console. A key provisioned in the console but not specified the list here will not be allowed when querying the model via direct routing.

Take note of the Direct Route Handle to get the inference endpoint. This is what you will use access the deployment instead of the global https://api.fireworks.ai/inference/ endpoint. For example:

curl \
    --header 'Authorization: Bearer <FIREWORKS_API_KEY>' \
    --header 'Content-Type: application/json' \
    --data '{
        "model": "accounts/fireworks/models/llama-v3-8b-instruct",
        "prompt": "The sky is"
    }' \
    --url https://my-account-abcd1234.us-arizona-1.direct.fireworks.ai/v1/completions

​
Supported Regions for Direct Routing

Direct routing is currently supported in the following regions:

  • US_Iowa_1
  • US_Nevada_1
  • US_Virginia_1
  • US_Virginia_2
  • US_Arizona_1
  • US_Illinois_1
  • US_Illinois_2
  • EU_Frankfurt_1
  • EU_Paris_1
  • EU_Helsinki_1
  • AP_Tokyo_1

​
Private Service Connect (PSC)

Contact your Fireworks representative to set up GCP Private Service Connect to your deployment.

Contact your Fireworks representative to set up AWS PrivateLink to your deployment.