Docs
Using AI Drops for Business
Everything on one page. Questions this does not answer go to support.
Setup
Go to /onboarding and choose Add to Slack. Approve the scopes in Slack.
Pick the channels to post to and the feeds each channel follows.
To post in a private channel, invite the app there first with /invite @AI Drops.
Channel rules
Each channel has its own rule: which labs and products it follows, which update types (releases, new models, incidents, usage limits, new commands, deprecations), a minimum importance, keyword filters, a schedule and quiet hours.
Keyword filters and quiet hours need the Team plan or above. Change rules any time under Dashboard, Channels.
Quiet hours hold real-time posts until the window ends. Incidents skip quiet hours and post straight away. You can also hold posts over the weekend.
The /drops command
/drops latest shows the five newest drops, only to you. Add claude, openai or cursor to limit it to one lab.
/drops pause 1h, 1d or 1w pauses posts to the current channel. Drops published while paused are skipped, not saved for later. /drops resume turns posting back on.
/drops digest now posts the current channel's waiting digest, including anything held by quiet hours.
/drops settings links to the dashboard. /drops help lists the commands.
Digests
A channel can post in real time, as a daily digest or as a weekly digest. Pick the hour, and for weekly digests the day. Daily digests can skip weekends.
A digest is one message with the held drops sorted by importance, up to 40 shown, with a link to the full list.
In a digest channel everything waits for the digest, incidents included. Send status incidents to a separate real-time channel if people need them live.
Weekly digests need the Team plan or above. Daily digests work on every plan.
Webhooks
On Business and Enterprise, add a webhook URL under Dashboard, Integrations. Each drop or digest is a JSON POST with the headers X-AIDrops-Timestamp, X-AIDrops-Signature and X-AIDrops-Event (drop or digest).
The signature is v1= followed by the hex HMAC-SHA256 of the timestamp, a period and the raw request body, keyed with your webhook secret. Recompute it, compare, and reject timestamps older than five minutes.
Failed deliveries are retried and appear in the delivery log. A 404, 410, 401 or 403 response pauses the destination until you fix the URL.
API overview
Business and Enterprise plans can create API keys under Dashboard, API keys. Send the key as Authorization: Bearer aid_...
Endpoints under /api/public/v1 list drops (and fetch one by id), your destinations and your delivery history. The OpenAPI description is at /api/public/v1/openapi.json.
Keys can be revoked at any time. Each key is limited to 120 requests a minute across the REST API and the MCP server; over the limit you get 429 with Retry-After. The MCP server is at /api/mcp and takes the same key.