agentdrop

# AgentDrop Deploy a static site (Markdown or HTML) with one HTTP call and get back a public, real-time, undoable URL. No SDK, no API key, no account required. **API base:** `https://abundant-poodle-82.convex.site` ## How to deploy — it is just an HTTP call (there is NO CLI) AgentDrop is **only an HTTP API**. There is no `agent`, `agent-drop`, `drop`, or any other command, binary, MCP tool, or login to find, install, or run. **Do not search the machine for a deploy command and do not run one.** To publish, *you* send a single HTTP request yourself — run the `curl` below (or use your language's HTTP client) and read the `url` out of the JSON response. That is the entire deploy. A site is **one document**: a single Markdown or HTML file, not a folder of files. To include images, upload each one with the images endpoint (below) and use the returned URL in your HTML — never local paths like `./assets/img.png`. Anything the images endpoint doesn't accept (video, fonts, other assets) must be referenced by an absolute public URL you host elsewhere; AgentDrop will not serve it. ## If you speak MCP instead There is a stateless MCP server at `https://abundant-poodle-82.convex.site/mcp` (Streamable HTTP, revision 2026-07-28: no session, no SSE stream, POST only). Add it to your client config and use the tools `deploy_site`, `update_site`, `undo_site`, `redo_site`, `get_site`, and `delete_site` instead of the curl calls below. Older clients that still send `initialize` are answered too. The endpoint requires authorization. An unauthenticated call answers `401` with a `WWW-Authenticate` header pointing at the OAuth metadata, so a client that speaks MCP authorization registers itself and opens a browser automatically. The person is then offered two ways through: connect an account, or continue without one. A client that cannot do OAuth may send an account key as the bearer token instead. Connect the harness you are running in: ```bash claude mcp add --transport http agentdrop https://abundant-poodle-82.convex.site/mcp # Claude Code codex mcp add agentdrop --url https://abundant-poodle-82.convex.site/mcp # Codex gemini mcp add --transport http agentdrop https://abundant-poodle-82.convex.site/mcp # Gemini CLI code --add-mcp '{"name":"agentdrop","type":"http","url":"https://abundant-poodle-82.convex.site/mcp"}' # VS Code ``` Cursor (`~/.cursor/mcp.json`) and anything else that edits JSON: ```json { "mcpServers": { "agentdrop": { "url": "https://abundant-poodle-82.convex.site/mcp" } } } ``` ## If the user has an account key Anonymous deploys are rate limited fairly tightly and the pages they make are temporary. If the user gives you a key that starts with `adk_`, send it on deploy: ```bash curl -X POST https://abundant-poodle-82.convex.site/api/v1/sites \ -H "Authorization: Bearer adk_..." \ -H "Content-Type: application/json" \ -d '{ "kind": "markdown", "visibility": "private", "content": "# Hello" }' ``` With a key the page is owned by that account, kept for 90 days instead of 30, private unless you ask for public, and the create limit is far higher. The user generates one at the app's account page. Treat it like a password: never write it into page content, and never show it back in a published page. ## Private by default — ask before publishing publicly Every page takes a `visibility` of `"private"` or `"public"`. **Always send it explicitly.** Default to `"private"`, and only send `"public"` after the user has said, in that conversation, that the page may be world-readable. If you are unsure, ask them first: "should this be public, or private to you?" - `"private"` — the page opens only for the signed-in owner, or for a caller presenting the edit token. Anyone else with the link gets a plain not-found page, so the URL does not even confirm the page exists. Use this for anything drawn from the user's own code, data, notes, or work. - `"public"` — anyone holding the link can read it. Use this only for something the user is deliberately publishing or sharing. A private page an anonymous deploy created belongs to whoever holds the edit token. Tell the user to open the `manageUrl` and claim it, which ties it to their account and makes it open for them alone. Omitting `visibility` on an update leaves the current setting alone. ## Security — read first NEVER put secrets in site content: no API keys, tokens, passwords, private keys, `.env` values, connection strings, or internal URLs. Site content is **public**. AgentDrop also rejects obvious credentials, but you are the first line of defense. ## Deploy a site ```bash curl -X POST https://abundant-poodle-82.convex.site/api/v1/sites \ -H "Content-Type: application/json" \ -d '{ "kind": "markdown", "visibility": "private", "title": "Optional title", "content": "# Hello\n\nMarkdown or a full HTML document." }' ``` `kind` is `"markdown"` or `"html"`, `visibility` is `"private"` or `"public"`, `title` is optional, and the body is plain JSON: do not put comments inside it. Response: ```json { "slug": "3f9a8c1e-7b2d-4c6a-9e1f-2a8b7c6d5e4f", "url": "https://app.example/3f9a8c1e-7b2d-4c6a-9e1f-2a8b7c6d5e4f", // share this with the user "manageUrl": "https://app.example/manage/3f9a8c1e-7b2d-4c6a-9e1f-2a8b7c6d5e4f?t=SECRET", "editToken": "SECRET", // SAVE THIS "kind": "markdown", "expiresAt": 1730000000000 } ``` Each deploy is assigned a random unguessable URL automatically — you don't choose it. **Persist the `editToken` and `slug`** (e.g. in your working notes). You need the token to update, undo, or delete the site later. Give the user the `url` and the `manageUrl` (the manage page lets them sign in to keep the site for 90 days). ## Update content (replaces the current version, keeps history) ```bash curl -X PUT https://abundant-poodle-82.convex.site/api/v1/sites/<slug> \ -H "Authorization: Bearer <editToken>" \ -H "Content-Type: application/json" \ -d '{ "kind": "markdown", "content": "# Updated" }' ``` Prefer **update / undo over re-creating** a site — the URL stays stable and viewers see changes in real time. ## Undo / redo ```bash curl -X POST https://abundant-poodle-82.convex.site/api/v1/sites/<slug>/undo -H "Authorization: Bearer <editToken>" curl -X POST https://abundant-poodle-82.convex.site/api/v1/sites/<slug>/redo -H "Authorization: Bearer <editToken>" ``` Use these to revert a bad edit instead of resending the whole site. Returns the new `{ canUndo, canRedo, version, versions }`. ## Status & raw content ```bash curl https://abundant-poodle-82.convex.site/api/v1/sites/<slug> # metadata + history status curl https://abundant-poodle-82.convex.site/api/v1/sites/<slug>/raw # the raw Markdown/HTML ``` ## Images (optional) Upload an image, then embed the returned `url` in your Markdown/HTML. ```bash curl -X POST https://abundant-poodle-82.convex.site/api/v1/sites/<slug>/images \ -H "Authorization: Bearer <editToken>" \ -H "Content-Type: image/png" \ --data-binary @diagram.png # → { "url": "https://abundant-poodle-82.convex.site/api/v1/assets/<id>" } ``` Limits: ≤ 5 MB/image, ≤ 10 images/site. **Images always expire after 7 days.** ## Delete ```bash curl -X DELETE https://abundant-poodle-82.convex.site/api/v1/sites/<slug> -H "Authorization: Bearer <editToken>" ``` ## Retention - Anonymous sites: kept **30 days** from the last update. - Claimed sites (user signs in on the manage page): **90 days**. - Images: **7 days**, always. ## Limits - Content: ≤ 1 MB per site. `kind` must be `markdown` or `html`. - Errors return JSON `{ "error": "..." }` with a 4xx/5xx status; rate limits return 429.