Solidway v0.1.0 is released under AGPL-3.0; source and releases are on GitHub. This documentation is being rewritten against the release — pages outside Quick start and Reference still describe planned behaviour. The current reference lives in docs/getting-started.md and docs/architecture.md in the repository.

Your first request

Create a route, add provider credentials, issue an API key, and call the gateway.

Open the bootstrap URL from the previous page, set the admin password, and the console opens. Everything below happens in the console — there is no configuration file.

1. Create a route

A route is the entry point your scripts talk to. Give it a name (for example prod) and, optionally, a description.

2. Add provider credentials

Inside the route, add a provider credential: pick a preset (OpenAI, Anthropic, Gemini, …), paste the upstream key, and adjust the inbound formats if needed. Saving fetches the model list from the upstream. Add more credentials to the same route to build a pool — the gateway selects between them and fails over before the first byte.

3. Create an API key

On API keys, create a key bound to the route. The plaintext is shown once; copy it before closing the dialog.

4. Call it

The gateway speaks the dialect of the provider family you configured:

curl http://127.0.0.1:6565/v1/chat/completions \
  -H "Authorization: Bearer <YOUR_API_KEY>" \
  -H "Content-Type: application/json" \
  -d '{"model":"<MODEL>","messages":[{"role":"user","content":"Hello"}]}'

The console shows ready-to-copy snippets for curl, the OpenAI/Anthropic SDKs and common terminal agents on the route page under Examples & agent setup.

Where to go next

Usage — requests, tokens and latency per route, key, provider and model.
Incidents — provider failures with reason, duration and manual restore for retired credentials.
System — bind address, TLS, cooldown durations, alert webhook, session lifetime.