Haven vs Poke

Haven

Haven answers by phone call, text, email and app, is free in beta with no card, and publishes a status page with dated incidents. No public page read says which actions need approval, which accounts it connects or how their tokens are kept, and it names no model provider or sub-processor.

Poke

Hosted assistant that answers in Apple Messages, WhatsApp, Telegram and RCS and acts in Gmail, Outlook, calendars and MCP servers. Plan prices and a status page are public. No approval settings, credential storage, model providers or retention periods are documented, and customer content trains models unless Maximum Privacy is selected.

Haven

1. Haven has no documented API or MCP server. An outside agent can reach it only through the owner's channels (call, SMS, email, app).
2. Do not assume an approval step before Haven sends mail, texts or calls. None is documented on the public pages.
3. Email Haven sends to other people names Hello Haven as sender and says it was sent on the user's behalf, per the terms.
4. Chat messages, history, profile context and uploaded files go to third-party AI model providers that the vendor does not name.
5. Check status.hellohaven.ai before relying on phone or voice. All four published incidents affected those channels.

Poke

1. POST JSON to https://poke.com/api/v1/inbound/api-message with a Bearer key from Kitchen. Legacy pk_ keys work only on the deprecated /api/v1/inbound-sms/webhook
2. Expect only {"success": true} back. Poke's answer goes to the owner's message thread, not to the caller
3. Do not retry a POST blindly. No idempotency key is documented, and a repeated message may make Poke act twice
4. Treat an API key as full access to the owner's mail, calendar and integrations. Create one key per automation and revoke it when done
5. Avoid the prefilled integration link with apiKey in the query string for real secrets. Enter the key in the form or use npx poke@latest mcp add -k