@ouro.bot/cli 0.1.0-alpha.56 → 0.1.0-alpha.561

package/dist/trips/store.js

@@ -0,0 +1,146 @@
+"use strict";
+var __createBinding = (this && this.__createBinding) || (Object.create ? (function(o, m, k, k2) {
+    if (k2 === undefined) k2 = k;
+    var desc = Object.getOwnPropertyDescriptor(m, k);
+    if (!desc || ("get" in desc ? !m.__esModule : desc.writable || desc.configurable)) {
+      desc = { enumerable: true, get: function() { return m[k]; } };
+    }
+    Object.defineProperty(o, k2, desc);
+}) : (function(o, m, k, k2) {
+    if (k2 === undefined) k2 = k;
+    o[k2] = m[k];
+}));
+var __setModuleDefault = (this && this.__setModuleDefault) || (Object.create ? (function(o, v) {
+    Object.defineProperty(o, "default", { enumerable: true, value: v });
+}) : function(o, v) {
+    o["default"] = v;
+});
+var __importStar = (this && this.__importStar) || (function () {
+    var ownKeys = function(o) {
+        ownKeys = Object.getOwnPropertyNames || function (o) {
+            var ar = [];
+            for (var k in o) if (Object.prototype.hasOwnProperty.call(o, k)) ar[ar.length] = k;
+            return ar;
+        };
+        return ownKeys(o);
+    };
+    return function (mod) {
+        if (mod && mod.__esModule) return mod;
+        var result = {};
+        if (mod != null) for (var k = ownKeys(mod), i = 0; i < k.length; i++) if (k[i] !== "default") __createBinding(result, mod, k[i]);
+        __setModuleDefault(result, mod);
+        return result;
+    };
+})();
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.TripNotFoundError = void 0;
+exports.ensureAgentTripLedger = ensureAgentTripLedger;
+exports.readAgentTripKeypair = readAgentTripKeypair;
+exports.upsertTripRecord = upsertTripRecord;
+exports.readTripRecord = readTripRecord;
+exports.listTripIds = listTripIds;
+const fs = __importStar(require("node:fs"));
+const path = __importStar(require("node:path"));
+const identity_1 = require("../heart/identity");
+const runtime_1 = require("../nerves/runtime");
+const core_1 = require("./core");
+function tripsRoot(agentName) {
+    return path.join((0, identity_1.getAgentRoot)(agentName), "state", "trips");
+}
+function ledgerPath(agentName) {
+    return path.join(tripsRoot(agentName), "ledger.json");
+}
+function recordsDir(agentName) {
+    return path.join(tripsRoot(agentName), "records");
+}
+function recordPath(agentName, tripId) {
+    return path.join(recordsDir(agentName), `${tripId}.json`);
+}
+function readJsonFile(filePath) {
+    if (!fs.existsSync(filePath))
+        return null;
+    return JSON.parse(fs.readFileSync(filePath, "utf-8"));
+}
+function writeJsonAtomic(filePath, value) {
+    fs.mkdirSync(path.dirname(filePath), { recursive: true });
+    const tmp = `${filePath}.tmp`;
+    fs.writeFileSync(tmp, JSON.stringify(value, null, 2), "utf-8");
+    fs.renameSync(tmp, filePath);
+}
+class TripNotFoundError extends Error {
+    statusCode = 404;
+    constructor(input) {
+        super(`trip not found: agent=${input.agentName} trip=${input.tripId}`);
+    }
+}
+exports.TripNotFoundError = TripNotFoundError;
+/**
+ * Idempotent — if the agent already has a ledger on disk, return it; otherwise
+ * generate a fresh keypair and persist both halves.
+ */
+function ensureAgentTripLedger(input) {
+    const existing = readJsonFile(ledgerPath(input.agentName));
+    if (existing) {
+        return { ledger: existing.ledger, added: false };
+    }
+    const created = (0, core_1.newTripLedgerRecord)({
+        agentId: input.agentName,
+        ...(input.label ? { label: input.label } : {}),
+        ...(input.now ? { now: input.now } : {}),
+    });
+    const stored = {
+        schemaVersion: 1,
+        ledger: created.ledger,
+        privateKeyPem: created.keypair.privateKeyPem,
+    };
+    writeJsonAtomic(ledgerPath(input.agentName), stored);
+    (0, runtime_1.emitNervesEvent)({
+        component: "trips",
+        event: "trips.ledger_created",
+        message: "agent trip ledger keypair created",
+        meta: { agentId: input.agentName, ledgerId: created.ledger.ledgerId, keyId: created.ledger.keyId },
+    });
+    return { ledger: created.ledger, added: true };
+}
+function readLedgerOrThrow(agentName) {
+    const stored = readJsonFile(ledgerPath(agentName));
+    if (!stored) {
+        throw new Error(`no trip ledger for agent ${agentName} — call ensureAgentTripLedger first`);
+    }
+    return stored;
+}
+function readAgentTripKeypair(agentName) {
+    const stored = readLedgerOrThrow(agentName);
+    return {
+        keyId: stored.ledger.keyId,
+        publicKeyPem: stored.ledger.publicKeyPem,
+        privateKeyPem: stored.privateKeyPem,
+    };
+}
+function upsertTripRecord(agentName, trip) {
+    const stored = readLedgerOrThrow(agentName);
+    const payload = (0, core_1.encryptTripRecord)(trip, stored.ledger.publicKeyPem, stored.ledger.keyId);
+    writeJsonAtomic(recordPath(agentName, trip.tripId), payload);
+    (0, runtime_1.emitNervesEvent)({
+        component: "trips",
+        event: "trips.record_upserted",
+        message: "trip record upserted",
+        meta: { agentId: agentName, tripId: trip.tripId, legCount: trip.legs.length, status: trip.status },
+    });
+}
+function readTripRecord(agentName, tripId) {
+    const payload = readJsonFile(recordPath(agentName, tripId));
+    if (!payload)
+        throw new TripNotFoundError({ agentName, tripId });
+    const stored = readLedgerOrThrow(agentName);
+    return (0, core_1.decryptTripRecord)(payload, stored.privateKeyPem);
+}
+function listTripIds(agentName) {
+    const dir = recordsDir(agentName);
+    if (!fs.existsSync(dir))
+        return [];
+    return fs.readdirSync(dir)
+        .filter((entry) => entry.endsWith(".json"))
+        .map((entry) => entry.slice(0, -".json".length))
+        .sort();
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ouro.bot/cli",
-  "version": "0.1.0-alpha.56",
+  "version": "0.1.0-alpha.561",
   "main": "dist/heart/daemon/ouro-entry.js",
   "bin": {
     "cli": "dist/heart/daemon/ouro-bot-entry.js",
@@ -9,8 +9,9 @@
   },
   "files": [
     "dist/",
-    "AdoptionSpecialist.ouro/",
-    "subagents/",
+    "SerpentGuide.ouro/",
+    "RepairGuide.ouro/",
+    "skills/",
     "assets/",
     "changelog.json"
   ],
@@ -19,36 +20,66 @@
     "./runOuroCli": "./dist/heart/daemon/daemon-cli.js"
   },
   "scripts": {
-    "dev": "tsc && node dist/senses/cli-entry.js --agent ouroboros",
+    "dev": "tsc && node dist/heart/daemon/ouro-bot-entry.js dev",
+    "cli": "tsc && node dist/senses/cli-entry.js",
     "daemon": "tsc && node dist/heart/daemon/daemon-entry.js",
     "ouro": "tsc && node dist/heart/daemon/ouro-entry.js",
     "teams": "tsc && node dist/senses/teams-entry.js --agent ouroboros",
-    "bluebubbles": "tsc && node dist/senses/bluebubbles-entry.js --agent ouroboros",
+    "bluebubbles": "tsc && node dist/senses/bluebubbles/entry.js --agent ouroboros",
     "test": "vitest run",
+    "test:integration": "npm run build && vitest run --config vitest.integration.config.ts",
+    "test:e2e:package": "npm run build && node scripts/package-e2e.cjs",
+    "test:e2e:real-smoke": "npm run build && node scripts/nightly-real-smoke.cjs",
+    "typecheck:mailbox-ui": "tsc --noEmit -p packages/mailbox-ui/tsconfig.json",
+    "test:mailbox-ui": "npm test --prefix packages/mailbox-ui",
     "test:coverage:vitest": "vitest run --coverage",
     "test:coverage": "node scripts/run-coverage-gate.cjs",
-    "build": "tsc",
+    "build": "node scripts/clean-dist.cjs && tsc && (cd packages/mailbox-ui && npm install --ignore-scripts 2>/dev/null && npm run build && cd ../.. && node scripts/copy-mailbox-ui.cjs) || echo 'mailbox-ui build skipped'",
     "lint": "eslint src/",
+    "release:preflight": "node scripts/release-preflight.cjs",
+    "release:smoke": "node scripts/release-smoke.cjs",
     "audit:nerves": "npm run build && node dist/nerves/coverage/cli-main.js"
   },
   "dependencies": {
     "@anthropic-ai/sdk": "^0.78.0",
+    "@azure/identity": "^4.13.0",
+    "@azure/storage-blob": "^12.31.0",
+    "@microsoft/teams.api": "2.0.5",
     "@microsoft/teams.apps": "^2.0.5",
+    "@microsoft/teams.cards": "2.0.5",
+    "@microsoft/teams.common": "2.0.5",
     "@microsoft/teams.dev": "^2.0.5",
+    "@microsoft/teams.graph": "2.0.5",
+    "@types/react": "^17.0.91",
     "fast-glob": "^3.3.3",
+    "ink": "^3.2.0",
+    "mailparser": "^3.9.8",
     "openai": "^6.27.0",
-    "semver": "^7.7.4"
+    "react": "^17.0.2",
+    "semver": "^7.7.4",
+    "smtp-server": "^3.18.4",
+    "stripe": "^22.0.0"
   },
   "repository": {
     "type": "git",
     "url": "https://github.com/ouroborosbot/ouroboros"
   },
   "devDependencies": {
+    "@testing-library/react": "^16.3.2",
+    "@types/mailparser": "^3.4.6",
     "@types/semver": "^7.7.1",
+    "@types/smtp-server": "^3.5.13",
     "@vitest/coverage-v8": "^4.0.18",
     "eslint": "^10.0.2",
+    "jsdom": "^29.0.2",
     "typescript": "^5.7.0",
     "typescript-eslint": "^8.56.1",
     "vitest": "^4.0.18"
+  },
+  "overrides": {
+    "@testing-library/react": {
+      "react": "$react",
+      "@types/react": "$@types/react"
+    }
   }
 }

package/skills/agent-commerce.md

@@ -0,0 +1,106 @@
+# Agent Commerce Skill
+
+How to book, purchase, and pay for things on behalf of humans.
+
+## Three Patterns
+
+### Pattern A: API (Structured, Preferred)
+
+For services with direct API access: Duffel flights, LiteAPI hotels.
+
+1. Search using the API tool (`flight_search`, LiteAPI MCP)
+2. Present options to the human with prices and details
+3. Human approves a specific option and price
+4. Book using the API tool with passenger data from `user_profile_get`
+5. Create a single-use virtual card via `stripe_create_card`
+6. Complete payment through the API
+7. Deactivate the card via `stripe_deactivate_card`
+8. Confirm booking to the human
+
+**Key tools**: `flight_search`, `flight_book`, `flight_cancel`, `user_profile_get`, `user_profile_store`, `stripe_create_card`, `stripe_deactivate_card`, `stripe_list_cards`
+
+### Pattern B: Browser (Best-Effort)
+
+For sites without API access, use browser automation via Playwright MCP.
+
+1. Navigate to the booking site
+2. Search for the requested service
+3. Fill forms using data from `user_profile_get`
+4. Use a virtual card from `stripe_create_card` for payment
+5. If blocked by anti-bot measures, fall back to Pattern C
+6. Complete and confirm the booking
+
+**Limitations**: Browser automation is fragile. Sites may block, layouts change, CAPTCHAs appear. Always have Pattern C as fallback.
+
+### Pattern C: Link-Only (Primary for Hostile Sites)
+
+For sites that block automation or require complex human interaction.
+
+1. Research the best options using browser tools or API tools
+2. Prepare a curated link with pre-filled parameters where possible
+3. Send the link to the human with a summary of what to book
+4. Human completes the booking in their own browser
+
+**When to use**: Always use Pattern C as the primary approach for sites known to block automation (most airline direct sites, hotel chains, rental car sites). Pattern B is best-effort, not reliable.
+
+## Payment autonomy Levels
+
+- **Level 0**: No autonomous payments. Agent researches, human pays manually.
+- **Level 1**: Agent creates virtual cards, human approves each transaction explicitly.
+- **Level 2**: Agent can book pre-approved items (within budget, approved categories) without per-transaction approval.
+- **Level 3**: Full delegation with spending limits. Agent manages a budget and books as needed.
+
+Default is Level 1. Level changes require explicit human approval.
+
+## Error Handling
+
+### Price Change Guard
+Before completing a booking, verify the final price matches the approved price within 5%. If the price changed more than 5%, stop and report to the human. Never pay a price the human didn't approve.
+
+### Partial Failure Reporting
+When booking involves multiple services (e.g., flight + hotel), each service may succeed or fail independently — this is a partial failure scenario. Report the status of each service separately. **Never auto-cancel a successful booking because a related booking failed.** Let the human decide.
+
+Example: "Flight SFO-JFK booked (confirmation: ABC123). Hotel booking failed: no availability for those dates. Would you like me to search for alternative hotels?"
+
+### Refund Flow
+If a booking fails after card creation:
+1. Deactivate the virtual card immediately
+2. Report the failure to the human
+3. If a charge was made, note it for the human to follow up with the provider
+
+## CAPTCHA Handling
+
+When a CAPTCHA appears during browser automation (Pattern B):
+1. Take a screenshot and send it to the human
+2. Explain what page you're on and what you were trying to do
+3. Ask the human to solve the CAPTCHA in their own browser
+4. Switch to Pattern C (link-only) for this transaction
+
+Never attempt to solve CAPTCHAs programmatically.
+
+## Card Number Isolation
+
+Card numbers must NEVER appear in:
+- Tool return values shown to the model
+- Nerves events or logs
+- Chat messages to the human
+- Any stored state or written notes
+
+The only place card numbers exist is inside the Stripe client's internal payment flow functions, scoped to a single function call. The model only ever sees card IDs and last-4 digits.
+
+## Profile Data Usage
+
+Access profile data only when needed for the current transaction:
+- `user_profile_get` to retrieve specific fields (never dump full profile)
+- Passport data only for international bookings
+- Loyalty program numbers only when booking with that program
+- Emergency contact only when the booking service requires it
+
+## Self-Test
+
+Before first use, run the commerce self-test to verify all services are configured:
+- Stripe: creates and deactivates a test virtual card
+- Duffel: runs a test flight search
+- LiteAPI: verifies API key in vault
+
+Report results to the human with actionable next steps for any failures.

package/skills/browser-navigation.md

@@ -0,0 +1,117 @@
+# Browser Navigation Skill
+
+When to use browser tools and how to navigate effectively.
+
+## When to Use Browser Tools
+
+Use browser navigation when:
+- The target site has no API (e.g., Airbnb, VRBO, travel blogs)
+- Content is dynamic or requires JavaScript rendering
+- Login-required pages need session-based access
+- You need to verify visual content (screenshots, layouts)
+- Price comparison requires real-time scraping
+
+Do NOT use browser tools when:
+- A dedicated API or MCP server exists (prefer `weather_lookup`, Duffel MCP, etc.)
+- The data is available via a public JSON endpoint
+- The task can be completed with `web_search`
+
+## Stealth Browsing Best Practices
+
+The `@playwright/mcp` server is configured with realistic user-agent and viewport settings. To avoid detection on travel sites:
+
+- **Add delays between navigations**: Wait 2-5 seconds between page loads. Never hammer requests in rapid succession.
+- **Vary timing**: Use random delays rather than fixed intervals (e.g., 2-5s, not exactly 3s every time).
+- **Avoid predictable patterns**: Don't navigate the same path repeatedly in short succession.
+- **Use realistic scroll behavior**: Scroll gradually through pages rather than jumping to specific elements.
+- **Respect robots.txt**: Check for rate limits and crawling restrictions.
+
+## Navigation Workflow
+
+Follow this pattern for every page interaction:
+
+1. **Navigate**: Use `browser_navigate` to load the page
+2. **Wait**: Allow the page to fully load (use `browser_wait` if needed)
+3. **Snapshot**: Take a `browser_snapshot` to understand the page structure
+4. **Extract**: Parse the accessibility tree for relevant data
+5. **Screenshot** (optional): Use `browser_screenshot` for visual confirmation
+
+## Form Filling Patterns
+
+### Login Flows
+1. Navigate to the login page
+2. Take a snapshot to identify form fields
+3. Use `browser_type` for username/password fields
+4. Use `browser_click` to submit
+5. Wait for redirect, then verify login succeeded via snapshot
+6. NEVER hardcode credentials -- use `credential_get` to retrieve login info
+
+### Sign-up Flows
+1. Use `credential_generate_password` to mint a strong password for the target domain
+2. Fill the signup form with that password
+3. If the site rejects the password policy, generate a new one that matches the site rules
+4. Once the site accepts the exact password, call `credential_store` immediately
+5. Do not claim a new credential is saved until `credential_store` succeeds
+
+### Search Forms (Hotels, Flights, Rentals)
+1. Navigate to the search page
+2. Snapshot to identify input fields
+3. Fill location/date fields with `browser_type`
+4. Select options with `browser_select_option` or `browser_click`
+5. Submit the search
+6. Wait for results to load (travel sites often have loading animations)
+7. Snapshot the results page to extract listings
+
+### Booking Forms
+1. **ALWAYS confirm with the user before proceeding to payment**
+2. Fill traveler information
+3. Use stored credentials for payment (via `credential_get` -- NEVER type raw card numbers)
+4. Screenshot the final review page for user confirmation
+5. Only click "Book" / "Confirm" after explicit user approval
+
+## Anti-Bot Detection Avoidance
+
+The stealth configuration handles most fingerprinting automatically. Additionally:
+
+- **Don't access detection endpoints**: Avoid URLs containing "captcha", "challenge", "verify"
+- **Handle CAPTCHAs**: If you encounter a CAPTCHA, pause and inform the user. Do not attempt automated solving.
+- **Rotate viewport sizes occasionally**: Use different viewport sizes across sessions
+- **Maintain cookies**: Use persistent `user-data-dir` to appear as a returning user
+- **Avoid headless tells**: The user-agent is set to a real browser string
+
+## Travel Site Patterns
+
+### Airbnb / VRBO
+1. Search by location + check-in/check-out dates + guests
+2. Results load dynamically -- scroll to load more listings
+3. Extract: title, price per night, total price, rating, number of reviews
+4. For detailed info, click into each listing and snapshot
+5. Compare top 3-5 options
+
+### Hotel Sites (Booking.com, Hotels.com)
+1. Search by destination + dates + guests + rooms
+2. Filter by price range, star rating, amenities
+3. Extract: name, price, location, rating, key amenities
+4. Check cancellation policies (important for travel planning)
+
+### Flight Comparison
+1. Prefer Duffel MCP for flight search (structured API data)
+2. Use browser only if Duffel doesn't cover the airline
+3. Google Flights is useful for price comparison but requires careful navigation
+
+## Error Handling
+
+- **Page timeouts**: Retry once after 5 seconds. If still failing, inform the user.
+- **CAPTCHAs**: Stop and ask the user to solve manually.
+- **Stale elements**: Re-snapshot the page and retry the interaction.
+- **Blocked/403**: The site may have detected automation. Wait 30 seconds and try with a different approach (e.g., direct URL instead of navigation).
+- **Session expired**: Re-login using stored credentials.
+
+## Human Confirmation Gates
+
+**ALWAYS** confirm with the user before:
+- Any booking or payment action
+- Entering personal information (name, address, phone)
+- Agreeing to terms of service
+- Subscribing to any service
+- Any action that creates a financial obligation

package/skills/commerce-setup-guide.md

@@ -0,0 +1,116 @@
+# Commerce Setup Guide
+
+Human-facing guide for configuring the agent's commerce capabilities.
+
+## Architecture Overview
+
+The agent's commerce system has three pillars:
+
+1. **User Profile**: Secure storage of personal data (name, passport, payment preferences) in Vaultwarden, accessed only when needed for specific transactions.
+
+2. **Booking Delegation**: Direct API access to flight (Duffel) and hotel (LiteAPI) booking systems, plus browser automation fallback for sites without APIs.
+
+3. **Payment**: Stripe Issuing virtual cards created per-transaction, with spend limits and merchant category restrictions. Card numbers never enter the model's context.
+
+## Setup Steps
+
+### 1. Stripe Issuing (Required for Payments)
+
+- Create a Stripe account: https://dashboard.stripe.com
+- Enable Stripe Issuing (requires business verification)
+- Create a restricted API key: https://dashboard.stripe.com/apikeys
+  - Permissions needed: `issuing_cards:write`, `issuing_cards:read`
+- Store in vault: `credential_store stripe.com --password <key>`
+
+### 2. Duffel (Flights)
+
+- Create a Duffel account: https://app.duffel.com
+- Generate a sandbox token: https://app.duffel.com/tokens
+- Store in vault: `credential_store duffel.com --password <token>`
+
+### 3. LiteAPI (Hotels)
+
+- Create a LiteAPI account: https://dashboard.liteapi.travel
+- Get your sandbox API key
+- Store in vault: `credential_store liteapi.travel --password <key>`
+- Configure MCP server in agent.json (see commerce-setup.md skill for details)
+
+### 4. User Profile
+
+Store your travel profile with the agent:
+```
+user_profile_store '{"legalName":{"first":"...","last":"..."},"email":"...","phone":"...","preferences":{}}'
+```
+
+## Tool Reference
+
+### User Profile Tools
+| Tool | Description | Trust Level |
+|------|-------------|-------------|
+| `user_profile_store` | Store/update profile fields | Family |
+| `user_profile_get` | Retrieve a specific profile field | Family |
+| `user_profile_delete` | Delete entire profile | Family |
+
+### Payment Tools
+| Tool | Description | Trust Level |
+|------|-------------|-------------|
+| `stripe_create_card` | Create a virtual card | Family |
+| `stripe_deactivate_card` | Deactivate a card | Family |
+| `stripe_list_cards` | List active cards | Family |
+
+### Flight Tools
+| Tool | Description | Trust Level |
+|------|-------------|-------------|
+| `flight_search` | Search for flights | Friend |
+| `flight_hold` | Hold a flight offer | Family |
+| `flight_book` | Book a flight | Family |
+| `flight_cancel` | Cancel a booking | Family |
+
+### Hotel Tools
+Hotels are accessed through the LiteAPI MCP server. Tools are dynamically registered when the MCP server connects. Common tools include search, get rates, and book.
+
+## Security Model
+
+### Credential Gateway
+All API keys are stored in the agent's Vaultwarden vault. They are never exposed as environment variables or stored in config files. MCP servers receive credentials at startup via `vault:` env resolution.
+
+### Card Number Isolation
+Virtual card numbers exist only within the Stripe client's internal functions during a payment flow. They are never:
+- Returned to the model in tool outputs
+- Included in nerves events or logs
+- Stored in any persistent state
+- Shown in chat messages
+
+The model only sees card IDs (e.g., `ic_...`) and last-4 digits.
+
+### Trust Gating
+- **Family trust required**: All profile, payment, and booking tools
+- **Friend trust sufficient**: Flight search (read-only, no payment)
+- **Stranger/acquaintance**: No commerce access
+
+### Vault Resolution Failures
+When a `vault:` reference cannot be resolved for an MCP server:
+- The specific server is skipped (not crashed)
+- Other servers continue to start normally
+- An error event is emitted with the specific resolution failure
+- Error messages are actionable (e.g., "item not found", "field empty")
+
+## Verification Tiers
+
+### Tier 1: Real-Tested
+- User profile vault CRUD (tested against live Vaultwarden)
+- MCP credential injection (tested with real `vault:` env resolution)
+- Tool registration and guardrail enforcement
+
+### Tier 2: Mocked
+- Stripe Issuing API calls (mocked SDK)
+- Duffel flight API calls (mocked HTTP)
+- LiteAPI hotel API calls (MCP config only)
+- Full booking flow (profile -> search -> card -> book -> confirm -> deactivate)
+- Card number leakage verification
+
+### Post-Handoff
+- Real Stripe Issuing card creation (requires live Stripe account with Issuing)
+- Real Duffel booking (requires live API key)
+- Real LiteAPI hotel search (requires live MCP server)
+- Browser automation for Pattern B sites

package/skills/commerce-setup.md

@@ -0,0 +1,84 @@
+# Commerce Setup Wizard
+
+Step-by-step guide for setting up the agent's commerce infrastructure: payment, booking, and accommodation APIs.
+
+last_verified: 2026-04-06
+
+## Prerequisites
+
+- Agent vault must be set up (run `vault_setup` tool if not done)
+- Vault must be reachable at the configured server URL
+
+## Step 1: Stripe Issuing (Payments)
+
+1. Create a Stripe account at https://dashboard.stripe.com
+2. Enable Stripe Issuing (requires business verification)
+3. Create a restricted API key at https://dashboard.stripe.com/apikeys
+   - Enable only `issuing_cards:write` and `issuing_cards:read` permissions
+4. Store the key in the vault: `credential_store stripe.com --password <restricted_key> --notes "Stripe Issuing restricted key"`
+
+### Verification
+Run `stripe_list_cards` to verify the key works. Expected: empty list or existing cards.
+
+## Step 2: Duffel (Flights)
+
+1. Create a Duffel account at https://app.duffel.com
+2. Generate a sandbox API token at https://app.duffel.com/tokens
+   - Start with sandbox mode for testing
+   - Switch to live mode when ready for real bookings
+3. Store the key in the vault: `credential_store duffel.com --password <api_token> --notes "Duffel API token (sandbox)"`
+
+### Verification
+Run `flight_search` with any route (e.g., SFO to JFK). Expected: list of flight offers.
+
+## Step 3: LiteAPI (Hotels)
+
+1. Create a LiteAPI account at https://dashboard.liteapi.travel
+2. Get your sandbox API key from the dashboard
+3. Store the key in the vault: `credential_store liteapi.travel --password <api_key> --notes "LiteAPI sandbox key"`
+4. Configure the MCP server in agent.json:
+   ```json
+   {
+     "mcpServers": {
+       "liteapi": {
+         "command": "npx",
+         "args": ["tsx", "src/index.ts"],
+         "cwd": "/path/to/liteapi-mcp-server",
+         "env": {
+           "LITEAPI_API_KEY": "vault:liteapi.travel/apiKey"
+         }
+       }
+     }
+   }
+   ```
+
+### Verification
+The LiteAPI MCP server will start automatically when the agent boots. Check agent logs for `mcp.connect_end` event for the liteapi server.
+
+## Step 4: User Profile
+
+Store the human's travel profile:
+```
+user_profile_store '{"legalName": {"first": "...", "last": "..."}, "email": "...", "phone": "...", "preferences": {}}'
+```
+
+Optional but recommended fields: dateOfBirth, passport, driverLicense, addresses, loyaltyPrograms.
+
+## Self-Test
+
+After setup, run the commerce self-test to verify all services:
+- Stripe: creates and deactivates a test virtual card
+- Duffel: runs a test flight search
+- LiteAPI: verifies the API key is stored in the vault
+
+The self-test reports per-service health with actionable error messages:
+- "Flights working, hotels not yet -- LiteAPI key missing."
+- "Your Duffel key returned 401. Verify it at app.duffel.com/tokens."
+
+## Security Model
+
+- All API keys stored in the agent's Vaultwarden vault (not env vars)
+- Card numbers never appear in model context or logs
+- Virtual cards are single-use by default, deactivated after each transaction
+- User profile access requires family trust level
+- Vault credentials are resolved at MCP server startup, not at runtime