Set up Raindrop using raindrop.ai/auth.md
raindrop.ai/auth.md
How it works
- Unclaimed org. Signup creates an org on the Hobby plan with no members. Its write key can send events, but nobody can sign in to read them.
- Claim link. The link is valid for 72 hours. The first person who signs in through it becomes the org’s Owner. If nobody claims the org in 72 hours, the link and the write key are disabled.
Sign up
Run this in the project root:- create-raindrop
- HTTP API
--org-name is required and allows letters, numbers, spaces, and underscores. The command writes RAINDROP_WRITE_KEY to ./.env, adds .env to .gitignore, and prints the claim link. It does not print the key, and it does nothing if RAINDROP_WRITE_KEY is already set.raindrop-setup skill and send one real interaction through it.
Check the integration
About 30 seconds after the interaction, check the newest event:- create-raindrop
- HTTP API
0 means healthy, 1 means it needs attention (the command prints the checks and a fix prompt), and 2 means no events have arrived yet.- The user message is clean: only the current turn, as plain text.
- The assistant response is complete: the text the user saw, not a raw provider response.
- Tool calls appear in the trace.
- Tool inputs and outputs are readable.
healthy.
The check works only for an org created through agent signup, until someone claims it. Other write keys get
403. After the claim, review the integration on the Get started page.Claim the org
The agent gives you the claim link, which looks likehttps://app.raindrop.ai/claim#…. Open it, sign in or sign up, and select Claim. The page shows when the org was created and how many events it has, so you can confirm it’s the one your agent set up.