#
Model Service Integrations
Step-by-step guides for connecting Phoeniqs AI Model Service to the applications and platforms you already use.
The Model Service exposes an OpenAI-compatible API on Swiss sovereign infrastructure. Because many tools, frameworks, and client libraries already speak that API, you can often add Phoeniqs models to an existing stack by changing the base URL and API key, without rebuilding your application from scratch.
#
Why integrate with existing applications?
Teams integrate Phoeniqs MaaS into existing software when they want sovereign AI capabilities inside workflows they already rely on, rather than starting over in a new product.
Common reasons include:
- Keep your current tools: Add LLM features to internal apps, chatbots, automation platforms, or developer workflows without replacing the software your teams already use.
- Meet sovereignty and compliance requirements: Route inference through Phoeniqs-hosted models on Swiss infrastructure when data residency, guardrails, or governance policies matter.
- Reduce migration effort: OpenAI-compatible clients and SDKs let you point existing code at Phoeniqs by updating configuration instead of rewriting integrations.
- Standardize on one model provider: Use a single API key and billing model across multiple applications, from prototypes to production services.
- Control cost and usage: Consume models through your Phoeniqs subscription and monitor token usage across every connected application.
#
Integration guides
Integrate Phoeniqs MaaS with OpenCode: connect OpenCode to Phoeniqs models via opencode.json.
integrate-maas-with-opencode/
Integrate Phoeniqs MaaS with Cursor: add custom models and test in Cursor.
integrate-maas-with-cursor/
Getting started
If you have not set up API access yet, start with Model Service Guides for inference basics, API keys, and sample calls.
#
Related links
Sample API calls: ready-to-run cURL examples for every endpoint.
../model-service-guides/sample-api-calls/