The section reference — from installation to fine tuning: how to set up models and count spending, how to connect programs and limit contractors, what gets into the log and analytics, how to hide secrets and route ordinary traffic through the same server, where the file-based setting lives and how to drive the product with a program. Start with the installation and the first steps, then open the section you need right now.
Docker Compose, PostgreSQL next to it, environment variables, first sign-in.
What the product consists of, who it fits, and where to start in five steps.
Your own key for every person: spending limits, allowed models, revocation.
Where and how to reach a model, and what a million “portions of text” (tokens) costs.
Where your traffic exits: an HTTP proxy, SOCKS5, a VPN, a Happ subscription or direct. A channel can also work as a proxy for contractors.
Three addresses, an access key instead of a vendor key, a connection check.
A program written for one vendor works with another vendor’s model.
Two prices for every request, spending limits and how they are counted.
What is visible about every request — and what the log does not contain.
Volume, latency, breakdown by models and keys, spending.
Keys and passwords go to the model under a conventional placeholder.
HTTP and SOCKS5 on one port, a port per channel, sign-in with a key.
Language and font size, sign-out, license information, report retention.
Connecting Xedant Agent, and what works without it.
A subfolder, a front proxy, where the data lives, what is lost without a volume.
Where the setting lives, how to edit it by hand and move it to another server.
The management key, self-documentation, and what a program can do.
Administrator sign-in, where secrets live, what to close before going online.
← Back to the Proxy Agent section home
