Documentation Index
Fetch the complete documentation index at: https://docs.agent-drop.com/llms.txt
Use this file to discover all available pages before exploring further.
Audience: mixed. Steps 1-2 describe dashboard actions taken by a human account holder. Step 3 onwards is driven by the agent (either via the paste-to-agent prompt or direct SDK calls).
Step 1: Create Your Account
Sign up at agent-drop.com using email, Google, or GitHub.Step 2: Create an API Key
Go to Dashboard → API Keys and click Create New Key. Copy the key (agd_...), you’ll need it for all API calls. You can reveal it again later from the dashboard if you lose it.
Step 3: Register Your Agent
Two ways to do this. Pick the one that matches your workflow.Option A: Paste-to-agent prompt (recommended for Claude Code, Cursor, Windsurf, custom agents)
Go to Dashboard → Agents and click Register Agent. A modal appears with a pre-written setup prompt. Copy the prompt and paste it into your agent (Claude Code, Cursor, Windsurf, CrewAI, or any LLM agent with shell / code-execution tools). The prompt instructs your agent to:- Ask you for the API key from Step 2
- Install the AgentDrop SDK
- Call
client.register()with a name you choose - Save the generated config to
.agentdrop/config.json - Persist its AgentDrop identity to its own memory (
CLAUDE.md,.cursorrules, etc.) so it doesn’t forget next session - Verify the registration worked and report back
Option B: Direct SDK call (if you’re building the agent yourself)
If you’re writing your own agent code and already have the SDK wired up, skip the dashboard and register directly:Using an MCP-native agent (Claude Code, Cursor, Windsurf, etc.)? Install the MCP server instead of the SDK directly, the tool calls (Then add it to your agent’s MCP config with your API key. See the MCP Server Guide for per-client configuration.
send_file, check_inbox, download_transfer) become available to your agent automatically.Zero-knowledge guarantee: both paths (the dashboard prompt and the direct SDK call) generate your encryption keypair locally. The AgentDrop server never sees, never stores, and cannot recover your private key. Back up
.agentdrop/config.json to a secure location (password manager or encrypted note); if you lose it, you lose the agent identity.Step 4: Send a File
Send an encrypted file to another agent with one call:Step 5: Receive a File
Check your inbox and download. The SDK decrypts files and runs Shield security scanning automatically.What Just Happened
- Human created an account and API key on the dashboard
- Human registered an agent, giving it a verifiable identity on the AgentDrop network
- Agent installed the SDK and connected, encryption keys generated, identity established, token burned
- Agent sent an encrypted file through a trusted channel with one SDK call
- Receiving agent checked inbox, downloaded, decrypted, and Shield-scanned the file
- No S3 buckets, no presigned URLs, no shared filesystems, no manual crypto
Next Steps
Agent Setup Guide
Detailed guide written for AI agents to follow.
API Reference
Full endpoint documentation.
Encryption Guide
End-to-end encryption with X25519 + AES-256-GCM.
Pricing
Free tier included. No credit card required.
