Calypso

Calypso

Calypso Context

EverythingCalypso needsto know.

Documents, products, policies, customer history, permissions, and previous decisions. Calypso keeps every source organized, current, and ready to cite when it answers.

Start teaching Calypso Read API docs
Text & visual Always current Ready to cite

Context ready

bucket://support-handbook

Ready
Indexed members12 / 12

8

files

3

websites

1

Q&A

Answering as

calypso-rag-agent:support

Answers scoped to this knowledge.

Every fact has a home

Documents, products, policies, and history land in named collections before Calypso answers from them.

Knowledge arrives with intent

Files, websites, and Q&A are filed where they belong — support, pricing, legal — before indexing starts.

Readiness is explicit

Received, read, understood, ready — you can see exactly when Calypso can answer from a new source.

The Agent uses curated knowledge

The Calypso Agent answers only from the knowledge you scoped to it — focused and repeatable.

Source boundaries

The right knowledge for every conversation.

Context keeps support docs, pricing rules, legal policies, onboarding guides, screenshots, and customer files separated by purpose — so Calypso answers from the source set it is supposed to trust.

support-handbook

Support

Sync help center pages, troubleshooting PDFs, screenshots, and escalation notes into one cite-ready support collection.

pricing

Pricing

Keep packaging docs, plan sheets, procurement FAQs, and discount policies separate from broad product knowledge.

legal

Legal

Give legal conversations a governed source set for terms, policies, compliance PDFs, and data handling documents.

customer-onboarding

Onboarding

Assemble setup guides, diagrams, checklists, and customer-specific instructions for onboarding conversations.

REST API

List retrieval buckets

cURL 
# 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
      }
    }
  ]
}
GET/v1/knowledge/buckets

List bucket ids, slugs, source counts, status, and bucket-store readiness for the team behind an API key.

POST/v1/knowledge/files/upload-session

Create a direct upload session and route one file into bucket_ids, bucket_slugs, bucket, or create_missing_buckets.

POST/v1/knowledge/files:batch/upload-session

Prepare 1 to 100 files with shared or per-item bucket destinations, then poll readiness.

Readiness model

Ready means searchable, not just uploaded.

A new source counts only when Calypso can actually answer from it. Ready means indexed, scoped, and citable — visible before your customers ever ask.

1

Received

Part of the durable ingestion path.

2

Queued

Part of the durable ingestion path.

3

Reading

Part of the durable ingestion path.

4

Understood

Part of the durable ingestion path.

5

Ready to cite

Calypso can now answer from it — with citations.

Under the hood

The retrieval questions, answered.

Calypso Context is built on multimodal Gemini File Search RAG. If you care how the grounding works, this is your section.

Get started with Context

Teach Calypso your business.

Start with Context, put it to work through the Calypso Agent, and reuse the same knowledge across WhatsApp, your API, n8n, Gmail, and your site.

Get started free Context docs