Skip to content

Licensing & Quotas

chakra-convai requires a valid license issued by Chakra Console (CHAKRA_LICENSE_KEY). The engine will refuse to start or serve calls without a verified license.


Cryptographic License Verification

  1. Startup Check: On boot, the engine contacts Chakra Console's /v2/verify endpoint.
  2. Cryptographic Signature: The license payload is signed using Ed25519; the engine verifies this signature against Chakra Labs' public key.
  3. Periodic Recheck: During execution, the license is periodically refreshed.
  4. Grace Period: If the network connection to Chakra Console experiences a transient outage, the engine enters a configurable grace period, ensuring ongoing phone calls and web sessions are not interrupted.

Governed Attributes

Chakra Console centrally governs several core operational constraints:

1. Project Type & Channel Entitlements

A project license authorizes specific channel combinations: - phone - web_voice - web_chat

If an application attempts to launch a session on an unauthorized channel, the session is refused with caller_refused.

2. Pipeline Allocations & Pins

The license dictates which speech pipelines (chakra managed, gemini_live) the application can use, and may optionally pin specific agents to dedicated pipelines.

3. Daily Talk Time Limit Per Caller

To prevent runaway billing or spam callers, Chakra Console configures the maximum daily talk time allowed per unique telephone number.

The engine tracks cumulative call minutes in PostgreSQL. When a caller approaches their daily quota, warning prompts ([call_limit] approaching_limit) play before the call politely concludes ([call_limit] time_up).


Usage Reporting

At the end of each session, chakra-convai securely reports usage metrics to Chakra Console: - Session Type (phone, web_voice, web_chat) - Model utilized - Cumulative token usage (text tokens, speech input/output audio seconds, vision frames) - Session duration