BYOK proxy
Keep the SDK. Change where the completion goes.
The production chat route is POST https://api.maskio.io/v1/proxy/chat/completions. Maskio tokenizes messages in RAM, calls the provider with the key stored for that workspace, and restores tokens in the reply.
What you configure
Create an API key in the Maskio workspace with the proxy:llm scope. Store the provider key in that workspace. Send the workspace and session headers documented in the BYOK guide. The browser extension and the remote MCP server are separate entry points for people who are not calling the HTTP API.
What this is not
It is not a silent base_url of https://api.maskio.io/v1 that magically matches every OpenAI SDK default. The path is /v1/proxy/chat/completions, and the workspace headers are required so the right dictionary is used.
Questions
Do you mark up model tokens?+–
No. You pay the provider with your own key. Maskio bills the privacy plan.
Are prompts stored?+–
The token map is RAM with a TTL. Logs keep counts and latency, not the message text.
See it on a payload you control.
The sandbox and the free tools run before you create an account.