Private development. C.O.S. is not yet publicly available. These domains are accessible only during active development sessions. Public launch has not been announced.
API status fetching…
API version fetching…
Schema fetching…
Auth API keys · per-org
Rate limiting Phase 58-3 · pending
Fetched —
AI Governance · Private Development

C.O.S.
Governed AI.
Every decision traceable.

A model-agnostic compliance layer for AI deployments. Policy-versioned, governed by design, and auditable from first principle to last output.

What is C.O.S.? API documentation
ModelAgnostic
Policy versioningIndependent of API
StorePostgreSQL
AuthAPI key · per-org
APIREST · v1
StatusPrivate development
What is C.O.S.?

One acronym. Many truths.

C.O.S. is whatever your compliance infrastructure needs it to be. The name is intentionally broad — because the problem it solves is broad.

At its core: a governed, model-agnostic system that sits between your AI deployments and your regulatory obligations. It versions compliance logic independently of code, makes every decision replayable, and enforces policy consistency across jurisdictions, providers, and release cycles.

C O S
Compliance Operating System
Compliance Orchestration System
Contextual Operating System
Continuous Oversight System
Custodian of Standards
Coordinator of Systems
Coherent Operations Substrate
∴

Documentation-first

Every decision is governed, traceable, and preserved. No silent state changes.

⊗

Model-agnostic

Logical roles — not model names. Swap providers without touching compliance logic.

⊞

Policy-versioned

Compliance rule sets are independently versioned. Audit any decision against the policy active when it was made.

⊡

Multi-jurisdiction

Industry × jurisdiction × data classification. Rules derive from the intersection — not from hardcoded logic.

// Developer

REST API · v1

The C.O.S. API is available at cosprotocol.io/v1. API key authentication. Org-scoped. Full OpenAPI spec at docs.cosprotocol.io.

Quick start
# Liveness check (no auth required)
curl https://cosprotocol.io/v1/health

# Retrieve org profile
curl -H "Authorization: Bearer $COS_API_KEY" \
     https://cosprotocol.io/v1/organisations/{org_id}

# List API keys for org
curl -H "Authorization: Bearer $COS_API_KEY" \
     https://cosprotocol.io/v1/organisations/{org_id}/api-keys
Auth model
HeaderAuthorization: Bearer <key>
Key formatcos_live_<48 chars>
ScopePer-organisation
No-key response401 Unauthorized
API surface · v1
GET /v1/healthLiveness · public
GET /v1/versionVersion metadata · public
/v1/organisationsOrg management
/v1/…/api-keysKey provisioning
/v1/billing/…Billing summary
Full OpenAPI specification → docs.cosprotocol.io

Request API access

C.O.S. is in private development. Access is by invitation only. API keys are provisioned directly — no self-service portal yet.

To request access or discuss a pilot, contact: hello@cosprotocol.io