Enterprise AI deployments need governance: who can access what, how much they're spending, what the AI is actually saying, and whether it's staying within policy. Cognipeer provides this through Console's observability layer and Agent SDK's runtime guardrails.
This guide covers setting up enterprise-grade governance across your AI infrastructure.
When to reach for this recipe
If your team needs the capabilities described above and you'd rather build on proven primitives than wire one from scratch — this is the shape to start from.
Architecture
Console provides the control plane: project management, API key scoping, usage tracking, tracing, and dashboard-level observability.
Agent SDK adds runtime-level governance with input/output guardrails, content filtering, and approval workflows.
1. Project-Scoped API Keys
Console organises resources into projects. Each project gets its own API keys, models, and usage quotas.
1// Each project has isolated API keys
2// Configure via Console dashboard:
3//
4// Project: "Customer Support"
5// - API Key: cp_support_xxx
6// - Allowed models: gpt-4o, claude-3.5-sonnet
7// - Rate limit: 100 req/min
8//
9// Project: "Internal Tools"
10// - API Key: cp_internal_xxx
11// - Allowed models: gpt-4o-mini
12// - Rate limit: 500 req/min
13
14// In your application, use the project-scoped key
15constclient=newConsoleClient({
16apiKey:"cp_support_xxx",// Scoped to "Customer Support"
17baseURL:"https://your-console.example.com",
18});
2. Agent SDK Guardrails
Apply input and output guardrails in Agent SDK to control what agents can say and do before and after a response is generated.
Use Console guardrails when you want tenant-managed policies that can also be evaluated outside the agent runtime, for example at API boundaries or batch moderation steps.