Choose the right integration path first.
If you start with the correct package, the rest of the implementation becomes much simpler. Use this page to pick the right path for your framework, runtime, and product goals.
Choose by framework
Next.js app
Use @serviceagent/nextjs when you need chat, booking, voice, webhooks, and server-side access in one package.
React or Vite app
Use @serviceagent/react when you want prebuilt UI components and the fastest frontend integration path.
Node.js or server runtime
Use @serviceagent/sdk for server-side APIs, automations, knowledge base search, analytics, and CRM sync.
Cursor or Claude workflow
Use @serviceagent/mcp when you want AI coding tools to provision and configure ServiceAgent directly.
Choose by product goal
Add chat to an app or website
Start with @serviceagent/nextjs or @serviceagent/react.
Add booking and scheduling
Use the framework package for your frontend and keep the booking key in environment configuration.
Build low-latency voice or dialer flows
Use @serviceagent/aiva-sdk for custom voice, transcripts, summaries, and call intelligence experiences.
Connect backend workflows or internal tools
Use @serviceagent/sdk to call APIs from your own services and background jobs.
Choose by level of control
- Want the fastest path? Use @serviceagent/cli.
- Want framework-native components? Use @serviceagent/nextjs or @serviceagent/react.
- Want server-side API control? Use @serviceagent/sdk.
- Want full control over voice UI and transport? Use @serviceagent/aiva-sdk.
- Want a copy-ready coding agent brief? Use the prompt builder.