The developer experience isn't an afterthought.
Frigade is built by a team of developers, so the API, the controls, and the docs come first, not last. A few lines to drop in, with a real surface underneath. Launch it from any event, wire it to the actions you've already built, pass in roles, redact fields, and theme it so it feels native.
// Launch Frigade from any buttonbutton.addEventListener("click", () => {frigade.ask({prompt: "How do I export invoices?",role: user.role,})})
Control every part of the assistant.
Ask API
Open the assistant from any event or button click, with the prompt and context you choose.
Tool calling
Let it run the actions your engineers already built, so it does the work instead of describing it.
Support handoff
Escalate to Zendesk, Intercom, or HubSpot with the full conversation attached.
Event listeners
Hook into opens, messages, and resolutions to trigger your own logic and analytics.
Dynamic permissions
Pass the user's role so the assistant only sees and does what that user is allowed to.
Data privacy
Redact fields so sensitive data never leaves your app or reaches the model.
Preferences
Decide whether it shows by default, per user or globally, and override it at runtime.
Native theming
Inherit your colors, type, and spacing so it looks like part of your product, not a bolted-on widget.
Go fully headless.
Build the assistant exactly to your spec with your own components, while Frigade's engine, training, tool calls, and handoff run underneath. All the control of building it yourself, without the parts you'd rather not maintain.
A script tag, or the package. Your call.
Drop in a script tag and you're running, or install the package and import it into your app. It works with React, vanilla JS, modern SPAs, and server-rendered apps.
Two ways to guide users.
Frigade AI learns your product and guides users in real time. When you want to script an exact flow, sequence, or announcement, the developer-friendly Frigade Engage line gives you deterministic control. Same platform, two complementary ways to build.
The pieces developers reach for most.
The API surface is how teams wire Frigade into real workflows and the rest of their stack.