Home
Documentation
AI Gateway
Routes

Routes

Expose HTTP endpoints that forward requests to an LLM Provider.

The Routes module defines the HTTP endpoints exposed by AI Gateway. These endpoints receive requests from your applications and forward them to an associated LLM Provider. Each route maps a public path to a registered provider and a specific HTTP method. You can optionally override the provider endpoint, configure a timeout, and require scopes in the access token.

NOTE
To create a route, you must have at least one registered LLM Provider. Policies are applied per route. A route without a policy processes requests without guardrails, rate limiting, or prompt enrichment.

Quick links

Learn how to:

Filter and list routes
Create a route
Edit a route
Delete a route
Review the form fields

Listing

The Routes page lists registered routes with pagination. You can filter by:

LLM Provider (optional): identifies the LLM Provider associated with the route.
HTTP method (optional): route HTTP method. Values: All methods, GET, POST, PUT, PATCH, DELETE.
Exposed endpoint (optional): text search by exposed path.

Use Search to apply the filter and Clear to reset it.

Columns shown in the table:

Method: route HTTP method.
Exposed Endpoint: public path exposed by the gateway.
LLM Provider: summary of the linked LLM Provider, displayed as a list of tags with one entry per provider configuration, in the format Provider / Model / Pn (for example, OpenAI / gpt-4o / P1). Shows No LLM provider. when empty.
Timeout (s): timeout in seconds for the provider call (shows - when not configured).
Scopes: list of associated scopes, resolved to the name registered in Scopes. Shows No scopes assigned. when empty.
Created At: creation date and time in your time zone.
Actions: Edit and Delete icons for each row.

Create Route

Step 1

On the Routes page, click Create Route.

Step 2

Fill in the Create Route form fields (see Form fields). The LLM Provider field is a searchable select. Type part of the identifier to filter the list.

Step 3

Click Save to confirm the registration. To discard the operation, click Cancel.

Edit Route

In the Actions column of the row you want, click the Edit icon. The Update Route form opens with the current data. Change the required fields and click Save.

Delete Route

In the Actions column of the row you want, click the Delete icon. Confirm the operation in the "Do you want to delete route [routeId]?" dialog.

IMPORTANT
Deletion is permanent and cannot be undone. Policies associated with the route also become orphaned. Review and remove dependent policies before deleting the route.

Form fields

The table below covers all fields in the creation and edit forms.

Field	Type	Required	Rules
LLM Provider	Searchable select	Yes	Lists registered LLM Providers.
HTTP method	Select (enum)	Yes	Values: GET, POST, PUT, PATCH, DELETE.
Exposed endpoint	Text	Yes	Minimum 1 character. Public path exposed by the gateway (for example, `/v1/chat/completions`).
Provider endpoint	Text	No	When provided, overrides the default endpoint of the associated provider. Minimum 1 character.
Provider timeout (seconds)	Integer	No	When provided, must be a positive integer.
Scopes	Multi-select	No	List of scope IDs from the Scopes catalog required in the request access token. Select zero or more scopes. An empty list means any authenticated token can access the route.

TIP
An empty Scopes list means any authenticated token can access the route. To restrict access, register the relevant scopes in Scopes, select one or more here, and make sure the presented token contains those scope IDs.

How happy are you with this page?

API Keys

Policies