Project
API keys and billing
The most important project-level responsibilities in Calypso RAG are API key management, billing visibility, usage awareness, and member access.
Why this page exists
The Project area in Calypso RAG is intentionally narrower than the full Calypso platform. The most important operational responsibilities are:
- keeping API keys healthy
- understanding billing status
- understanding usage visibility
- managing members
Billing in the RAG variant
The RAG product uses a hosted onboarding and checkout model. In practice, that means:
- checkout is part of the product flow
- a phone number is required for billing, support, and hosted workspace activation
- the workspace is treated as ready after checkout instead of waiting on WhatsApp or assistant activation
Member access
Use Project → Members when you need to control who can work inside the RAG workspace.
Keep member access aligned to real responsibilities:
- who curates sources
- who changes agent policy
- who owns production integrations
Operational recommendation
Treat API key ownership and billing ownership as deliberate responsibilities, not background settings.
In a retrieval product, broken keys or misunderstood billing state will surface as reliability problems long before they look like administrative issues.