# Vendo

> Embed an agent in your product that lets every customer automate their work, build their own views, and connect their tools, inside your brand and your guardrails.

## Docs

- [Compound tools](https://docs.vendo.run/capabilities/compound-tools.md): Compose multi-step capabilities from your existing tools in .vendo/capabilities.json and run each step through guard with its own approval and audit.
- [Connected accounts](https://docs.vendo.run/capabilities/connected-accounts.md): Let each signed-in user connect their own Gmail, Slack, or GitHub through Composio so every tool call runs as that user, isolated per principal.
- [Connectors: Composio and remote MCP tools in Vendo](https://docs.vendo.run/capabilities/integrations.md): Add Composio and remote MCP tools to Vendo by normalizing them into the same guarded tool registry with policy, approvals, and audit applied.
- [MCP door: expose Vendo tools to Claude, ChatGPT, Cursor](https://docs.vendo.run/capabilities/mcp.md): Serve your product's tools to Claude, ChatGPT, Cursor, and other MCP clients through one guarded, OAuth-authenticated door that shares your policy.
- [Publish your Vendo MCP door to the official registry](https://docs.vendo.run/capabilities/mcp-registry.md): Publish your Vendo MCP door to the official registry: prove domain ownership via DNS or HTTP, generate server.json, and run mcp-publisher.
- [Voice: WebRTC voice stage with useVoice and VendoStage](https://docs.vendo.run/capabilities/voice.md): Use the headless useVoice hook and the shipped VendoStage surface to add a themed, accessible WebRTC voice stage to your Vendo product.
- [Vendo product changelog](https://docs.vendo.run/changelog/overview.md): Weekly release notes covering new Vendo features, product updates, MCP door capabilities, and bug fixes shipped to the SDK and runtime.
- [Architecture: the nine Vendo blocks and how they compose](https://docs.vendo.run/concepts/architecture.md): How the nine Vendo blocks fit together: their one-way dependency rule, the umbrella composition, and where host code plugs into each seam.
- [Generated UI and apps: vendo/app@1 and the sandbox ladder](https://docs.vendo.run/concepts/generated-ui.md): How Vendo generates apps as vendo/app@1 documents, the four-rung sandbox ladder from tree-only to HTTP, and the user-owned import and fork model.
- [In-client venue and approvals](https://docs.vendo.run/concepts/in-client-venue.md): How approved apps render in the host page instead of the sandboxed iframe, how approvals pin the app version hash, and dropping back on version change.
- [Prompt assembly: how Vendo builds the agent system prompt](https://docs.vendo.run/concepts/prompts.md): The fixed five-step order Vendo uses to assemble the agent system prompt each turn, from operating prompt through brief, directions, catalog, and host.
- [Tools and safety: guard.bind, policy, and away-run scopes](https://docs.vendo.run/concepts/tools-and-safety.md): How Vendo unifies host APIs and connectors under one ToolDescriptor shape, routes every call through guard.bind, and scopes authority for away runs.
- [actAs presets for Auth.js, Supabase, Clerk, Auth0](https://docs.vendo.run/connect/act-as-presets.md): Wire Auth.js, Supabase, Clerk, Auth0, or a generic HS256 JWT into Vendo's actAs seam so away automations and MCP calls act as the signed-in user.
- [Tools from your API](https://docs.vendo.run/connect/api-tools.md): How vendo sync extracts OpenAPI operations, tRPC procedures, and host routes into .vendo/tools.json and runs them as the signed-in user under guard.
- [Host components: register branded UI and remix baselines](https://docs.vendo.run/connect/host-components.md): Register branded host components with prop schemas and JSON examples so Vendo's generated apps can select and render your own UI natively.
- [Product instructions: briefs, directions, and design rules](https://docs.vendo.run/connect/instructions.md): Where to place product briefs, company directions, agent-prompt additions, and app design rules so each lands in the correct contracted channel.
- [Theming Vendo surfaces with the VendoTheme token shape](https://docs.vendo.run/connect/theming.md): The VendoTheme token shape extracted into .vendo/theme.json and consumed by every shipped chrome surface, including colors, radii, density, and motion.
- [vendo init: scan, interview, and scaffold your app](https://docs.vendo.run/connect/vendo-init.md): How the vendo init wizard scans your app, asks about your model, brief, critical-tool risk, and the MCP door, and writes reviewable diffs plus .vendo files.
- [Deploying Vendo to production: a wiring checklist](https://docs.vendo.run/deploy/deploying.md): Checklist for taking Vendo to production: model, principal resolution, Postgres store, mounted handler, policy or judge, tick schedule, webhooks, sandbox.
- [Persistence: Postgres schema and PGlite for local dev](https://docs.vendo.run/deploy/persistence.md): How Vendo's Postgres schema, default-on secret encryption, append-only audit, and eraseStore API work across PGlite dev and hosted production.
- [Principals and organizations](https://docs.vendo.run/deploy/principals-and-orgs.md): How Vendo scopes data to users and orgs, merges anonymous sessions on sign-in, reserves the vendo: namespace, and gates org APIs on a Cloud key.
- [Scheduler and webhooks: cron, timers, and event ingestion](https://docs.vendo.run/deploy/scheduler-and-webhooks.md): How Vendo drives UTC cron schedules and duration timers, ingests host events, and verifies external webhook triggers for the automations block.
- [Telemetry and capability misses](https://docs.vendo.run/deploy/telemetry.md): What Vendo's build telemetry and capability-miss events collect, what they never send, and every environment variable and config flag that opts you out.
- [Troubleshooting Vendo: doctor, /status, and error codes](https://docs.vendo.run/deploy/troubleshooting.md): Diagnose broken Vendo wiring with npx vendo doctor, the /status round trip, and the stable error taxonomy shared by CLI, handler, and client.
- [Vendo Cloud: hosted sharing, publishing, and API keys](https://docs.vendo.run/deploy/vendo-cloud.md): Sign in with email OTP, provide an API key to the runtime, and use hosted app sharing and publishing from the CLI or a composition.
- [Vendo: agentic interface SDK for your product](https://docs.vendo.run/index.md): Vendo is a full-stack agentic interface for your product: converse, call your APIs as the signed-in user, generate apps, and run pre-approved automations.
- [Install Vendo: staged playbook for humans and agents](https://docs.vendo.run/install.md): Canonical staged install playbook for Vendo: base install to a green doctor, review and remix, and block unlocks. Raw Markdown at /install.md.
- [Quickstart: Next.js](https://docs.vendo.run/quickstart.md): Install @vendoai/vendo in a Next.js app, mount the fetch handler under /api/vendo, drop in VendoRoot, and ship a first working agent turn.
- [Quickstart: Express and other JavaScript servers](https://docs.vendo.run/quickstart-node.md): A fetch handler you can mount in any Node-compatible runtime. vendo init scaffolds the adapter for Express; elsewhere you mount vendo.handler yourself.
- [CLI reference: vendo init, doctor, sync, refine, mcp, cloud](https://docs.vendo.run/reference/cli.md): Reference for the vendo bin commands: init, doctor for wiring checks, sync for build-time extraction, refine for compound proposals, mcp, and cloud.
- [The .vendo directory: tools, policy, theme, and data files](https://docs.vendo.run/reference/dot-vendo.md): Every path inside the .vendo directory, which tool writes it, and the exact format contract, from tools.json and policy.json to theme.json and data.
- [Environment variables for Vendo host, sandbox, and peers](https://docs.vendo.run/reference/environment-variables.md): Every environment variable Vendo reads across host process, sandbox runs, and peer providers, with the effect each has on the composition and CLI.
- [Handler options: createVendo config and fetch settings](https://docs.vendo.run/reference/handler-options.md): Every createVendo configuration option and fetch-handler setting, including base path, principal resolution, CSRF policy, and wire error behavior.
- [Headless hooks](https://docs.vendo.run/reference/hooks.md): React hooks from @vendoai/ui share a { data, error, isLoading, refresh } contract with optional polling for threads, apps, approvals, and grants.
- [HTTP routes: threads, approvals, MCP door, and OAuth](https://docs.vendo.run/reference/http-routes.md): Reference for every HTTP route Vendo mounts under the base path, including methods, body shapes, responses, and streaming for the wire.
- [Server API reference for @vendoai/vendo composition](https://docs.vendo.run/reference/server-api.md): Server-side reference for @vendoai/vendo: the createVendo composition, Vendo interface, fetch handler, Next.js adapter, and host-event seam.