API reference

Routing

Every request to deepc Business API accepts a routing object that controls how the study is matched to a validated model and which backend provider fulfils it. Defaults are safe — the routing object only narrows behaviour.

The routing object

Add a routing object alongside the study payload. Every field is optional. Anything you omit falls back to the model's defaults configured for your tenant.

json
{
  "model": "milvue.fracture.v1",
  "routing": {
    "order": ["milvue", "azmed"],
    "allow_fallbacks": true,
    "region": "eu",
    "data_collection": "deny",
    "zdr": true,
    "require_regulatory": ["CE-IIa"],
    "max_latency_ms": 8000
  },
  "study": { /* … */ }
}

Fields

Field	Type	Behaviour
order	string[]	Preferred provider slugs in order. First reachable wins.
allow_fallbacks	boolean	Fall back to other providers if the preferred one is unavailable. Default true.
region	"eu" \| "us"	Pin execution to a hosting region. Inference runs never leave that region.
data_collection	"allow" \| "deny"	Reject providers that retain input data. Default "deny".
zdr	boolean	Route only to Zero Data Retention providers.
require_regulatory	string[]	Require a regulatory mark (e.g. "CE-IIa", "FDA-510k"). Non-compliant providers are skipped.
max_latency_ms	number	Reject providers whose p95 latency exceeds this budget.

Provider order & fallbacks

Without an order, deepc routes to the best-performing validated provider for the model (uptime + latency + cost). Set order to pin a preference; set allow_fallbacks: false to fail closed if the preferred provider is degraded.

json
"routing": { "order": ["milvue"], "allow_fallbacks": false }

Region pinning & data residency

region ensures the study, the inference and the audit record stay in one hosting region. The router will only consider provider endpoints that physically run in that region. EU and US are generally available; see hosting regions for compliance posture and roadmap.

Data-policy & Zero Data Retention

data_collection: "deny" is the default and excludes any provider whose terms permit retention of input data for training or analytics. zdr: true further restricts routing to providers contractually bound to a Zero Data Retention policy.

Regulatory enforcement

require_regulatory hard-filters providers by mark. Use this when a hospital contract or local regulator requires a specific clearance. Supported values today: CE-IIa, CE-IIb, FDA-510k, UKCA, CADt, CADe, CADx.

Response — routing receipt

Every response includes a routing block describing what actually ran. This is what your audit log captures.

json
{
  "status": "completed",
  "routing": {
    "model_version": "milvue.fracture.v1@2026.05",
    "routed_provider": "milvue",
    "routed_region": "eu",
    "regulatory": ["CE-IIa", "FDA-510k"],
    "zdr": true,
    "attempted": ["milvue"],
    "decision_ms": 12
  },
  "findings": [ /* … */ ]
}

Errors

If no provider satisfies the routing constraints, the request fails with 409 NO_ROUTE and a structured reason field listing which constraints excluded each candidate. See errors.