Placet supports four connection types for agent integration. You can use them independently or combine them.Documentation Index
Fetch the complete documentation index at: https://docs.placet.io/llms.txt
Use this file to discover all available pages before exploring further.
Comparison
| Feature | MCP | REST API | WebSocket | Webhooks |
|---|---|---|---|---|
| Best for | AI coding agents | Scripts & apps | Persistent agents | Background jobs |
| Latency | Real-time (poll) | Up to 30s (poll) | Real-time (push) | Near real-time (push) |
| Persistent connection | Per-session | No | Yes | No |
| Agent needs public URL | No | No | No | Yes |
| Protocol | MCP over HTTP/stdio | HTTP REST | Socket.IO | HTTP callback |
Choosing a Connection
I'm using an AI coding agent (Claude Code, Copilot, Cursor)
I'm using an AI coding agent (Claude Code, Copilot, Cursor)
Use MCP. The Placet MCP server exposes all capabilities as tools that AI assistants can call directly. Configure your IDE with a one-line config.
I'm writing a script or simple integration
I'm writing a script or simple integration
Use the REST API. Send messages via HTTP, poll for responses with
long-polling. Works from any language with zero dependencies.
I'm building a persistent agent that reacts in real-time
I'm building a persistent agent that reacts in real-time
Use WebSocket. Connect via Socket.IO, subscribe to channels, and
receive instant push events when humans respond.
I'm running background automations (CI/CD, cron)
I'm running background automations (CI/CD, cron)
Use Webhooks. Set a webhook URL and let Placet push responses to your
server — your automation doesn’t block while waiting.
I just want to send notifications without waiting
I just want to send notifications without waiting
Use fire-and-forget via the REST API:
POST /api/v1/messages without a review field. No response mechanism needed.