Your backend, your helpdesk, your data.
Capabilities map to your own endpoints. Hand-offs land in Peeve Hand-Offs; on Growth and up, a hand-off can also open a Zendesk ticket or a Linear issue. Nothing about Peeve is a separate silo.
Pre-built connectors, on Growth and up: Stripe · Slack · Zendesk · Linear · HubSpot · Salesforce · Cal.com.
Beyond answers: look things up and take action in your systems.
Peeve doesn't just answer from a help center. Connect your own tools two ways (your MCP server or any REST API), and mid-conversation it reads live data (an order, an invoice, an account status) and takes real actions for your customers. No SDK, no integration project: minutes, not weeks.
Turn your existing REST API into something the assistant can use, built automatically from your API docs.
Already run an MCP server? Peeve plugs straight into it. Your internal tools become things the assistant can do for customers.
Every tool Peeve works with.
Connectors are available on Growth and above. A one-time import from another tool is included on every plan.
Wiring a connector? Peeve shows the user, right on the screen.
The cursor moves to the control, highlights it, and states the scope before anything runs, inside your product, in the user's own session.
Where do Peeve hand-offs go?
Hand-offs land in Peeve Hand-Offs, where your team picks them up with the full session: the intent, every step attempted, its confidence and a replay. Peeve is the AI layer of your support: an AI customer support agent that resolves requests inside your product and hands the rest to a person with the full session. On the Growth plan a hand-off can also go to Zendesk as a ticket, notify Slack, email or a webhook, and log a bug as a Linear issue.
How do capabilities map to my backend?
Each capability points at one of your own endpoints, defined in peeve.config.json and reviewable in a pull request. The model requests the capability by name; your execution service makes the actual call with your credentials, which the model never sees.
Do I need to build an integration to use my own REST API?
No. Paste your API docs URL and Peeve builds the connector for you: base URL, authentication and every endpoint, each marked read or write for review. Add your credentials (encrypted per workspace) and the assistant can use it in conversations. It's minutes, not an engineering project, and the connector tracks your docs; you review and toggle it endpoint by endpoint. Available on Scale.
Can Peeve connect to my own MCP server?
Yes, on Growth and up. Paste your MCP server URL (and a token if it needs one); Peeve does a live handshake, discovers the tools it exposes, and you choose which ones the assistant may use. Reads happen automatically; anything that changes state runs through a confirmation step. It's an advanced option for teams that already run an MCP server. Most customers never need it.