Skip to content
CloudSitus

Capability · Embeddings

Embeddings in one shared vector space.

A single 4096-dimension embedding model wherever embeddings run (CH and EU today) — for general and PHI traffic alike — so your vectors stay comparable across jurisdictions.

Get startedRead the docs

POST /v1/embeddings

What you get

Built for regulated workloads

Embeddings resolve to the canonical qwen3-embedding-8b (4096-d) in production in CH (Infomaniak) and EU (Scaleway), for both general and PHI traffic. Because the model is the same in both regions, a vector embedded in Zurich is directly comparable to one embedded in Paris, so you can build one index that spans jurisdictions. US and other regions return no_route until the staged Fireworks (US) and Azure/Bedrock (ROW) rows — all in the same 4096-d space — are enabled.

01 · Portable

Cross-region comparable

The same 4096-d space in every region that serves embeddings means a query embedded in one region matches documents embedded in another. The staged regions use the same space, so adding one later needs no re-embedding.

02 · Same-space failover

Dimension-safe routing

Failover is filtered to a single vector dimension per request — a request only ever fails over within the same 4096-d Qwen space, never to a different-dimension model that would corrupt your index.

03 · PHI

PHI embeddings, resident

PHI embeddings run on Infomaniak (CH) and Scaleway (EU) under reviewed DPAs. US PHI embeddings are not available — US embeddings return no_route. A Fireworks row (same 4096-d space) is staged, pending BAA confirmation.

04 · Options

Pin a different space

Need a lighter or multilingual model? bge-multilingual-gemma2 (3584-d) and all-MiniLM-L12-v2 (384-d) are pin-only in CH. The same-space filter keeps any one request to a single dimension.

Availability & pricing

Where it runs, what it costs

Every route is pinned to a region, PHI stays on resident hosts, and the PHI gate is enforced per call. Prices mirror the live /v1/pricing rate card.

RegionProviderModelTierPrice
CHInfomaniakqwen3-embedding-8b · 4096-dPHI$0.14 / 1M
EUScalewayqwen3-embedding-8b · 4096-dPHI$0.19 / 1M
USFireworksqwen3-embedding-8b · 4096-dStaged$0.17 / 1M
CHInfomaniakbge-multilingual-gemma2 · 3584-dPHI$0.13 / 1M
CHInfomaniakall-MiniLM-L12-v2 · 384-dPHIFree

Per 1M input tokens. The canonical qwen3-embedding-8b is the default wherever embeddings run (CH and EU); other regions return no_route. bge / minilm are pin-only CH options in their own dimension.

Try it

A real call, end to end

Embed a batch in the EU. The response is a standard OpenAI embedding object; the headers confirm the route and space.

Residency & vectors

  • CH embeddings stay on Infomaniak via the Swiss /2/ AI surface.
  • EU embeddings run on Scaleway, in the same 4096-d space as CH.
  • US and other regions return no_route until the staged Fireworks (US) and Azure/Bedrock (ROW) rows are enabled.
  • Build one cross-jurisdiction index; the shared space keeps similarity scores meaningful.
curl
curl https://cloudsitus.com/api/v1/embeddings \
  -H "Authorization: Bearer $PHI_API_KEY" \
  -H "X-Region: EU" \
  -H "X-PHI: true" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "qwen3-embedding-8b",
    "input": ["patient presents with...", "follow-up in two weeks"]
  }'
response
x-phi-routed: scaleway-qwen3-embedding-8b/EU/phi
x-phi-tier: phi
x-phi-usage: verified
# data[].embedding -> 4096 floats

FAQ

Common questions

Search & RAG over PHIChat & reasoningAPI reference
Why one embedding model instead of the best per region?
Vector comparability. If different regions used different models, vectors would live in incompatible spaces and you could not search across them. The single 4096-d canonical keeps one index valid in every region that serves embeddings.
Can I mix embedding models in the same index?
No — vectors are only comparable within one model/dimension. The gateway enforces this: failover stays in the request’s vector dimension. Pin bge or minilm explicitly only if you maintain a separate index for them.
Are PHI embeddings available in the US?
Not yet in production. The Fireworks US PHI route is staged on the same 4096-d space and enables once its HIPAA BAA and serverless coverage are confirmed. US embeddings today return no_route until that row is enabled.

Ready when you are

Put embeddings & search in production — without giving up your data.

Spin up a key in minutes. The residency and PHI posture above arrives unchanged.

Get startedSee pricing

Prepaid credits from $10 · No subscription · No data retained