Client onboarding
End-to-end — top up, create an API key, and run inference.
This guide walks through using the gateway as a client: add credit with a USDT transfer, create an API key (SIWE), then call the chat completion API.
What you need
- An Ethereum wallet for signing
- USDT on Ethereum (mainnet)
- The gateway base URL —
https://api.tk24.ai
End-to-end flow
| Step | What happens |
|---|---|
| 1. Top up | Send USDT on Ethereum to the collection wallet from GET /v1/config. The indexer credits the sending wallet, usually within a minute. |
| 2. API key | POST /v1/auth/keys with a SIWE message and signature. Response includes a secret API key (store it safely). |
| 3. Inference | POST /v1/chat/completions with Authorization: Bearer <api_key> and a chat-style JSON body. |
Model IDs are addressed directly by name (e.g. gemini-2.5-flash) — see the Model catalog for the full list.
For copy-paste code covering all three steps, see the Quickstart.
SIWE message alignment
The SIWE message must match what the server verifies:
- domain — hostname of the gateway (e.g.
api.tk24.ai) - uri — the auth endpoint (e.g.
https://api.tk24.ai/v1/auth/keys) - chainId — must match the gateway's chain
If key creation fails with a 4xx, confirm you're using the same public HTTPS host the gateway presents.