npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@guidify-ai/vapi-studio

v0.1.1

Published

Vapi Studio — deterministic voice agents for Vapi (NestJS)

Readme

Vapi Studio

@guidify-ai/vapi-studio — a code-driven toolkit for Vapi.

Website: vapi-studio.guidify.ca — coming soon

This repo is the framework (npm package). Your bot is a separate NestJS app — start from the public starter below.


Create a new project

yarn start alone is not a full setup — fill credentials for your path first. Full checklist: Quick start.

git clone [email protected]:guidify-ai/vapi-studio-project.git my-bot
cd my-bot
cp .env.example .env
# Required for live voice: VAPI_API_KEY, POC_ASSISTANT_ID, VAPI_PHONE_NUMBER_ID
# Optional: TWILIO_* (SMS / Twilio-imported number), OPENAI_API_KEY|ANTHROPIC_… (leave MockBrain otherwise)
# Always: PROJECT_NAME=…  (PROJECT_SLUG optional)
yarn install
yarn start   # Docker + Postgres + ngrok → prints URLs (fails closed without Vapi trio)

Wire Vapi to the printed URLs:

| Setting | URL | | --- | --- | | Webhook | {PUBLIC_BASE_URL}/vapi/webhook | | Custom LLM | {PUBLIC_BASE_URL}/vapi/chat/completions |

Requirements: Node 22+, Yarn or npm, Docker Compose, ngrok, a Vapi account for live calls. Twilio and an LLM key only when you leave dry-run SMS / MockBrain.

Showcase (not a blank starter): vapi-studio-landing-page-sample-model — Planner LLM demo.


Repos

| Repo | Role | | --- | --- | | This package | guidify-ai/vapi-studio → @guidify-ai/vapi-studio on npm | | Starter | guidify-ai/vapi-studio-project — fork this to ship a bot | | Showcase | guidify-ai/vapi-studio-landing-page-sample-model — full Planner sample |

Self-hosted and Dockerized. No Guidify-hosted runtime. Vapi is the voice channel; your app is the Custom LLM + webhook endpoint.


Tools

| # | Tool | Status | Summary | | --- | --- | --- | --- | | 1 | Vapi Studio | Shipped | Deterministic agents — typed steps + flow.yaml. Supervisor routes every turn; Brain only at listen boundaries. | | 2 | Conversation events | Shipped | Event-driven bus — onStudioEvent + Nest eventListeners. Build any custom logic on the hooks; Guidify tools use the same surface. | | 3 | Vapi Custom Transcriber | Coming soon | Controllable ASR for digit listens, names, and constrained extracts — fewer junk transcripts as PII. | | 4 | Vapi Voice Profiles | Coming soon | Reusable voice + persona packs for Vapi assistants — consistent brand sound across flows. | | 5 | Vapi Integrations | Coming soon | Signed outbound hooks to CRM and tools — BYOK wiring without leaking provider protocols into Nodes. | | — | And more | Coming soon | More controllable surfaces for Vapi — same self-hosted stack, same graph-owned philosophy. |

Vapi Studio — Introduction · Concepts · Runtime API.

Conversation events — Events & logging · Extending events.


How it fits with Vapi

Vapi Studio assistants are Custom LLM + webhook endpoints — fully compatible with ordinary Vapi assistants:

| # | Mode | When to use | | --- | --- | --- | | 1 | Single-assistant flow | New bots. One Vapi assistant; the graph lives in Studio (flow.yaml + nodes). | | 2 | Multi-assistant Squad | Several Studio-backed assistants in one Squad. See Workflow & Squad. | | 3 | Inject into an existing Squad | Mix Studio and native Vapi members in Squads you already run. |

Most greenfield work starts with (1) via the starter clone above.


How multi-intention routing works

One listen can surface several competing intentions. Main path left → right; portal nodes on a row below.

Supervisor picks the next agent step each turn (scores intentions, checks portals, follows flow.yaml).

| Shape | Meaning | | --- | --- | | NODE | Agent step — speaks, listens, writes memory | | PORTAL NODE | Global interrupt (portal: true in flow.yaml) | | INTENTION | Routing signal on an edge |


Contribute to the framework

Only when changing this library (not when starting a bot):

git clone [email protected]:guidify-ai/vapi-studio.git
cd vapi-studio
yarn install && yarn build && yarn test

See CONTRIBUTING.md — architectural PRs require an ARD under docs/ards/ (SpecKit under .specify/).


Documentation

| | | | --- | --- | | Create a new project | Starter · Creating an app | | Showcase | landing-page-sample-model · Example apps | | Doc site index | docs/README.md | | Runtime handbook | docs/reference/runtime-api.md | | Best practices | docs/best-practices/ | | ARDs | docs/ards/ | | SpecKit | .specify/ · docs/guides/speckit.md | | Env presets | .env.example |

License

MIT — see LICENSE.