Provider-direct by architecture
Your prompt traffic does not pass through Solwyn.
The SDK runs in your application. Supported model calls continue directly to the provider you selected. Solwyn's control plane receives the operational metadata needed for budgets, attribution, and alerts — not prompt or response content.
Solwyn checks the project budget in-process before every supported model call. Under budget, the call is sent directly to the provider. When the limit is reached, the SDK raises BudgetExceededError and the call is not sent. Prompt traffic always goes directly to the model provider; only usage metadata is sent asynchronously to the Solwyn dashboard.
The data inventory.
- Model identifier
- Token counts
- Latency
- Status / error category
- Project identifier
- Custom tags you attach
- Prompt content
- Response content
- System messages
- Function calls
- Conversation history
- Tool arguments or payloads
- Your provider API keys
Your provider API keys are configured in your own environment, alongside the SDK. Solwyn never holds them. Cost is calculated inside Solwyn's control plane from the token counts — the SDK never computes or transmits a price.