Buckets are retrieval storage for AI teams
A Calypso Bucket is a named source layer for RAG. Agents search the buckets you attach instead of scanning an unstructured pile of uploads.
Calypso Buckets store docs, websites, PDFs, Q&A, and customer context in durable retrieval spaces. Keep knowledge organized, indexed, and ready for source-grounded answers.
1-100
files per batch
active
readiness signal
scoped
agent memory
Bucket live
8
files
3
websites
1
Q&A
attached agent
calypso-rag-agent:support
memory scoped to this bucket
A Calypso Bucket is a named source layer for RAG. Agents search the buckets you attach instead of scanning an unstructured pile of uploads.
Single-file, batch, UI, and MCP uploads target a bucket id, bucket slug, or bucket name before Calypso accepts the file for indexing.
A file can be accepted, queued, indexed, and then bucket-active. Production tests should wait for bucket sync before evaluating answers.
The default hosted agent and named profiles can each point at selected buckets for focused, repeatable retrieval.
Bucket design
Pour the right raw material into each bucket: docs, screenshots, websites, FAQs, policies, and customer files. Calypso keeps the retrieval boundary clean so agents answer from the right source set.
support-handbookSync help center pages, troubleshooting PDFs, screenshots, and escalation notes into one cite-ready support bucket.
pricingKeep packaging docs, plan sheets, procurement FAQs, and discount policies separate from broad product knowledge.
legalGive legal-facing agents a governed source set for terms, policies, compliance PDFs, and data handling documents.
customer-onboardingAssemble setup guides, diagrams, checklists, and customer-specific instructions for onboarding assistants.
API workflow
# List retrieval buckets for this API key
curl https://api.calypso.so/v1/knowledge/buckets \
-H "Authorization: Bearer sk_..."
{
"team_id": "team_123",
"buckets": [
{
"id": "bucket_abc",
"slug": "support-handbook",
"name": "Support Handbook",
"status": "active",
"memberCount": 12,
"counts": {
"file": 8,
"website": 3,
"qa": 1,
"retrievable": 12
},
"bucketStore": {
"status": "active",
"indexed_member_count": 12,
"pending_member_count": 0
}
}
]
}/v1/knowledge/bucketsList bucket ids, slugs, source counts, status, and bucket-store readiness for the team behind an API key.
/v1/knowledge/files/upload-sessionCreate a direct upload session and route one file into bucket_ids, bucket_slugs, bucket, or create_missing_buckets.
/v1/knowledge/files:batch/upload-sessionPrepare 1 to 100 files with shared or per-item bucket destinations, then poll readiness.
Readiness model
For reliable RAG tests, wait until each source is indexed and the bucket store reports it as active. That is the point when an agent can retrieve and cite the new knowledge.
Accepted
Part of the durable ingestion path.
Queued
Part of the durable ingestion path.
Indexing
Part of the durable ingestion path.
Active source
Part of the durable ingestion path.
Bucket active
Searchable through the selected bucket.
Get started with Buckets
Create buckets for each source boundary, attach them to agent profiles, and reuse the same retrieval layer across your website, API, MCP, n8n, and product UI.