"Buy a Ticket BOS → NYC, Charge My Amex"

💬 You type one sentence:

That's it. You don't click through screens. You don't open a travel website. You don't open your credit card app. You don't write an email. You just say what you want.

🤖 The AI does 4 things automatically:

📋 But wait — who sets "the rules"?

In any company, different people have different spending limits. Your company probably has rules like:

A manager uploads these rules from any data source — documents, web pages, wikis, databases, or even pasted text. Each source is chunked, vectorized, and indexed for semantic search. No coding required. The AI searches these indexes before every action and enforces them automatically.

📚 What is "RAG"? (The simplest explanation)

RAG stands for Retrieval-Augmented Generation. Sounds fancy. Here's what it really means:

Think of it like a smart filing cabinet. Your company's rules are filed away. Before the AI does anything, it opens the cabinet, reads the relevant rules, and follows them.

The magic: the rules come from any data source — documents, web pages, wikis, databases, blob storage. Each source is chunked, embedded into vectors, and stored in searchable AI indexes. Change the source, and the AI's behavior changes instantly. No developers needed. No code deployments.

🔒 What about passwords and API keys?

The AI needs to log into Stripe to charge your card, and into Gmail to send your email. But different people have different accounts. How does it know which one to use?

It checks your personal vault first. If you haven't set up your own key, it checks your team's. If your team hasn't set one up either, it uses the company default. Like a waterfall — it flows down until it finds what it needs.

🎯 Putting it all together

When you say "Book a flight and charge my Amex", here's what happens in about 5 seconds:

1. The AI reads your company's rules — finds your budget limit ($500), required class (economy), your preferences (Delta, aisle seat)
2. Searches flights that fit those rules — only shows you economy flights under $500 on Delta
3. Grabs the right Stripe key — your personal? your team's? company default? (waterfall)
4. Finds your Amex card — looks up your saved cards in Stripe, picks the Amex
5. Charges it — $189 to your Amex for Delta BOS→JFK
6. Sends you an email — confirmation + adds it to your Google Calendar

One sentence in. Flight booked, card charged, email sent, calendar updated. Rules followed. No screens. No forms.

💰 "The AI has access to so much financial data. How are pass codes protected?"

Short answer: The AI never sees your passwords, card numbers, or API keys.

Think of it this way: the AI is like a personal assistant who knows your name but not your PIN. It tells the bank what to do, but the bank handles the actual money. The assistant never touches cash.

💳 "Payment gateways — how safe are they? Can they be hacked?"

Short answer: We use Stripe, which is PCI DSS Level 1 certified — the highest security standard in the payments industry.

If a hacker breached ContextWeaver, what would they get? Encrypted vault entries containing Stripe customer IDs (useless without Stripe's API key) and policy documents (your travel rules — not financial data). No card numbers. No bank accounts. No passwords.

🗄️ "What about the personal vault? Where is that data stored?"

Short answer: The vault uses industry-standard secret managers — the same ones that protect bank infrastructure.

In production, your vault is never on the same server as the AI. The AI requests a secret, uses it for one API call, then discards it. The secret is never written to disk, never included in logs, and never sent to the LLM.

🌐 "It depends on how third parties handle data. How do you ensure that?"

Short answer: We only use third parties that are independently audited and certified.

Key principle: ContextWeaver is a conductor, not a warehouse. It orchestrates actions between systems you already trust (Stripe, Gmail, Azure) but never stores your actual financial or personal data itself. Your data stays where it already is — in the systems designed to protect it.

🔄 "What about pass codes when multi-tasking with just one instruction?"

Short answer: Each action uses its own isolated credential lookup. Nothing is shared between steps.

Even though you gave one instruction, each tool call is a separate, isolated execution. The Stripe key used in Step 3 is resolved fresh from the vault, used for that one API call, and immediately discarded. It's never passed to the email step, never stored in memory, and never sent back to the AI. Think of each step as a separate locked room — they can't see into each other.

🧱 Every connector is a building block. Snap them together to build anything.

The travel example above used 3 connectors (Travel + Payments + Email). But ContextWeaver isn't a travel app — it's a platform for building any service by combining connectors like Lego blocks:

🔌 Three ways to add any system to the platform:

🔒 Enterprise-grade security at every level — B2B and B2C