Guides

The documentation describes what each part of Salyro does. A guide works through one whole task instead — from the first step to a result you can check.

24 August 2026Debug a failed requestAn ordered path from "something failed" to "this is why" — the status, the error body, the request id, and the gateway's log.
24 August 2026Migrate an existing OpenAI integrationMoving production traffic onto Salyro is a configuration change — a base URL, a key and a model id — not a rewrite.
24 August 2026Send images with visionThe second modality Salyro supports — how an image goes into a request, which providers read it, and what it does to token counts.
24 August 2026Stream responsesShow text as it is generated instead of waiting for the whole answer — enabling streaming, consuming it server-side, and handling a client that leaves.
24 August 2026Get structured JSON outputAsk for output that conforms to a schema instead of extracting JSON from prose — and find out immediately when a model cannot do it.
24 August 2026Switch providers without changing your codeWith one interface in front of four providers, moving a request from OpenAI to Anthropic is a change of model id — and nothing else.
23 August 2026Attribute cost per feature or customerSplitting gateways along the boundary you want to measure, so “what did this feature cost us” has an answer.
23 August 2026Respond to a leaked API keyWhat to do in the first few minutes after a Salyro key reaches somewhere it should not have — and what you can establish afterwards.
23 August 2026Rotate a provider credential without downtimeThe order of operations that replaces a provider key on a gateway without a window where requests fail.
23 August 2026Separate your environments with gatewaysHow to give development, staging and production a gateway each, and what that separation actually buys you.