Approval Gates Over the API: Safe Writes for Any Agent
How Zevari's approval gate works over the REST API - stage a write with confirmations.requestAction, a human approves, then you execute. A self-hosted agent cannot send unattended.
Why the gate exists
An autonomous agent that can send on LinkedIn unattended is a banned account waiting to happen. Zevari inverts it: the agent does all the research and drafting, then stops at the gate, and a human approves before any write executes. This works the same whether the agent is Claude over MCP or a self-hosted bot over REST.
The three-step handshake
- 1. Stage
Call confirmations.requestAction with the action_type that matches the write you intend. You receive a confirmation id.
- 2. Approve
The human approves out of band - in chat, Slack, a daily digest, or via an approval endpoint - which flips the confirmation to approved.
- 3. Execute
Call the actual write endpoint referencing the approved confirmation. Without an approved confirmation, the write is refused.
Which actions are gated
LinkedIn writes (connection request, message, comment, post), content publishing, and campaign launches are gated, along with anything outbound or paid. Reads - search, score, draft - are not gated.
Polling vs webhooks
A headless or self-hosted agent learns a confirmation was approved by polling the confirmation status or by receiving a notification, then proceeds to execute. Until then, it waits.
Why this matters for self-hosted agents
OpenClaw and Hermes Agent run 24/7 on a VPS. The gate guarantees no unattended sends - the difference between this and cookie-driven tools that advertise no approval required.
Docs Links
- Help Center
Human-facing guide to Zevari skills, workflows, agents, videos, safety, and support.
- Workflow Guide
LinkedIn outreach, content, prospect research, audience analysis, campaign, inbox, and GTM workflows for Claude.
- Prompting Guide
Copy-ready prompts that require AI assistants to read the MCP reference before acting.
- Workspaces and Sender Seats
Human-facing setup guide for workspaces, members, billing, add-on LinkedIn sender seats, and teammate LinkedIn connections.
- Safety Center
Human-facing guide to Zevari safety guardrails, warm-up, pauses, blocked actions, and recovery state.
- Warm-Up
Human-facing guide to LinkedIn sender warm-up and gradual activity ramping.
- API Playbooks
Ordered REST call flows for developers and AI agents using the Zevari API.
- MCP Reference
Agent-facing tool schemas, capability contracts, examples, gotchas, and recovery guidance.
- API Reference
Public REST API reference powered by the Zevari OpenAPI document.
- MCP Reference JSON
Machine-readable MCP tool reference.
- LLMs Full
AI-readable Zevari documentation bundle.
- Support
Send bug reports, support handoffs, and feature requests.