Familiar interfaces. Explicit boundaries.
Build with Cardean through documented APIs, SDKs and deployment paths. The developer experience makes policy and failure behaviour visible — not to hide important differences behind a universal abstraction.
Gateway developer preview opens in August 2026 Analytics and Identity developer access follow — Analytics in 2026, Identity in 2027
Point one AI workflow at a governed endpoint.
The first quickstart takes a developer from an existing OpenAI-compatible request to a Cardean-managed endpoint, then adds project identity and one policy.
- Create or receive a Cardean environment.
- Add a provider credential to the controlled credential store.
- Create a project and issue an application credential.
- Change the application base URL.
- Send a test request.
- Apply an allowed-model or budget policy.
- Inspect the decision and request metadata.
Choose the path that matches what you are building.
Integrate
API reference, SDK patterns, authentication and request examples.
Operate
Configuration, deployments, upgrades, metrics, logs, backups and recovery.
Govern
Policy model, identities, roles, evidence, retention and exceptions.
Extend
Provider adapters, webhooks, exports, policy hooks and community integrations.
Contribute
Repository guides, issue labels, development setup, roadmap and release process.
Change the endpoint. Keep the request shape. Add policy at the boundary.
# Illustrative only — point an existing OpenAI-compatible request at a Cardean-managed endpoint. curl https://gateway.example.cardean.io/v1/chat/completions \ -H "Authorization: Bearer $CARDEAN_APP_KEY" \ -H "Content-Type: application/json" \ -d '{"model": "gpt-4o-mini", "messages": [{"role": "user", "content": "hello"}]}'
Tested release examples for Python, TypeScript and cURL ship with the documentation.