TKAPI Gateway

Operations overview

Checking gatewayConnecting to TKAPI
——

Loading gateway data…

PRIVATE CONTROL PLANE

Connect to TKAPI

Use the administrator key configured for this gateway. It stays in this browser tab and is never written into the dashboard source.

Session-only access

ENCRYPTED CREDENTIAL

Configure provider

The key is encrypted before it is stored in SQLite. For security, an existing key can be replaced or removed but never revealed.

PROVIDER KEY POOLS

Manage keys

Free and paid keys stay in separate pools. Adding a pool replaces legacy key selection for this provider. Unknown billing keys cannot serve requests.

Add key

Choose Free only when the upstream account cannot charge for these models. Billing-enabled accounts belong in Paid even if they include an allowance.

CAPACITY FALLBACK

Provider quota

Enter the cap assigned by the provider. TKAPI uses local gateway usage to estimate remaining capacity when live provider headers are unavailable. Live reported quota always takes precedence.

CLIENT ACCESS

Create application

Define the application policy and usage guardrails. A new client key is shown once after creation.

Access policy
Allowed routes

Leave every route unchecked to allow all policy-compatible aliases.

Budgets 0 means unlimited

ONE-TIME CLIENT KEY

Copy this key now

TKAPI stores only a one-way hash. This key cannot be displayed again after this window is closed.

Store it in the consuming application's server-side secret manager. Never place it in browser code, a mobile bundle or source control.