Integrations
Per-provider pages for every integration Vendo brokers — what it is, which auth modes are supported, env vars exposed at runtime, proxy endpoint, and code examples.
Vendo brokers OAuth flows, BYOK credentials, and shared upstream keys for the providers below. Pick one to see its auth profiles, the env vars Vendo injects at boot, the proxy endpoint (when applicable), and a vendo.token(...) snippet in Python / TypeScript / Swift.
For the platform-wide picture — how connections, bindings, and the proxy interact — see Concepts: connections & integrations and Infrastructure: the proxy.
Available providers
The list below is auto-generated from the monorepo's packages/integrations/<slug>/catalog.json files (enabled entries only). Every link points to a generated per-provider page; the prose on each page is hand-written.
Anthropic
Claude family of models. Vendo holds the upstream credential and bills per token (including cache reads / writes) through the proxy.
AssemblyAI
Speech-to-text transcription. Vendo holds the upstream credential and bills per hour of audio.
ElevenLabs
Realistic text-to-speech and speech-to-text. Vendo holds the upstream credential and bills per character (TTS) or per second of audio (STT).
Google Gemini
Gemini family of models. Vendo holds the upstream credential and bills per token (including cached input) through the proxy with a route allowlist on /v1beta/models.
Publish posts, read comments, and view analytics on Instagram
MuAPI
Image and media generation. Vendo holds the upstream credential and bills per generation.
Notion
Read & write Notion pages and databases via the official OAuth app install flow. Tokens never expire; no refresh strategy.
OpenAI
GPT family of models. Vendo holds the upstream credential and bills per token through the proxy with a route allowlist on /v1/chat, /v1/responses, /v1/embeddings.
OpenRouter
Unified API for hundreds of LLMs. Vendo holds the upstream credential and bills per token through the proxy.
Supabase
Manage Supabase projects (admin)
Telegram
Telegram Bot API. Tenants connect by uploading their bot token; Vendo verifies via getMe, registers a webhook, and forwards inbound updates to the deployment.
How a provider gets here
Each enabled packages/integrations/<slug>/ entry ships with one or more auth profiles — vendo_managed_pool (Vendo holds the key), byok_static (you upload yours), oauth_app_install / oauth2 (per-user OAuth), or composio_managed (brokered through Composio). The per-provider page lists which profiles are wired up and which one is the default.
The runtime env-var contract for each integration — the env vars Vendo injects into your deployment when you bind a connection — comes from packages/integrations/<slug>/integration.ts::connectionEnvVars. The "Environment variables" table on each page is generated directly from that source, so it stays in lockstep with what the deploy worker actually writes.
Adding a new integration
Integrations come from the monorepo's packages/integrations/<slug>/ modules — one folder per slug, with catalog.json (metadata + auth profiles), integration.ts (env-var contract + adapter wiring), and optional connect.ts / adapter.ts / webhook.ts. Composio-bridged providers (Instagram, Supabase today) live under the same path and additionally declare a composio_auth_config_id in their catalog. To propose a new one, open an issue on runvendo/vendo with: provider name, what tools would consume it, and which auth profiles the provider supports.