3,283 tools, each with the route SHAI actually has

An email inbox API for agents, self-serve on an API key (am_..., Console -> API Keys). At connect time the platform creates one inbox for the tenant on the tenant's own key and registers the inbound webhook, storing both on the connection row; the comms hub then delivers approvals and needs-you items by email from that address with the SMS ladder's wording plus the AI disclosure, and a YES / NO reply decides the approval exactly as by text. A SHAI-native adapter (inboxes.create, messages.send, messages.list, webhooks.create) plus an official OAuth MCP server. Not on the owner's integrations list, so it has no /integrations page.

Without it: Nothing: the ladder is platform chat -> SMS -> call exactly as before, and a tenant with no AgentMail row is byte for byte as today.

Amazon's voice assistant and Echo devices. Confirmed live 2026-09-20: Amazon publishes no consumer-authorizable API through which a third party can list, read or control the devices in a person's Alexa account or run their routines — every documented path runs the other way (Alexa calls a device maker's add-on; routine custom triggers are an enrol-by-e-mail developer preview; Smart Properties is partner-only). Password-based community bridges are excluded under the compliance rules.

Without it: Nothing that Home Assistant or SmartThings cannot do — /smart-home reaches Alexa-visible devices through the hub the user exposes to Alexa, and routines the user creates in the Alexa app keep running; SHAI does not fire them.

A separate, per-token-billed Anthropic account/key the platform worker uses via the Claude Agent SDK to run skills on the user's behalf.

Without it: The platform cannot execute any skill for that tenant.

Second named data vendor — marketplace of pre-built Actors for Instagram/Facebook/LinkedIn/web data, billed by compute unit plus proxy usage.

Without it: Same gap as Bright Data — needs-connector: apify recorded.

UGC-style ads with AI actors - script, actor, voice, generated talking-actor video - through a documented OpenAPI (HTTP Basic with a Client ID / Secret the customer generates under Settings > Public API), PLAN-GATED: the Terms in force since 2026-08-21 restrict the API to a Customized offer (Pro, via sales). A SHAI-native adapter; an optional, quote-first route in /ad-creatives. Not on the owner's integrations list, so it has no /integrations page; connectable on /connections from this row.

Without it: Nothing: /ad-creatives' image route and its /new-edit handoff run as before; on a Starter/Creator plan the card says the API is not on your plan and stores nothing.

One API-key self-serve API that publishes and schedules to fourteen networks including TikTok, Instagram, Facebook, YouTube, LinkedIn, X and Pinterest, with per-client profiles on its Launch/Business/Enterprise plans. The route that lets SHAI own upload -> edit -> caption -> schedule end to end; a SHAI-native adapter (post.create, post.schedule, post.delete, profiles.read, history.read) plus Ayrshare's official hosted MCP server at https://api.ayrshare.com/mcp. On the owner's integrations list (entry 528), so it keeps its /integrations page.

Without it: Nothing stops: /publish-edit delivers files plus metadata as today and TikTok stays on the Higgsfield route; /organic-content-creator posts through GHL's Social Planner as before.

One of three named data vendors for /lead-list-builder's public lead datasets and scraping infrastructure, under Bright Data's terms and the target platform's terms.

Without it: No live scrape or vendor dataset pull; filter capture and output schema still deliver. needs-connector: brightdata recorded.

The user's own Claude.ai subscription for running skills in Claude Code on their own account.

Without it: Nothing runs in Claude Code at all.

The authentication provider the platform's own web app uses for sign-in (email + Google + GitHub OAuth) and its owner/admin/member roles.

Without it: Nothing locally — with CLERK_SECRET_KEY unset the platform runs its test auth provider and every session is the fixture tenant. A real deployment cannot sign anyone in.

The integration platform behind SHAI's one-click connections: it runs the OAuth hop for 1,500+ apps, holds the refresh token, and executes an action on the connected account's behalf. It is the platform's own connector rather than a per-skill one — the owner sets one key on the deployment and every tenant then connects their own accounts through it, per business. The five tools with no catalog app (GoHighLevel's agency API, Twilio, Higgsfield, OpenArt, cutroom) keep the pasted-key path, which is unchanged.

Without it: Nothing that works today stops working: every tool is still connected by pasting its key in Setup, which is how all 33 rows here have been connected since Phase 5. What is missing is the one-click OAuth path — a non-technical owner has to find and paste an API key for each app, which is the step they most often stall on. GET /api/healthz says "no provider configured" in words.

AI video ads - a video from a product URL, an AI avatar clip from text or audio, AI shorts from a script, custom-template renders - through a self-serve API-key pair (X-API-ID / X-API-KEY, pasted colon-joined) that needs an API subscription, plus an official OAuth MCP server. A SHAI-native adapter; an optional, quote-first route in /ad-creatives. Not on the owner's integrations list, so it has no /integrations page; connectable on /connections from this row.

Without it: Nothing: /ad-creatives' image route and its /new-edit handoff run as before.

The standalone video-editor application built in its own private repo (Contract B §4b, mode BOTH) — not part of this platform or this monorepo, shares no code, data, or client folders with either. Listed here so a tenant sees it exists; nothing in this platform calls it.

Without it: Nothing in this platform. The six OPERATE editing skills (/new-edit and the rest) already run the video-editor squad here, on the file-based EDL; Cutroom is a separate product for the same editing surface, not this platform's dependency.

The tenant's own DeepSeek key, reached through DeepSeek's own OpenAI-compatible API. Routed work only.

Without it: Nothing stops. A policy that names DeepSeek without this key parks that step as needs-connector: deepseek.

Where SHAI lives in Discord (Contract C item C22): /shai in a channel it has been invited into or in a direct message, approvals as buttons that resolve the same approval row the dashboard, SMS, voice, Slack and Teams resolve, files and page links posted back as links, and scheduled tasks delivered to a channel. Every reply is ephemeral by default, because a Discord server is usually a room full of people who did not ask.

Without it: @SHAI reaches nothing in Discord and no approval can be pressed there. The dashboard, chat, SMS, voice, Slack and Teams are unaffected and every approval is still decidable in all of them.

The tenant's own ElevenLabs key, so SHAI's replies in the portal are spoken by the Flash model (eleven_flash_v2_5) streamed from ElevenLabs' own text-to-speech endpoint, and so a phone call through Twilio's ConversationRelay names the same ElevenLabs voice. Optional: with no key the free browser voice speaks exactly as before (C23).

Without it: Nothing stops. With Settings -> Voice on the free browser voice nothing here is read. With Settings -> Voice set to ElevenLabs and no key, the portal's spoken reply parks as needs-connector: elevenlabs and says so on the panel - it never falls back to the browser voice silently - and a call uses Twilio's documented default voice.

A reseller portal for AI phone receptionists (XRAY scans, deployed lines, recordings and summaries). Its own llms.txt, read 2026-09-20, states "There is no public API and no MCP endpoint - Exelo is an authenticated partner portal"; /api, /docs, /developers and /openapi.json answer 404. No adapter is built; the guide row carries the click-by-click portal checklist as a manual-fallback unit and SHAI never scripts the portal. It overlaps /voice-agent-builder. Not on the owner's integrations list, so it has no /integrations page.

Without it: Nothing: no skill routes to it.

The tenant's own Fish Audio key, so SHAI's replies in the portal are spoken by Fish Audio's text-to-speech endpoint (POST https://api.fish.audio/v1/tts, chunked audio, model header s1 / s2-pro / s2.1-pro). Portal only: Twilio's ConversationRelay carries Google, Amazon and ElevenLabs voices and not Fish Audio, so a Fish Audio tenant's calls use Twilio's documented default voice and Settings -> Voice says so.

Without it: Nothing stops. With Settings -> Voice on the free browser voice nothing here is read. With Settings -> Voice set to Fish Audio and no key, the portal's spoken reply parks as needs-connector: fishaudio and says so on the panel - never a silent fall back to the browser voice.

Hosts the user's private SHAI instance repo (via the SHAI GitHub App), every client website repo, and release-repo access grants.

Without it: No instance repo can be created; no client website repos.

The CRM the owner's businesses run on: rung 3 of both notify ladders, rung 2 of the scheduler ladder, and the home of every S6 skill.

Without it: Every S6 skill is needs-connector: ghl and cannot run; the S1 skills lose only their sending rung, not their plan.

Google's official API for creating and managing Search/Display/Performance Max campaigns via CampaignBudgetService + CampaignService, batched through GoogleAdsService.Mutate with temporary resource names.

Without it: setup/plan still deliver in full; launch holds at needs-connector: google_ads.

The tenant's own Gemini key, reached through Google's own OpenAI-compatibility layer. Routed work only, for the reason the OpenAI row gives.

Without it: Nothing stops. A policy that names Google without this key parks that step as needs-connector: google.

The calendar /life-planner (S1 Life OS) writes to — rung 1 of the calendar ladder (tools/gcal.py); GHL is rung 2.

Without it: tools/gcal.py falls back to its local store — every merge and conflict resolution still runs, but nothing lands on a real external calendar; the report says planned, never written.

Google's official Device Access API for a person's own Nest thermostats, cameras, doorbells and displays: real, documented and user-authorizable, but only on the user's own Device Access project (a one-time US$5 registration), through an OAuth client in the user's own Google Cloud project, and for personal use only. Manual-fallback today: the platform runs no OAuth flow against a user-supplied client yet. Not on the owner's integrations list, so no /integrations page.

Without it: Direct Nest reads and commands park as a manual-fallback unit with the row's checklist; the same devices work through the user's own Home Assistant Nest integration if they have set it up there.

The real performance-measurement API /site-speed (#94) uses for before/after scores. Confirmed live 2026-09-08: a keyless call to pagespeedonline.googleapis.com/pagespeedonline/v5/runPagespeed returns HTTP 429 (quota_limit_value: 0 for the default per-project daily quota) -- a Google Cloud API key is required even though the API itself has a generous free tier once one exists.

Without it: /site-speed's Step 2 code fixes still deliver in full; the before/after measurement (Steps 1 and 3) holds until a key is connected -- never a guessed score.

Google's own API for a site's search performance — the real data /seo (#92) reads instead of an invented ranking figure.

Without it: Live query/impression/position data; the rest of an SEO pass still runs.

Avatar video from a script - HeyGen's stock avatars, a photo avatar, or a digital twin of a real person - through a self-serve API key (X-Api-Key) billed to a prepaid API wallet, plus voices, translation and lipsync. A SHAI-native adapter (avatars.read, voices.read, video.create, video.status, video.fetch) behind the likeness-consent gate: no render before a `likeness` row in the client's rights.md and the consent sentence on this connection; every output lands with aigc: true. Also an OAuth MCP server (trial-scale). On the owner's integrations list (entry 1484), so it keeps its /integrations page.

Without it: Nothing stops: the avatar slot parks needs-connector: heygen with its manual fallback, exactly as an unfunded OpenArt slot does.

The video-generation provider the Contract B squad uses for the routes docs/higgsfield-capabilities.md records.

Without it: The Higgsfield-only generation routes; every other stage of an edit still runs.

The open-source home-automation hub a person runs on their own hardware, and the one hub through which every brand they already own is reachable. Its REST API (states, service calls, history) is authorized with a long-lived access token the user creates on their own profile page. The recommended path for /smart-home: connect the hub, not each brand.

Without it: Every read and every command parks with needs-connector: home-assistant (or smartthings in its place); /smart-home still writes its schedule proposals and approval items and says in one line what to connect.

Same partner-gated pattern as OpenTable, checked live 2026-09-08 for /flight-deals (#10), /hotel-deals (#11), /hotel-booking (#12). Booking.com's Demand API requires Managed Affiliate Partner status, a signed contract, and Account-Manager-enabled Partner Centre access before sandbox credentials are issued, and the partner portal is not accepting new registrations as of this check. No major flight-search engine publishes a consumer-authorizable personal API either.

Without it: Nothing — this is the shipped path, not a fallback. /flight-deals, /hotel-deals, /hotel-booking run on WebSearch/WebFetch against airline, hotel, and OTA results pages, real prices cited per run, exactly like /date-ideas and /restaurant-finder need no paid connector; /hotel-booking books through the property's own site, a major OTA's booking flow (a §3.13 UI-only step), or the phone agent.

Mailbox warm-up, sending-domain rotation, sequence builder, and deliverability/reply-tracking platform for cold outbound — distinct from Resend (transactional only).

Without it: Sequence copy and compliance checklist still deliver; no mailbox warm-up, live send, or real reply/deliverability numbers. needs-connector: instantly recorded.

LinkedIn's developer platform: self-service Open Permissions (sign-in, the user's own posting/commenting/liking) plus gated Marketing/Community-Management APIs. Confirmed live 2026-09-08: does not send connection requests, does not send member-to-member DMs, does not search arbitrary member profiles. SNAP (Sales Navigator partner program) is closed to new partners.

Without it: Structural gap, not a missing key: /lead-list-builder mode linkedin and /dm-outreach mode linkedin stay needs-connector (data vendor) / manual-fallback (send) regardless of this connection.

Meta's official API for a business's Instagram professional account and Facebook Page — the compliant path for /social-engagement and /dm-outreach ahead of any third-party tool.

Without it: No like/comment/share or DM through the compliant official path; falls to manual-fallback or needs-connector: meta.

Meta's official API for creating and managing Meta/Instagram ad campaigns (/act_<id>/campaigns, /adsets, /ads) -- distinct scope from the Meta Graph API row (organic DMs/engagement).

Without it: setup/plan still deliver the full structure/calendar; launch holds at needs-connector: meta and nothing spends.

Where SHAI lives in Microsoft Teams (Contract C item C21): @SHAI in channels and group chats it has been added to, direct messages, approvals as Adaptive Cards that resolve the same approval row the dashboard, SMS, voice and Slack resolve, files and page links posted back as links, and scheduled tasks delivered to a conversation. The same surface as Slack, in the other place a team already talks.

Without it: @SHAI reaches nothing in Teams and no approval can be pressed there. The dashboard, chat, SMS, voice and Slack are unaffected and every approval is still decidable in all of them.

The platform's managed Postgres (DATABASE_URL).

Without it: Nothing locally — with DATABASE_URL unset the platform runs PGlite in process behind the same schema and migrations. A deployment loses durability across restarts and cannot run more than one process.

The tenant's own OpenAI key. Used only for the routed half of a run — extraction, summarising, classification, first drafts, checks — never for the orchestrator, which runs only Claude (the Agent SDK does not route to other vendors).

Without it: Nothing stops. A policy that names OpenAI without this key parks that step as needs-connector: openai and the run does that part itself and says so - it never falls back to a more expensive model without asking.

Image/video generation connector for AI logos, walkthrough videos, and aerial flyovers; docs/openart-capabilities.md owns the model policy and credit-cost tables.

Without it: No AI-generated logo and no video (walkthrough/flyover) for a client; the website and non-video services still work.

The tenant's own OpenRouter key - one key that reaches hundreds of models, including open-weight ones no vendor sells directly. This is the only provider SHAI reaches through a first-party AI SDK provider package rather than an OpenAI-compatible base URL.

Without it: Nothing stops. A policy that names OpenRouter without this key parks that step as needs-connector: openrouter.

The reservation-booking API /restaurant-booking (#18) would use to book a table directly instead of a deep link. Confirmed partner-only live 2026-09-08: no self-service developer portal or personal API key; approved partners get OAuth 2.0 sandbox access after a written application, production needs a signed agreement.

Without it: Nothing stops — /restaurant-booking uses the restaurant's own OpenTable reservation deep link or widget URL as the first self-serve path, falling to the phone agent (docs/compliance.md §5) when no online path exists.

Long video in, short clips out. A self-serve organization API key (Pro plan and above) on api.opus.pro/api: clip projects, uploads, exportable clips with titles/hashtags/ranges, collection export, transcripts; plus an official OAuth MCP server. A SHAI-native adapter behind /build-cut's optional clip-finder route - a second opinion from the user's own Opus project; SHAI's own picks stay the default and free. The virality score has no documented REST field and stays needs-probe. Not on the owner's integrations list, so it has no /integrations page.

Without it: Nothing: /build-cut's own Find Viral Clips is the default.

Third named data vendor, metered by execution hours; also sells account-phantom automations that drive a user's own logged-in session (manual-fallback per compliance.md §3).

Without it: needs-connector: phantombuster recorded; no live scrape or account-phantom run.

The Docker host for apps/worker and apps/comms — long-running services an agent run outlives a serverless function on. Fly.io is the documented alternative.

Without it: Platform-mode runs. Claude Code mode is unaffected — it runs on the user's own machine and Claude account.

The email transport behind the notify port; rung 1 of the email ladder in tools/notify.py.

Without it: Nothing stops: the email is planned and logged, and its content still lands in the workspace as a file the user can send themselves.

The subscription backend for mobile apps: overview metrics (MRR, active subscriptions, revenue last 28 days), revenue by date range, charts (actives, churn, trials, LTV), customers and subscriptions, through a self-serve REST v2 secret key with granular read permissions, plus an official OAuth MCP server. A SHAI-native read-only adapter; an optional read of app revenue in /forecasting and /scaling-plan. Not on the owner's integrations list, so it has no /integrations page.

Without it: Nothing: both skills use master.md's numbers as before and mark the app-revenue line unavailable - connect RevenueCat.

Amazon's Ring devices. Confirmed live 2026-09-20: Ring now has an official Partner API at api.amazonvision.com (devices, status, event history, WHEP live video, snapshots, signed webhooks; GA 2025-04-21), but it is reachable only through an app registered on Ring's developer portal by an identity-verified developer — a private app for up to ten accounts or a certified public one — which the account holder then authorizes inside the Ring app by OAuth. No key a person can paste; US-only; the linked account needs a paid Ring plan or a trial. SHAI holds no registered Ring app, so no adapter is connectable today. Not on the owner's integrations list, so no /integrations page.

Without it: 'Who is at the door' is answered by the Ring app, the Ring Alexa skill or IFTTT, not by SHAI; nothing else stops.

The CRM /salesforce-admin (#29) administers through Salesforce's official REST, SOQL, and Tooling APIs only — never scraping, never a browser script against Salesforce's own site.

Without it: /salesforce-admin cannot read or write any real org data — it delivers the Connected-App/OAuth setup steps instead of fabricating a field, object, record, or report.

Samsung's smart-home cloud and hub. Its public REST API lists devices, reads state, sends commands and runs scenes, authorized with a personal access token the user issues on their own Samsung account with the scopes they choose. A PAT issued since 30 December 2024 expires after 24 hours, and free API access ends in October 2026 (a US$4.99/month personal plan is announced).

Without it: Reads and commands park with needs-connector: smartthings when home-assistant is not connected either; nothing else stops.

The 32-byte key the platform seals every stored credential with (AES-256-GCM).

Without it: Storing any credential at all: the layer refuses the write rather than falling back to plaintext.

Checked live 2026-09-08 for /personal-shopper (#14). Google's merchant-facing Content/Merchant API is seller-side only (a store uploading its own product feed), not a consumer price-comparison tool. The consumer side needs no API or account at all — Google Shopping's own public search results and every named retailer's own product-search pages are public pages WebSearch/WebFetch reads directly.

Without it: Nothing — no consumer-authorizable purchase API exists for a personal buyer at any retailer checked, so the actual purchase is always the user's own click on the cited retailer link; this was never a gap a connector could close.

Where SHAI lives in Slack (Contract C item C20): @SHAI in channels, DMs, threads and the Agents surface, approvals as buttons that resolve the same approval row the dashboard, SMS and voice resolve, files and page links posted back, and scheduled tasks delivered to a channel. Also the workspace /chat-agent-builder mode slack (#89) posts into.

Without it: @SHAI reaches nothing, no approval can be pressed in Slack, and no task can be delivered to a channel. The dashboard, chat, SMS and voice are unaffected and every approval is still decidable in all of them.

The payments provider the one question deferred (line 5: no Stripe in v1).

Without it: Nothing in v1. "Cash collected" stays honestly unavailable in /ads-metrics and /outreach-metrics for want of a payments connector.

The SMS and voice transport behind the notify port (tools/notify.py); rung 1 for sms, the only rung for call.

Without it: Nothing stops: notify.py plans and logs the message; the deliverable becomes calendar events plus schedule.md instead of a self-firing text.

The Redis behind the platform's BullMQ queue and its run-log pub/sub (REDIS_URL).

Without it: Nothing locally — with REDIS_URL unset the platform runs an in-memory queue implementing the BullMQ subset the worker uses. A deployment loses queue durability and cross-process streaming.

Same partner-gated pattern as OpenTable and the OTAs, checked live 2026-09-08 for /car-buying (#13). Autotrader's own REST APIs (listings, VIN/VRM lookups, valuations, finance-product integration) are sold to dealers and finance partners, not individual consumers; TrueCar publishes no public API at all. No auto lender exposes a consumer-authorizable API that originates a loan or places an order on a named person's behalf.

Without it: Nothing — this is the shipped path. /car-buying runs on WebSearch/WebFetch against dealer and marketplace listing pages plus a real published rate table (Experian's quarterly report) for financing, exactly like /hotel-deals/flight-deals need no paid connector for pricing. The actual purchase, financing application, and negotiation are the user's own, handed back as an exact next-steps checklist.

Hosts the platform itself and every client website /build-website deploys, under the running user's own connected team.

Without it: No client website can go live; the platform itself cannot be deployed.

The VSL video host and player. Its ONE public customer API is the read-only Analytics API (analytics.vturb.net, X-Api-Token + X-Api-Version: v1): players, quota, session stats, play rate, pitch retention, conversions, revenue, traffic origin, A/B comparison groups. No upload, embed-code or player-settings endpoint exists - those are dashboard steps handed over as manual-fallback units. A SHAI-native read-only adapter; /vsl-script reads hosting analytics back through it. Not on the owner's integrations list, so it has no /integrations page.

Without it: Nothing: the script package delivers in full and the read-back section says unavailable - connect VTurb.