diff --git a/assets/provider-monitor-schema-v2.openapi.json b/assets/provider-monitor-schema-v2.openapi.json index c1f64575..fb57e419 100644 --- a/assets/provider-monitor-schema-v2.openapi.json +++ b/assets/provider-monitor-schema-v2.openapi.json @@ -136,9 +136,6 @@ "deployment_region": { "type": "string", "minLength": 1 - }, - "compliance": { - "$ref": "#/components/schemas/Compliance" } }, "required": [ @@ -2289,20 +2286,6 @@ "country_code" ], "additionalProperties": false - }, - "Compliance": { - "type": "object", - "properties": { - "zdr": { - "type": "boolean" - }, - "hipaa": { - "type": "boolean" - } - }, - "additionalProperties": { - "type": "boolean" - } } } } diff --git a/guides/community/for-providers.mdx b/guides/community/for-providers.mdx index d485bd35..f4cb13a7 100644 --- a/guides/community/for-providers.mdx +++ b/guides/community/for-providers.mdx @@ -133,8 +133,7 @@ Below is an example of the response format: "slug": "anthropic/claude-sonnet-4" }, "datacenters": [{ "country_code": "US", "region": "us-east-1" }], - "deployment_region": "US", - "compliance": { "zdr": true, "hipaa": false } + "deployment_region": "US" } ] } @@ -681,9 +680,9 @@ Each map uses the same [capability descriptor](#capability-descriptors) grammar, } ``` -### 6. Datacenters, deployment region, and compliance +### 6. Datacenters and deployment region -Declare where each endpoint physically serves from and its data-handling posture: +Declare where each endpoint physically serves from: ```json lines { @@ -691,19 +690,13 @@ Declare where each endpoint physically serves from and its data-handling posture { "country_code": "US", "region": "us-east-1" }, { "country_code": "DE" } ], - "deployment_region": "US", - "compliance": { - "zdr": true, - "hipaa": false - } + "deployment_region": "US" } ``` - `datacenters[].country_code`: ISO 3166-1 alpha-2 country code. - `datacenters[].region`: provider-scoped region identifier (e.g. `us-east-1`). - `deployment_region`: optional provider-scoped label for the model deployment's region or scope (e.g. `US`, `global`). Use it when the same underlying model is deployed to more than one region under distinct model `id`s, so each document declares which regional deployment it describes. It complements `datacenters`, which lists the physical serving locations. This is a display-only label today: OpenRouter does not route or bill on it, so use consistent values across your documents and coordinate the vocabulary with us before publishing. -- `compliance.zdr`, zero data retention: no prompt retention and no training on prompts. -- `compliance.hipaa`: HIPAA compliance. Additional boolean certification flags (SOC 2, GDPR, FedRAMP, ...) may be added over time. ### 7. Operational fields