Hosted or self-hosted

Sentisec runs between your agent and the model provider. Most teams use the hosted endpoint at api.sentisec.ch — nothing to install, your provider keys stay in your workspace. Teams with data-residency or network constraints run the same thing inside their own environment.

Hosted

Point your client at the workspace-scoped URL and you are done.

curl -X POST https://api.sentisec.ch/ws/<your-workspace-id>/v1/messages \
  -H "Authorization: Bearer $SENTISEC_API_KEY" \
  -H "anthropic-version: 2023-06-01" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "claude-sonnet-4",
    "max_tokens": 256,
    "messages": [{"role": "user", "content": "hello"}]
  }'

The call appears as a session in the dashboard within a second — that is your confirmation the route is live.

For coding agents, set the base URL your agent already reads and it runs unchanged:

# Anthropic-shaped agents: Claude Code, opencode
export ANTHROPIC_BASE_URL=https://api.sentisec.ch/ws/<your-workspace-id>

# OpenAI-shaped agents: Cursor, Codex, and most others
export OPENAI_BASE_URL=https://api.sentisec.ch/ws/<your-workspace-id>/v1

Per-agent detail in CLI agents. If you would rather not use an API key at all, subscription mode protects Claude Code and Codex using the subscription you already have.

Self-hosted

Run Sentisec inside your own VPC or on-premise when you need data residency, an air-gapped install, or single-tenant isolation. Everything above works identically — you point the same clients at your own hostname instead of api.sentisec.ch.

Deployment recipes, images, and operator runbooks are provided under NDA with your deployment.

Request enterprise access →

Which one do I want

Next

• cURL and raw HTTP — the request shapes in full.
• Providers — connect an upstream credential.
• Deployment — hosted, self-hosted, and in-VPC compared.