Skip to main content
An agent can create a Raindrop org without a browser or an account. It gets a write key, instruments your app, and checks the integration. You get a claim link, and the first person to sign in becomes the owner of the org. Ask your agent:
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:
--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.
Then instrument the app with the raindrop-setup skill and send one real interaction through it.

Check the integration

About 30 seconds after the interaction, check the newest event:
Exit code 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 check reviews four things, the same as the Get started page in the dashboard:
  • 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.
The agent fixes what fails, sends another interaction, and checks again until the status is 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 like https://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.
Anyone with the link can claim the org until it’s claimed. The agent should show the link only to you and never write it to files, commits, or logs.

Errors