CaseDesk routes a customer-selected runtime or provider through OpenAI, Anthropic, and Gemini-compatible APIs. Any supported tool with a custom API base URL can use the governed connection.
Each CaseDesk account gets one base URL and API key. Paste the path that matches what your tool expects, and choose the target deployment with the request's model.
Select the provider account and region for the connected endpoint. Review that provider's data-processing controls and any external tools you enable for the workload.
Your provider bills compute directly. CaseDesk uses prepaid credit for active connections and measured routing services, so platform charges remain visible and controllable.
Connect approved tools to the same governed API surface. Your n8n workflows, Flowise agents, and Cursor IDE use the same CaseDesk credentials and policy boundary.
CaseDesk supports compatible customer-selected runtimes and providers. Change an approved underlying model or endpoint without rebuilding every client integration.
Connect a model endpoint in infrastructure your organisation controls. CaseDesk verifies the payer, endpoint health, and data boundary before enabling a trial route.
Your connection detail page shows the base URL and API key for all three formats. Copy the one that matches your tool - OpenAI, Anthropic, or Gemini.
In n8n this is the "Base URL" field on the OpenAI credential. In Flowise it is "Base Path". In Cursor it is "Override OpenAI Base URL". Every tool has a name for it - the value is your CaseDesk URL.
Your automations, agents, and IDE completions use the governed connection. The runtime continues to operate in the provider or infrastructure boundary your organisation approved.
Start with the Developer Sandbox, then connect an environment you control.
Try the Developer Sandbox