These pages describe the intended behaviour of the gateway. The open-source release and the enterprise edition are being split out; details will be updated when the first release ships.
First request
Bootstrap the process, add a provider in the console, forward one request.
Two steps: start the process with a three-entry configuration file, then add a provider in the console.
1. The configuration file
# solidway.toml
[server]
listen = "0.0.0.0:8080"
public_url = "https://gateway.example.com"
[console]
listen = "127.0.0.1:8081"
[state]
path = "/var/lib/solidway"
That is the whole file. It says where to listen, which domain is served, where the console is reachable, and where to keep state. Providers, keys and routing policy are added in the console, not here.
2. Start it
./solidway --config ./solidway.toml
3. Add a provider
Open the console, add a provider with its base URL and the routes it accepts, then add a credential to it. The console shows a fingerprint rather than the secret once saved.
4. Send a request
curl -sS https://gateway.example.com/anthropic/v1/messages \
-H 'content-type: application/json' \
-d '{
"model": "claude-sonnet-5-5",
"max_tokens": 64,
"messages": [{"role": "user", "content": "Say hello."}]
}'
The provider receives the body you sent, with the credential header added. The response is passed back as it arrived.
What to look at next
- Add a second credential and enable load balancing
- Add a fallback target and enable failover
- Turn on metrics to see what the gateway observed