Gateways

Gateway Endpoints

Each Gateway contains one or more endpoints. An endpoint defines a path, the HTTP methods it accepts, its price, and whether it uses exact or wildcard matching.

Adding an endpoint

From your Gateway detail page, click Add Endpoint. You will configure:

Field	Description
Path	The URL path segment (e.g. /users or /search)
Methods	Allowed HTTP methods (GET, POST, PUT, DELETE, etc.)
Price	Cost per request in USD (e.g. 0.001)
Mode	Exact match or wildcard match

Path modes

Exact mode - The endpoint only matches the exact path. A request to /users matches, but /users/123 does not.

Wildcard mode - The endpoint matches the path and any sub-paths. A wildcard endpoint at /users matches /users, /users/123, and /users/123/posts.

Plain Text

Exact:    /api/search     → matches only /api/search
Wildcard: /api/resources  → matches /api/resources, /api/resources/42, etc.

Use wildcard mode for RESTful resource APIs where you want a single price for the entire resource tree. Use exact mode when different sub-paths need different pricing.

Allowed methods

Select one or more HTTP methods for each endpoint. Requests using a method not in the allowed list receive a 405 Method Not Allowed response. Common configurations:

Read-only - Allow only GET.

Full CRUD - Allow GET, POST, PUT, DELETE.

Write-only - Allow only POST.

Per-endpoint pricing

Each endpoint has its own price. This lets you charge differently for expensive operations versus cheap reads:

Plain Text

GET  /api/search    → $0.001
POST /api/generate  → $0.05
GET  /api/status    → $0.0001

Prices are specified in USD and settled on Tempo. The minimum price is 0.0001 (one-hundredth of a cent).

Overview Upstream Auth